post
buff12345
new_folder.zipNew folder/1.docx
I WILL BE IN CHARGE OF THE COVER LETTER , EXECUTIVE SUMMARY AND OUTLINE OF SYSTEM STUDY
1. Cover letter
2. Cover or title page of project
3. Table of contents
4. Executive summary (including recommendations)
5. Outline of system study (all milestone lab assignments)
6. Detailed results of the system study (deliverables from each
milestone lab assignment)
7. System alternatives (use system alternative assessment and
feasibility matrix in Doc Sharing.)
8. System analysts' recommendation (use system alternative
assessment and feasibility matrix in Doc Sharing.)
9. Proposal summary (summarize information into a PowerPoint
presentation.)
10. Appendices (assorted documentation as needed)
1. So, we need a cover letter that is the basic proposal letter to Corner Market
2/3. We have the Title Page and Table of Contents
4. We will need a strong executive summary - as described by the professor she wants an abstract (what to expect to find) of what is contained in the paper, not a summary.
5. Outline of system study can be something like what is found in the course description for the project, and should cover all of the milestones, we have all the milestones, we just need to give an outline of what each is.
6. Detailed results of the milestones which tie to the outline. This is the actual diagrams use case lists, etc. that have been produced
7. System alternatives are not really needed if we have none as the professor outlined tonight. If we want to add 1 alternative to something we can, but it should not be included with the deliverable's and should be in its own report section. I don't think we need to broach this subject and she didn't sound like she cared one way or the other.
8. System analysis recommendation (Glenn did you understand what she wanted here, I got a phone call right in the middle of this part.)
9. Proposal Summary - summary of deliverable's that will need to be put into a PowerPoint presentation that will be uploaded with the project report along with out individual time cards and the team time card.
10. Appendices - the professor is not expecting anything here unless we had to do research for the project. She is expecting most groups to have no appendices as this was not a research paper.
Let me know who wants to tackle what and we can all work together to finish this project in a timely manner and move on with other things.
I would highly recommend downloading the week 7 seminar from doc sharing as the professor posted the topics and key items for the final and it should help.
New folder/Course Project Report Group C - Milestone 1 v3.0.docx
17
Course Project Report - Milestone 1
MIS-581
e-Grocer System Analysis
Group C
Anders Berg
Glenn Garrett
Dixon Stapleton
Ydannie Boncenor
Course Project Report
Professor Masullo
November, 2015
Table of Contents Statement of the Business Problem (System Request Form) 3 Business Requirements 5 1. Context Level Data Flow Diagram (Visio) 5 2. Use CASE List (normal business activities/work flows) 6 3. Use CASE Diagram (Visio) 10 4. Use CASE Scenarios (Description or narrative of steps in each use case) 14
Statement of the Business Problem (System Request Form)
Date: November 9, 2015
Project Name: MIS581 - Group C
Project Sponsor:
Name:
Department: e-Commerce
Organization: Corner Market
Contact Information: Phone:
Business Problem Statement:
To compete with larger grocery store chains, Corner Market needs to offer a grocery delivery service. Currently, they may take special orders over the phone, but they do not have a way for customers to browse products, place, track, and manage orders, or a way for their employees to be notified of and update orders in a timely manner.
System Scope Statement:
An e-commerce system that integrates with logistical functions will include the ability to place orders, update products, and manage orders. The project includes the infrastructure architecture, configuration, and deployment of the application as well as integration of third party billing and inventory systems. Testing and user acceptance will be performed prior to deployment.
High-Level Functional Requirements:
Customer
As a Customer
I want to browse products
So that I can place an order for delivery
As a Customer
I want to add products to my virtual shopping cart
So that I can continue shopping until I am ready to place my order
As a Customer
I want to checkout
So that I can finalize my order and trigger fulfillment
As a Customer
I want to be able to cancel my order before fulfillment
So that I have flexibility and freedom
As a Customer
I want to be able to view my status
So that I have a near real-time expectation of when my order will be delivered
As a Customer I want to be able to return an incorrect item So that I can exchange it for the correct item
Picker
As a Picker
I want to receive notification of a new order
So that I can begin fulfillment
As a Picker
I want to be able to update the status
So that I can trigger the next phase of fulfillment
Driver
As a Driver
I want to be receive notification that an order is staged for delivery
So that I can load it into my truck for delivery
As a Driver
I want to be able to update the status
So that I can trigger accurate delivery estimates and complete the order
Administrator
As an Administrator
I want to be able to view order status
So that I can track and manage company resources
As an Administrator
I want to be able to manage products
So that the system reflects the most accurate and current data
As an Administrator
I want to be able to manage orders
So that I can make adjustments to reflect status
Business Benefits:
Corner Market will be able to continue offering their farmers-market small-business service to their customers allowing them to continue to compete with larger grocery chains. Customers will be able to patron their favorite local market from the comfort and convenience of their home, increasing brand loyalty and positioning the organization to acquire a larger market.
Special Issues or Constraints:
Business Requirements
1. Context Level Data Flow Diagram (Visio)
2. Use CASE List (normal business activities/work flows)
USE CASE LISTS
e-Grocer Delivery System
Author (s): MIS581 – Group C Date: Nov 14, 2015
Version: 2.0
|
USE CASE NAME: |
Customer Item Selection |
USE CASE TYPE |
|
USE CASE ID: |
CIS |
Abstract: |
|
PRIORITY: |
|
Extension: |
|
INVOKED BY: |
Customer |
|
|
PARTICIPATING ACTORS: |
Customer |
|
|
DESCRIPTION: |
Online item selection by customer |
|
|
PRE-CONDITION: |
Customer needs groceries |
|
|
TYPICAL COURSE OF EVENTS: |
Step 1: Customer inputs Zip Code for home delivery availability, shops online and chooses items that are then placed in the online “cart” |
|
|
|
Step 2: Customer finishes choosing items and pays for the items in the “cart” during checkout |
|
|
|
Step 3: Customer provides payment information that is processed by the store (Credit/Debit/PayPal) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ALTERNATE COURSES: |
|
|
|
POST-CONDITION: |
Customer order processed, awaiting payment authorization |
|
USE CASE NAME: |
Customer Payment Processing |
USE CASE TYPE |
|
USE CASE ID: |
CPP |
Abstract: |
|
PRIORITY: |
|
Extension: |
|
INVOKED BY: |
e-Grocer System |
|
|
PARTICIPATING ACTORS: |
Customer, Payment Processor Employee (bank, credit card, PayPal, etc.), |
|
|
DESCRIPTION: |
Customer makes payment for online purchases |
|
|
PRE-CONDITION: |
Payment needed for online purchases |
|
|
TYPICAL COURSE OF EVENTS: |
Step 1: Payment system (bank, credit card, PayPal) processes payment choice made by customer for online placed in cart online |
|
|
|
Step 2a: Payment approved move to Step 3 |
|
|
|
Step 2b: Payment declined, move to CIS Step 3 and verify information or choose new payment method |
|
|
|
Step 2c: Restart CPP Step 1 |
|
|
|
Step 3: Payment system notifies e-Grocer System of approved payment status |
|
|
|
Step 4: e-Grocer System order status updated |
|
|
|
|
|
|
|
|
|
|
ALTERNATE COURSES: |
No verified payment, customer notified of payment failure, order deleted from e-Grocer System, |
|
|
POST-CONDITION: |
Payment approved, online order will be processed |
|
USE CASE NAME: |
Order Picking/Packing |
USE CASE TYPE |
|
USE CASE ID: |
OPP |
Abstract: |
|
PRIORITY: |
|
Extension: |
|
INVOKED BY: |
e-Grocer System |
|
|
PARTICIPATING ACTORS: |
e-Grocer Associate, e-Grocer Delivery Driver, Payment Processor Employee (bank, credit card, PayPal, etc.) |
|
|
DESCRIPTION: |
Upon approved payment, E-Grocer associate pulls orders, makes ready for delivery |
|
|
PRE-CONDITION: |
Approved payment for online purchases |
|
|
TYPICAL COURSE OF EVENTS: |
Step 1: Payment System notifies the e-Grocer System of approved payment status |
|
|
|
Step 2: e-Grocer System notifies e-Grocer associate of order needing to be pulled |
|
|
|
Step 3a: In stock items pulled and placed in order delivery carriers |
|
|
|
Step 3b: items that are out of stock or non-stock are ordered from other vendors/warehouses |
|
|
|
Step 3c: non and out stock items are gathered and placed with stocking items in pulled order delivery carriers |
|
|
|
Step 4: Delivery driver notified of order/s status |
|
|
|
Step 5: e-Grocer System order status updated |
|
|
|
|
|
|
ALTERNATE COURSES: |
Unobtainable item/s status communicated to customer for varied item selection or drop from order, payment change processed |
|
|
POST-CONDITION: |
Completed orders are ready for delivery to customer/s home/s |
|
USE CASE NAME: |
Delivery to Customer Home |
USE CASE TYPE |
|
USE CASE ID: |
DCH |
Abstract: |
|
PRIORITY: |
|
Extension: |
|
INVOKED BY: |
e-Grocer System |
|
|
PARTICIPATING ACTORS: |
e-Grocer Associate, e-Grocer Delivery Driver, Customer |
|
|
DESCRIPTION: |
e-Grocer associate processes pulled order/s to e-Grocer delivery driver to load and deliver to customer, updating order status |
|
|
PRE-CONDITION: |
Order/s pulled waiting for delivery |
|
|
TYPICAL COURSE OF EVENTS: |
Step 1: e-Grocer System order status updated |
|
|
|
Step 2: e-Grocer associate processes order/s for delivery to corresponding driver/s |
|
|
|
Step 3: e-Grocer associate released order/s to e-Grocer delivery driver/s for loading of delivery carriers |
|
|
|
Step 4: e-Grocer delivery driver loads delivery carriers into delivery vehicle for transport |
|
|
|
Step 5: e-Grocer delivery driver/s make delivery of carriers with online orders to customer/s home/s |
|
|
|
Step 6: e-Grocer delivery driver updates status or order as delivered or any issues |
|
|
|
Step 7: e-Grocer System order status updated |
|
|
|
|
|
|
ALTERNATE COURSES: |
Any issues items are entered into E-Grocer System to be handled by and e-Grocer associate |
|
|
POST-CONDITION: |
Items ordered online have been satisfactorily delivered to customer home |
3. Use CASE Diagram (Visio)
4. Use CASE Scenarios Case ID: CIS (Description or narrative of steps in each use case)
|
Use Case Name |
Customer Item Selection (CIS) |
|
Trigger Event |
Customer browsers to website or mobile application with intent to purchase grocery products online for home delivery |
|
Description |
A customer visiting the website or mobile application searches for grocery products that they wish to purchase. |
|
Actors |
Customer, e-Grocer System |
|
Pre-condition |
Customer needs groceries |
|
Post-condition |
Customer order processed, awaiting payment authorization |
|
Flow of Activities |
· Customer chooses e-Grocer System online to purchase groceries for home delivery · Customer enters home zip code to verify home delivery availability · Customer starts choosing items from e-Grocer System, placing them in the online cart · Customer finishes choosing items and moves to the checkout page of the e-Grocer System · Customer chooses type of payment · Customer enter payment information (bank/credit card/PayPal) |
Use CASE Scenarios Case ID: CPP (Description or narrative of steps in each use case)
|
Use Case Name |
Customer Payment Processing (CPP) |
|
Trigger Event |
Customer has entered payment choice and information, e-Grocer System contacts Payment Processor |
|
Description |
The e-Grocer System, having had the customer enter their choice of payment type and needed information, sends information to the Payment Processor |
|
Actors |
e-Grocer System, Payment Processor (bank/credit/PayPal), Customer |
|
Pre-condition |
Customer chooses type of payment and inputs payment information |
|
Post-condition |
Customer order processed, awaiting payment authorization |
|
Flow of Activities |
· e-Grocer System send payment information for processing to chosen Payment Processor · Payment Processor begins processing payment · If payment is approved Payment Processor will notify the e-Grocer System of order payment approval · If chosen payment method fails the Payment Processor will notify the e-Grocer System and the customer will be alerted and asked to verify information or choose new payment method · Upon approved payment, e-Grocer System updated and order status is moved to picking |
Use CASE Scenarios Case ID: OPP (Description or narrative of steps in each use case)
|
Use Case Name |
Order Picking/Packing (OPP) |
|
Trigger Event |
Payment Processor has approved payment method and e-Grocer System status set to pick order |
|
Description |
The e-Grocer System, having had the customers payment choice authorized prints a list of the order for the e-Grocer associates to pull |
|
Actors |
e-Grocer System, e-Grocer Associates, Payment Processor (bank/credit/PayPal), Customer |
|
Pre-condition |
Customer payment option approved |
|
Post-condition |
Customer order processed, awaiting delivery |
|
Flow of Activities |
· Payment Processor has approved payment choice of customer · e-Grocer System status updated and customer order printed · e-Grocer associate retrieves customer order and begins picking order · In stock items pulled and placed in delivery carriers · Non stock or out stock items are ordered from other warehouses or vendors as needed based on item · Non stock or out stock items are gathered from other suppliers and placed in delivery carriers · All items are placed in temporary cold storage awaiting a delivery driver assignment · Order status updated in the e-Grocer System |
Use CASE Scenarios Case ID: DCH (Description or narrative of steps in each use case)
|
Use Case Name |
Delivery to Customer home (DCH) |
|
Trigger Event |
e-Grocer System updated showing order status set to deliver |
|
Description |
The e-Grocer System, having had the customer’s order completely pulled to completion is made available for delivery, a delivery driver is assigned to the home delivery. Order is loaded is delivery vehicle and home delivery takes place |
|
Actors |
e-Grocer System, e-Grocer Associates, e-Grocer Delivery Driver, Customer |
|
Pre-condition |
Customer order picking is complete and order is fully prepared in delivery carriers |
|
Post-condition |
Customer order is delivered to home location and e-Grocer System order status is updated by the Delivery Driver |
|
Flow of Activities |
· e-Grocer System status updated to order completion, awaiting delivery · e-Grocer associate processes order/s and alerts e-Grocer System of assigned e-Grocer delivery driver · e-Grocer associate releases order/s (delivery carriers) to assigned e-Grocer delivery driver · e-Grocer delivery driver loads assigned order/s in to delivery vehicle · e-Grocer delivery driver delivers order/s placed online through the e-Grocer System to the home/s of the customer/s · e-Grocer delivery driver updates each order status as delivered in the e-Grocer System upon completion of home delivery · e-grocer System order status updated |
E-Grocer System Customer Checkout Browse Inventory Add Product To Cart Check Delivery Availibility Use Case Diagram: (CIS) Customer Item Selection E-Grocer Database
CustomerOrder StatusPayment ApprovedPayment DeclinedPayment Choice And InformationUse Case Diagram: (CPP) Customer Payment ProcessingPayment ProcessorPayment Status
E-Grocer System Customer Order Status Payment Approved Payment Declined Payment Choice And Information Use Case Diagram: (CPP) Customer Payment Processing Payment Processor Payment Status
Other Vendor/WarehouseE-Grocer AssociateStock Items PickedDelivery DriverAssigned & NotifiedOut of Stock / Non Inventory ItemsOrder and GatheredDelivery CarrierDelivery Carrier Placed In Cold StorageReady For DeliveryE-Grocer Delivery DriverE-Grocer DatabaseOrder ApprovedPayment Processor EmployeeNon Stock/Out Of StockItems ReceivedOrder CompleteUse Case Diagram: (OPP) Order Picking/Packing
E-Grocer System Other Vendor/Warehouse E-Grocer Associate Stock Items Picked Delivery Driver Assigned & Notified Out of Stock / Non Inventory Items Order and Gathered Delivery Carrier Delivery Carrier Placed In Cold Storage Ready For Delivery E-Grocer Delivery Driver E-Grocer Database Order Approved Payment Processor Employee Non Stock/Out Of Stock Items Received Order Complete Use Case Diagram: (OPP) Order Picking/Packing
CustomerE-Grocer Delivery DriverE-Grocer AssocaiteDelivery Driver AssignedE-Grocer Associate NotifiedDelivery Carrier ReleasedTo Delivery DriverDelivery Carrier LoadedInto VehicleE-grocer Delivery DriverDelivers Order To Customers HomeE-Grocer System Order Status UpdatedE-Grocer DatabaseUse Case Diagram: (DCH) Delivery to Customer Home
Use Case Diagram: (DCH) Delivery to Customer Home
CustomerCheckoutBrowse InventoryAdd Product To CartCheck Delivery AvailibilityUse Case Diagram: (CIS) Customer Item SelectionE-Grocer Database
New folder/Course Project Report Group C - Milestone 1-4 v4.2.docx
28
Course Project Report
MIS-581
e-Grocer System Analysis
Group C
Anders Berg
Glenn Garrett
Dixon Stapleton
Ydannie Boncenor
Course Project Report
Professor Masullo
December, 2015
Table of Contents Statement of the Business Problem (System Request Form) 3 2. Business Requirements 3 3. Context Level Data Flow Diagram (Visio) 5 4. Use CASE List (normal business activities/work flows) 6 5 Use CASE Diagram (Visio) 10 6. Use CASE Scenarios Case ID: CIS (Description or narrative of steps in each use case) 14 7. Project Charter 18 8. Logical and Physical Data Flow Diagrams 22 9. Logical and Physical Entity Relationship Diagrams 24 10. UML Use Case Diagram 26 11. UML Class Diagram 27 11. UML Sequence Diagram 28
Statement of the Business Problem (System Request Form)
Date: November 9, 2015
Project Name: MIS581 - Group C
Project Sponsor:
Name:
Department: e-Commerce
Organization: Corner Market
Contact Information: Phone:
Business Problem Statement:
To compete with larger grocery store chains, Corner Market needs to offer a grocery delivery service. Currently, they may take special orders over the phone, but they do not have a way for customers to browse products, place, track, and manage orders, or a way for their employees to be notified of and update orders in a timely manner.
System Scope Statement:
An e-commerce system that integrates with logistical functions will include the ability to place orders, update products, and manage orders. The project includes the infrastructure architecture, configuration, and deployment of the application as well as integration of third party billing and inventory systems. Testing and user acceptance will be performed prior to deployment.
High-Level Functional Requirements:
Customer
As a Customer
I want to browse products
So that I can place an order for delivery
As a Customer
I want to add products to my virtual shopping cart
So that I can continue shopping until I am ready to place my order
As a Customer
I want to checkout
So that I can finalize my order and trigger fulfillment
As a Customer
I want to be able to cancel my order before fulfillment
So that I have flexibility and freedom
As a Customer
I want to be able to view my status
So that I have a near real-time expectation of when my order will be delivered
As a Customer I want to be able to return an incorrect item So that I can exchange it for the correct item
Picker
As a Picker
I want to receive notification of a new order
So that I can begin fulfillment
As a Picker
I want to be able to update the status
So that I can trigger the next phase of fulfillment
Driver
As a Driver
I want to be receive notification that an order is staged for delivery
So that I can load it into my truck for delivery
As a Driver
I want to be able to update the status
So that I can trigger accurate delivery estimates and complete the order
Administrator
As an Administrator
I want to be able to view order status
So that I can track and manage company resources
As an Administrator
I want to be able to manage products
So that the system reflects the most accurate and current data
As an Administrator
I want to be able to manage orders
So that I can make adjustments to reflect status
Business Benefits:
Corner Market will be able to continue offering their farmers-market small-business service to their customers allowing them to continue to compete with larger grocery chains. Customers will be able to patron their favorite local market from the comfort and convenience of their home, increasing brand loyalty and positioning the organization to acquire a larger market.
Special Issues or Constraints:
Business Requirements
1. Context Level Data Flow Diagram (Visio)
2. Use CASE List (normal business activities/work flows)
USE CASE LISTS
e-Grocer Delivery System
Author (s): MIS581 – Group C Date: Nov 14, 2015
Version: 2.0
|
USE CASE NAME: |
Customer Item Selection |
USE CASE TYPE |
|
USE CASE ID: |
CIS |
Abstract: |
|
PRIORITY: |
|
Extension: |
|
INVOKED BY: |
Customer |
|
|
PARTICIPATING ACTORS: |
Customer |
|
|
DESCRIPTION: |
Online item selection by customer |
|
|
PRE-CONDITION: |
Customer needs groceries |
|
|
TYPICAL COURSE OF EVENTS: |
Step 1: Customer inputs Zip Code for home delivery availability, shops online and chooses items that are then placed in the online “cart” |
|
|
|
Step 2: Customer finishes choosing items and pays for the items in the “cart” during checkout |
|
|
|
Step 3: Customer provides payment information that is processed by the store (Credit/Debit/PayPal) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ALTERNATE COURSES: |
|
|
|
POST-CONDITION: |
Customer order processed, awaiting payment authorization |
|
USE CASE NAME: |
Customer Payment Processing |
USE CASE TYPE |
|
USE CASE ID: |
CPP |
Abstract: |
|
PRIORITY: |
|
Extension: |
|
INVOKED BY: |
e-Grocer System |
|
|
PARTICIPATING ACTORS: |
Customer, Payment Processor Employee (bank, credit card, PayPal, etc.), |
|
|
DESCRIPTION: |
Customer makes payment for online purchases |
|
|
PRE-CONDITION: |
Payment needed for online purchases |
|
|
TYPICAL COURSE OF EVENTS: |
Step 1: Payment system (bank, credit card, PayPal) processes payment choice made by customer for online placed in cart online |
|
|
|
Step 2a: Payment approved move to Step 3 |
|
|
|
Step 2b: Payment declined, move to CIS Step 3 and verify information or choose new payment method |
|
|
|
Step 2c: Restart CPP Step 1 |
|
|
|
Step 3: Payment system notifies e-Grocer System of approved payment status |
|
|
|
Step 4: e-Grocer System order status updated |
|
|
|
|
|
|
|
|
|
|
ALTERNATE COURSES: |
No verified payment, customer notified of payment failure, order deleted from e-Grocer System, |
|
|
POST-CONDITION: |
Payment approved, online order will be processed |
|
USE CASE NAME: |
Order Picking/Packing |
USE CASE TYPE |
|
USE CASE ID: |
OPP |
Abstract: |
|
PRIORITY: |
|
Extension: |
|
INVOKED BY: |
e-Grocer System |
|
|
PARTICIPATING ACTORS: |
e-Grocer Associate, e-Grocer Delivery Driver, Payment Processor Employee (bank, credit card, PayPal, etc.) |
|
|
DESCRIPTION: |
Upon approved payment, E-Grocer associate pulls orders, makes ready for delivery |
|
|
PRE-CONDITION: |
Approved payment for online purchases |
|
|
TYPICAL COURSE OF EVENTS: |
Step 1: Payment System notifies the e-Grocer System of approved payment status |
|
|
|
Step 2: e-Grocer System notifies e-Grocer associate of order needing to be pulled |
|
|
|
Step 3a: In stock items pulled and placed in order delivery carriers |
|
|
|
Step 3b: items that are out of stock or non-stock are ordered from other vendors/warehouses |
|
|
|
Step 3c: non and out stock items are gathered and placed with stocking items in pulled order delivery carriers |
|
|
|
Step 4: Delivery driver notified of order/s status |
|
|
|
Step 5: e-Grocer System order status updated |
|
|
|
|
|
|
ALTERNATE COURSES: |
Unobtainable item/s status communicated to customer for varied item selection or drop from order, payment change processed |
|
|
POST-CONDITION: |
Completed orders are ready for delivery to customer/s home/s |
|
USE CASE NAME: |
Delivery to Customer Home |
USE CASE TYPE |
|
USE CASE ID: |
DCH |
Abstract: |
|
PRIORITY: |
|
Extension: |
|
INVOKED BY: |
e-Grocer System |
|
|
PARTICIPATING ACTORS: |
e-Grocer Associate, e-Grocer Delivery Driver, Customer |
|
|
DESCRIPTION: |
e-Grocer associate processes pulled order/s to e-Grocer delivery driver to load and deliver to customer, updating order status |
|
|
PRE-CONDITION: |
Order/s pulled waiting for delivery |
|
|
TYPICAL COURSE OF EVENTS: |
Step 1: e-Grocer System order status updated |
|
|
|
Step 2: e-Grocer associate processes order/s for delivery to corresponding driver/s |
|
|
|
Step 3: e-Grocer associate released order/s to e-Grocer delivery driver/s for loading of delivery carriers |
|
|
|
Step 4: e-Grocer delivery driver loads delivery carriers into delivery vehicle for transport |
|
|
|
Step 5: e-Grocer delivery driver/s make delivery of carriers with online orders to customer/s home/s |
|
|
|
Step 6: e-Grocer delivery driver updates status or order as delivered or any issues |
|
|
|
Step 7: e-Grocer System order status updated |
|
|
|
|
|
|
ALTERNATE COURSES: |
Any issues items are entered into E-Grocer System to be handled by and e-Grocer associate |
|
|
POST-CONDITION: |
Items ordered online have been satisfactorily delivered to customer home |
3. Use CASE Diagram (Visio)
4. Use CASE Scenarios Case ID: CIS (Description or narrative of steps in each use case)
|
Use Case Name |
Customer Item Selection (CIS) |
|
Trigger Event |
Customer browsers to website or mobile application with intent to purchase grocery products online for home delivery |
|
Description |
A customer visiting the website or mobile application searches for grocery products that they wish to purchase. |
|
Actors |
Customer, e-Grocer System |
|
Pre-condition |
Customer needs groceries |
|
Post-condition |
Customer order processed, awaiting payment authorization |
|
Flow of Activities |
· Customer chooses e-Grocer System online to purchase groceries for home delivery · Customer enters home zip code to verify home delivery availability · Customer starts choosing items from e-Grocer System, placing them in the online cart · Customer finishes choosing items and moves to the checkout page of the e-Grocer System · Customer chooses type of payment · Customer enter payment information (bank/credit card/PayPal) |
Use CASE Scenarios Case ID: CPP (Description or narrative of steps in each use case)
|
Use Case Name |
Customer Payment Processing (CPP) |
|
Trigger Event |
Customer has entered payment choice and information, e-Grocer System contacts Payment Processor |
|
Description |
The e-Grocer System, having had the customer enter their choice of payment type and needed information, sends information to the Payment Processor |
|
Actors |
e-Grocer System, Payment Processor (bank/credit/PayPal), Customer |
|
Pre-condition |
Customer chooses type of payment and inputs payment information |
|
Post-condition |
Customer order processed, awaiting payment authorization |
|
Flow of Activities |
· e-Grocer System send payment information for processing to chosen Payment Processor · Payment Processor begins processing payment · If payment is approved Payment Processor will notify the e-Grocer System of order payment approval · If chosen payment method fails the Payment Processor will notify the e-Grocer System and the customer will be alerted and asked to verify information or choose new payment method · Upon approved payment, e-Grocer System updated and order status is moved to picking |
Use CASE Scenarios Case ID: OPP (Description or narrative of steps in each use case)
|
Use Case Name |
Order Picking/Packing (OPP) |
|
Trigger Event |
Payment Processor has approved payment method and e-Grocer System status set to pick order |
|
Description |
The e-Grocer System, having had the customers payment choice authorized prints a list of the order for the e-Grocer associates to pull |
|
Actors |
e-Grocer System, e-Grocer Associates, Payment Processor (bank/credit/PayPal), Customer |
|
Pre-condition |
Customer payment option approved |
|
Post-condition |
Customer order processed, awaiting delivery |
|
Flow of Activities |
· Payment Processor has approved payment choice of customer · e-Grocer System status updated and customer order printed · e-Grocer associate retrieves customer order and begins picking order · In stock items pulled and placed in delivery carriers · Non stock or out stock items are ordered from other warehouses or vendors as needed based on item · Non stock or out stock items are gathered from other suppliers and placed in delivery carriers · All items are placed in temporary cold storage awaiting a delivery driver assignment · Order status updated in the e-Grocer System |
Use CASE Scenarios Case ID: DCH (Description or narrative of steps in each use case)
|
Use Case Name |
Delivery to Customer home (DCH) |
|
Trigger Event |
e-Grocer System updated showing order status set to deliver |
|
Description |
The e-Grocer System, having had the customer’s order completely pulled to completion is made available for delivery, a delivery driver is assigned to the home delivery. Order is loaded is delivery vehicle and home delivery takes place |
|
Actors |
e-Grocer System, e-Grocer Associates, e-Grocer Delivery Driver, Customer |
|
Pre-condition |
Customer order picking is complete and order is fully prepared in delivery carriers |
|
Post-condition |
Customer order is delivered to home location and e-Grocer System order status is updated by the Delivery Driver |
|
Flow of Activities |
· e-Grocer System status updated to order completion, awaiting delivery · e-Grocer associate processes order/s and alerts e-Grocer System of assigned e-Grocer delivery driver · e-Grocer associate releases order/s (delivery carriers) to assigned e-Grocer delivery driver · e-Grocer delivery driver loads assigned order/s in to delivery vehicle · e-Grocer delivery driver delivers order/s placed online through the e-Grocer System to the home/s of the customer/s · e-Grocer delivery driver updates each order status as delivered in the e-Grocer System upon completion of home delivery · e-grocer System order status updated |
Corner Market, Inc.
Project Charter
|
Project Title: E-Grocer Internet Project with Same-Day Delivery Service |
Project ID: |
|
Sponsoring Organization: |
Sponsor Representative: |
|
Prepared By: Group – C |
Version: 1 |
|
Project Authorization: November 2015 |
Project Category: Strategic |
|
Project Start Date: November 2015 |
Project Finish Date: December 2015 |
A new Web-based service from Corner Market, Inc. is proposed: Get same-day or overnight delivery on everything in the store (perishable and non-perishable items). The operations will be located inside company stores with the “storefront” being an area of the existing Corner Market retail website. A diverse team of professionals will design and test new technology and logistics capabilities for the new delivery service.
The delivery service will corner the market of consumers that may not have the means or time to go to the market for their essentials. This service is ‘forward-thinking’ and will help us to develop a strategic change in existing operations and result in major cost savings that could mean the difference between future market success and failure.
Trial period for same-day and overnight delivery services will begin in a few select cities as a prototype. A number of new cities will be launched within two years from the present date.
Given the business need, the goal of our project is to continue to provide excellent customer service – albeit from a different method. We aim to do this by allowing consumers to shop their local Corner Market from the comfort of their home, office, etc. via our Website, and choose when and where they want delivery.
In business terms, our objectives are to increase market share and revenues by 10%. This is obtainable by providing excellent customer service, a fully functioning and easy-to-use Webstore, and by providing the best prices to our customers.
Vision or Preliminary Scope of the Project
The vision, or preliminary scope, of the project will be to attract customers (whom may already be existing customers or not) to shop the store and create more business for Corner Market, Inc. The preliminary scope of the project will be to set up operations in a few major cities (i.e. Los Angeles, San Francisco, Chicago, New York) as a trial for public adoption, to iron out early issues with the new technology, inventory, and logistics capabilities.
Sponsor: Mark Spenser | Project Support
Program Manager: Susan Town | Project Oversight
Project Manager: Geoffrey Smith | Risk Management, Control, Tracking
Project Team: Anders Berg | [email protected]
Dannie Boncenor | [email protected]
Dixon Stapleton | [email protected]
Glenn Garrett | [email protected]
Senior Programmer: Tom Sawyer | System Architect
Business Analyst: Mark Twain | Application Services
Data Architect: Julia White | Data Services
Project Manager Responsibilities and Authority:
The project team reports to the project manager during the lifespan of the project. Semi-annual evaluations of project team members will be conducted by functional managers with input from the project manager.
Corner Market, Inc. has allocated $75 million for new operating initiatives for the next two years (2016-2017). The majority of the costs of the project is through capital budget. No outsourcing is expected in this project.
The new service must meet all codes and specifications and should be completed on time with all equipment and computers ready to be deployed.
Without the newly requested equipment and people, it will be impossible to develop this new service. Lower revenues and profits due to loss of market share, existing and new-to-market external competitors, and a slow adoption rate are also risks that should be considered.
|
Event |
Probability |
Impact |
Mitigation |
|
Requirement changes after project sign-off |
Low |
Increase of budget and delay of project |
Involve all stakeholders to provide input and requirements during analysis |
|
Inability to transfer current data to new platform |
Low |
New platform may not be used to full potential |
Hire experienced partner during installation |
|
Unexpected technical problems |
Medium |
Project delay |
Develop a contingency plan |
|
Budget constraint |
Low |
Project delay |
Raise more funding from sponsor |
|
Integration does not meet requirements |
Medium |
Customer service will be hampered, system may not be liked by staff |
Full system test before live deployment |
Assumptions
· All personnel that are needed will be available to see the project to a successful completion
· Certified partner will assist Corner Market in a timely manner
· Project team will set appropriate goals for this project
· Security of customer data will be fully addressed
· No disastrous technological failures
· Organizational direction does not change during the project
· Courses needed to train key employees will be made available
· Funding will not be cut during the project
Constraints
· A limited budget has been set and need to balance the time to have optimum productivity.
·
The project stakeholders are our existing customer base, users, the project team, project sponsors, project champions, upper management, functional managers, the project manager, the project management office, suppliers, and members of the public who are potentially affected by the project. Corner Market, Inc. will document project activities and communicate with them during weekly meetings. Daily “stand-up” meetings will also be held to communicate pressing issues. The project will be approved by upper management, with power to make ongoing decisions being given to the project manager.
|
Approval Date: |
|
Project Manager: |
|
Project Sponsor(s): |
Name: Date:
______________________________________________________________
Name: Date:
______________________________________________________________
Name: Date:
______________________________________________________________
Logical and Physical Data Flow Diagrams
Logical and Physical Entity Relationship Diagrams
Logical Entity Relationship Diagram
Physical Entity Relationship Diagram
UML Use Case Diagram
UML Class Diagram
UML Sequence Diagram
E-Grocer System Customer Checkout Browse Inventory Add Product To Cart Check Delivery Availibility Use Case Diagram: (CIS) Customer Item Selection E-Grocer Database
CustomerOrder StatusPayment ApprovedPayment DeclinedPayment Choice And InformationUse Case Diagram: (CPP) Customer Payment ProcessingPayment ProcessorPayment Status
E-Grocer System Customer Order Status Payment Approved Payment Declined Payment Choice And Information Use Case Diagram: (CPP) Customer Payment Processing Payment Processor Payment Status
Other Vendor/WarehouseE-Grocer AssociateStock Items PickedDelivery DriverAssigned & NotifiedOut of Stock / Non Inventory ItemsOrder and GatheredDelivery CarrierDelivery Carrier Placed In Cold StorageReady For DeliveryE-Grocer Delivery DriverE-Grocer DatabaseOrder ApprovedPayment Processor EmployeeNon Stock/Out Of StockItems ReceivedOrder CompleteUse Case Diagram: (OPP) Order Picking/Packing
E-Grocer System Other Vendor/Warehouse E-Grocer Associate Stock Items Picked Delivery Driver Assigned & Notified Out of Stock / Non Inventory Items Order and Gathered Delivery Carrier Delivery Carrier Placed In Cold Storage Ready For Delivery E-Grocer Delivery Driver E-Grocer Database Order Approved Payment Processor Employee Non Stock/Out Of Stock Items Received Order Complete Use Case Diagram: (OPP) Order Picking/Packing
CustomerE-Grocer Delivery DriverE-Grocer AssocaiteDelivery Driver AssignedE-Grocer Associate NotifiedDelivery Carrier ReleasedTo Delivery DriverDelivery Carrier LoadedInto VehicleE-grocer Delivery DriverDelivers Order To Customers HomeE-Grocer System Order Status UpdatedE-Grocer DatabaseUse Case Diagram: (DCH) Delivery to Customer Home
Use Case Diagram: (DCH) Delivery to Customer Home
CustomerCustomer1ShippingAvailibility2IdentifyItems3PriceLookup4Fill Cart5Compute Cost Of Order6Settle TransactionD1Shipping AreaD3Price CheckZip CodeItems To PurchaseItem IDAdd ToCartItems &PricesCompute CostPaymentReceiptLogical Data Flow Diagram- Use Case CIS
Customer Customer 1 Shipping Availibility 2 Identify Items 3 Price Lookup 4 Fill Cart 5 Compute Cost Of Order 6 Settle Transaction D1 Shipping Area D3 Price Check Zip Code Items To Purchase Item ID Add To Cart Items & Prices Compute Cost Payment Receipt Logical Data Flow Diagram- Use Case CIS
CustomerSettle Transaction:1. Collect money2. Display and send receipt (electronically)Input Zip CodeSearch For Items(Or Input Item ID)Calculated Cost to be PaidPayment TransferredPhysical Data Flow Diagram - Use Case CISDelivery AvailabilityView ItemAdd to CartReview CartAdd Quantity To CartRemove Quantity From CartCheckoutProceed to CheckoutSearch For Different Items Again1.Manage “Loyalty Programs”2. Re-order Essentials(Agree to Privacy and Terms of Service)1.Set Delivery Address2. Set Delivery Window3. Set Payment Method4. Add Promo CodeCompute Cost of OrderSelect QuantityPlace OrderShipping AreaTemporary Trans. FileItems and PricesItems, Prices, and SubtotalsCustomer InputCustomer InputCustomer
Customer Settle Transaction: 1. Collect money 2. Display and send receipt (electronically) Input Zip Code Search For Items (Or Input Item ID) Calculated Cost to be Paid Payment Transferred Physical Data Flow Diagram - Use Case CIS Delivery Availability View Item Add to Cart Review Cart Add Quantity To Cart Remove Quantity From Cart Checkout Proceed to Checkout Search For Different Items Again 1.Manage “Loyalty Programs” 2. Re-order Essentials (Agree to Privacy and Terms of Service) 1.Set Delivery Address 2. Set Delivery Window 3. Set Payment Method 4. Add Promo Code Compute Cost of Order Select Quantity Place Order Shipping Area Temporary Trans. File Items and Prices Items, Prices, and Subtotals Customer Input Customer Input Customer
CustomerOrderRoleProductStoreLocationEmployeeCustomerIDPKFirstNamevarchar(25)StreetAddressvarchar(200)OrderIDPKCustomerIDvarchar(50)FKCountinteger(20)RoleIDPKNamevarchar(10)ProductIDPKSKUinteger(20)Namevarchar(25)StoreLocationIDPKNamevarchar(25)StreetAddressvarchar(200)EmployeeIDPKFirstNamevarchar(25)PhoneNumberinteger(20)EmailAddressvarchar(40)PhoneNumberinteger(20)AltPhoneNumberinteger(20)Passwordvarchar(10)Order_Countinteger(20)PurchaseSubtotalinteger(10)Taxinteger(6)DeliveryFeeinteger(5)PurchaseTotalinteger(10)Statusvarchar(10)SpecialInstructionsvarchar(30)EmailAddressvarchar(40)UserNamevarchar(20)Passwordvarchar(10)Descriptionvarchar(50)PhoneNumberinteger(20)Manufacturervarchar(10)ZipCodeinteger(10)ZipCodeinteger(10)LastNamevarchar(25)StreetAddressvarchar(200)ZipCodeinteger(10)LastNamevarchar(25)EmployeeIDFKattribute nameProductIDFKEmployeeIDFKRoleIDFKPriceinteger(6)
Customer Order Role Product StoreLocation Employee CustomerID int FK PK FirstName varchar(25) int FK PK StreetAddress varchar(200) int FK PK OrderID int FK PK CustomerID varchar(50) int FK PK Count integer(20) int FK PK RoleID int FK PK Name varchar(10) int FK PK ProductID int FK PK SKU integer(20) int FK PK Name varchar(25) int FK PK StoreLocationID int FK PK Name varchar(25) int FK PK StreetAddress varchar(200) int FK PK EmployeeID int FK PK FirstName varchar(25) int FK PK PhoneNumber integer(20) int FK PK EmailAddress varchar(40) int FK PK PhoneNumber integer(20) int FK PK AltPhoneNumber integer(20) int FK PK Password varchar(10) int FK PK Order_Count integer(20) int FK PK PurchaseSubtotal integer(10) int FK PK Tax integer(6) int FK PK DeliveryFee integer(5) int FK PK PurchaseTotal integer(10) int FK PK Status varchar(10) int FK PK SpecialInstructions varchar(30) int FK PK EmailAddress varchar(40) int FK PK UserName varchar(20) int FK PK Password varchar(10) int FK PK Description varchar(50) int FK PK PhoneNumber integer(20) int FK PK Manufacturer varchar(10) int FK PK ZipCode integer(10) int FK PK ZipCode integer(10) int FK PK LastName varchar(25) int FK PK StreetAddress varchar(200) int FK PK ZipCode integer(10) int FK PK LastName varchar(25) int FK PK EmployeeID int FK PK M1 M2 M3 M4 M1 M2 M3 M4 attribute name int FK PK ProductID int FK PK EmployeeID int FK PK M1 M2 M3 M4 RoleID int FK PK M1 M2 M3 M4 M1 M2 M3 M4 Price integer(6) int FK PK M1 M2 M3 M4
customerPickersDriversPlace OrderOrder ItemsPrepare OrderDelivery ConfirmationDeliveryinformationOrder DetailsAccountInfomationShopping ListItemsAvailable stockBilling resultsInventoryBilling systemsMerchant Services
Grocery Order System customer Pickers Drivers Place Order Order Items Prepare Order Delivery Confirmation Delivery information Order Details Account Infomation Shopping List Items Available stock Billing results Inventory Billing systems Merchant Services M1 M2 M3 M4 M1 M2 M3 M4 M1 M2 M3 M4 M1 M2 M3 M4 M1 M2 M3 M4 M1 M2 M3 M4 M1 M2 M3 M4 M1 M2 M3 M4 M1 M2 M3 M4
:Customer:Picker:Driver:Grocery Order system:Inventory:Billing SystemPlace OrderShopping List ItemsAvailable StockOrder DetailsBilling ResultsDelivery ConfirmationDelivery InfomartionOrder ItemsPrepare Order
:Customer :Picker :Driver :Grocery Order system :Inventory :Billing System Place Order Shopping List Items Available Stock Order Details Billing Results Delivery Confirmation Delivery Infomartion Order Items Prepare Order
CustomerCheckoutBrowse InventoryAdd Product To CartCheck Delivery AvailibilityUse Case Diagram: (CIS) Customer Item SelectionE-Grocer Database
New folder/Course Project Report Group C - Milestone 2 v1.0.docx
Context level Diagram
Project Charter
Corner Market, Inc.
Project Charter
|
Project Title: E-Grocer Internet Project with Same-Day Delivery Service |
Project ID: |
|
Sponsoring Organization: |
Sponsor Representative: |
|
Prepared By: Group – C |
Version: 1 |
|
Project Authorization: November 2015 |
Project Category: Strategic |
|
Project Start Date: November 2015 |
Project Finish Date: December 2015 |
Project Description:
A new Web-based service from Corner Market, Inc. is proposed: Get same-day or overnight delivery on everything in the store (perishable and non-perishable items). The operations will be located inside company stores with the “storefront” being an area of the existing Corner Market retail website. A diverse team of professionals will design and test new technology and logistics capabilities for the new delivery service.
Business Need:
The delivery service will corner the market of consumers that may not have the means or time to go to the market for their essentials. This service is ‘forward-thinking’ and will help us to develop a strategic change in existing operations and result in major cost savings that could mean the difference between future market success and failure.
Company Strategic Plan:
Trial period for same-day and overnight delivery services will begin in a few select cities as a prototype. A number of new cities will be launched within two years from the present date.
Project Goal
Given the business need, the goal of our project is to continue to provide excellent customer service – albeit from a different method. We aim to do this by allowing consumers to shop their local Corner Market from the comfort of their home, office, etc. via our Website, and choose when and where they want delivery.
Measurable Objectives
In business terms, our objectives are to increase market share and revenues by 10%. This is obtainable by providing excellent customer service, a fully functioning and easy-to-use Webstore, and by providing the best prices to our customers.
Vision or Preliminary Scope of the Project
The vision, or preliminary scope, of the project will be to attract customers (whom may already be existing customers or not) to shop the store and create more business for Corner Market, Inc. The preliminary scope of the project will be to set up operations in a few major cities (i.e. Los Angeles, San Francisco, Chicago, New York) as a trial for public adoption, to iron out early issues with the new technology, inventory, and logistics capabilities.
Stakeholders:
Sponsor: Mark Spenser | Project Support
Program Manager: Susan Town | Project Oversight
Project Manager: Geoffrey Smith | Risk Management, Control, Tracking
Project Team: Anders Berg | [email protected]
Dannie Boncenor | [email protected]
Dixon Stapleton | [email protected]
Glenn Garrett | [email protected]
Senior Programmer: Tom Sawyer | System Architect
Business Analyst: Mark Twain | Application Services
Data Architect: Julia White | Data Services
Project Manager Responsibilities and Authority:
The project team reports to the project manager during the lifespan of the project. Semi-annual evaluations of project team members will be conducted by functional managers with input from the project manager.
Budget:
Corner Market, Inc. has allocated $75 million for new operating initiatives for the next two years (2016-2017). The majority of the costs of the project is through capital budget. No outsourcing is expected in this project.
Project Success Criteria:
The new service must meet all codes and specifications and should be completed on time with all equipment and computers ready to be deployed.
Risks:
Without the newly requested equipment and people, it will be impossible to develop this new service. Lower revenues and profits due to loss of market share, existing and new-to-market external competitors, and a slow adoption rate are also risks that should be considered.
|
Event |
Probability |
Impact |
Mitigation |
|
Requirement changes after project sign-off |
Low |
Increase of budget and delay of project |
Involve all stakeholders to provide input and requirements during analysis |
|
Inability to transfer current data to new platform |
Low |
New platform may not be used to full potential |
Hire experienced partner during installation |
|
Unexpected technical problems |
Medium |
Project delay |
Develop a contingency plan |
|
Budget constraint |
Low |
Project delay |
Raise more funding from sponsor |
|
Integration does not meet requirements |
Medium |
Customer service will be hampered, system may not be liked by staff |
Full system test before live deployment |
Assumptions and Constraints
Assumptions
· All personnel that are needed will be available to see the project to a successful completion
· Certified partner will assist Corner Market in a timely manner
· Project team will set appropriate goals for this project
· Security of customer data will be fully addressed
· No disastrous technological failures
· Organizational direction does not change during the project
· Courses needed to train key employees will be made available
· Funding will not be cut during the project
Constraints
· A limited budget has been set and need to balance the time to have optimum productivity.
·
Communication
The project stakeholders are our existing customer base, users, the project team, project sponsors, project champions, upper management, functional managers, the project manager, the project management office, suppliers, and members of the public who are potentially affected by the project. Corner Market, Inc. will document project activities and communicate with them during weekly meetings. Daily “stand-up” meetings will also be held to communicate pressing issues. The project will be approved by upper management, with power to make ongoing decisions being given to the project manager.
Approval
|
Approval Date: |
|
Project Manager: |
|
Project Sponsor(s): |
Name: Date:
______________________________________________________________
Name: Date:
______________________________________________________________
Name: Date:
______________________________________________________________
New folder/Course Project Report Group C - Milestone 3 v1.0.docx
Logical and Physical Data Flow Diagrams
Logical and Physical Entity Relationship Diagrams
Logical Entity Relationship Diagram
Physical Entity Relationship Diagram
CustomerCustomer1ShippingAvailibility2IdentifyItems3PriceLookup4Fill Cart5Compute Cost Of Order6Settle TransactionD1Shipping AreaD3Price CheckZip CodeItems To PurchaseItem IDAdd ToCartItems &PricesCompute CostPaymentReceiptLogical Data Flow Diagram- Use Case CIS
Customer Customer 1 Shipping Availibility 2 Identify Items 3 Price Lookup 4 Fill Cart 5 Compute Cost Of Order 6 Settle Transaction D1 Shipping Area D3 Price Check Zip Code Items To Purchase Item ID Add To Cart Items & Prices Compute Cost Payment Receipt Logical Data Flow Diagram- Use Case CIS
CustomerSettle Transaction:1. Collect money2. Display and send receipt (electronically)Input Zip CodeSearch For Items(Or Input Item ID)Calculated Cost to be PaidPayment TransferredPhysical Data Flow Diagram - Use Case CISDelivery AvailabilityView ItemAdd to CartReview CartAdd Quantity To CartRemove Quantity From CartCheckoutProceed to CheckoutSearch For Different Items Again1.Manage “Loyalty Programs”2. Re-order Essentials(Agree to Privacy and Terms of Service)1.Set Delivery Address2. Set Delivery Window3. Set Payment Method4. Add Promo CodeCompute Cost of OrderSelect QuantityPlace OrderShipping AreaTemporary Trans. FileItems and PricesItems, Prices, and SubtotalsCustomer InputCustomer InputCustomer
Customer Settle Transaction: 1. Collect money 2. Display and send receipt (electronically) Input Zip Code Search For Items (Or Input Item ID) Calculated Cost to be Paid Payment Transferred Physical Data Flow Diagram - Use Case CIS Delivery Availability View Item Add to Cart Review Cart Add Quantity To Cart Remove Quantity From Cart Checkout Proceed to Checkout Search For Different Items Again 1.Manage “Loyalty Programs” 2. Re-order Essentials (Agree to Privacy and Terms of Service) 1.Set Delivery Address 2. Set Delivery Window 3. Set Payment Method 4. Add Promo Code Compute Cost of Order Select Quantity Place Order Shipping Area Temporary Trans. File Items and Prices Items, Prices, and Subtotals Customer Input Customer Input Customer
CustomerOrderRoleProductStoreLocationEmployeeCustomerIDPKFirstNamevarchar(25)StreetAddressvarchar(200)OrderIDPKCustomerIDvarchar(50)FKCountinteger(20)RoleIDPKNamevarchar(10)ProductIDPKSKUinteger(20)Namevarchar(25)StoreLocationIDPKNamevarchar(25)StreetAddressvarchar(200)EmployeeIDPKFirstNamevarchar(25)PhoneNumberinteger(20)EmailAddressvarchar(40)PhoneNumberinteger(20)AltPhoneNumberinteger(20)Passwordvarchar(10)Order_Countinteger(20)PurchaseSubtotalinteger(10)Taxinteger(6)DeliveryFeeinteger(5)PurchaseTotalinteger(10)Statusvarchar(10)SpecialInstructionsvarchar(30)EmailAddressvarchar(40)UserNamevarchar(20)Passwordvarchar(10)Descriptionvarchar(50)PhoneNumberinteger(20)Manufacturervarchar(10)ZipCodeinteger(10)ZipCodeinteger(10)LastNamevarchar(25)StreetAddressvarchar(200)ZipCodeinteger(10)LastNamevarchar(25)EmployeeIDFKattribute nameProductIDFKEmployeeIDFKRoleIDFKPriceinteger(6)
Customer Order Role Product StoreLocation Employee CustomerID int FK PK FirstName varchar(25) int FK PK StreetAddress varchar(200) int FK PK OrderID int FK PK CustomerID varchar(50) int FK PK Count integer(20) int FK PK RoleID int FK PK Name varchar(10) int FK PK ProductID int FK PK SKU integer(20) int FK PK Name varchar(25) int FK PK StoreLocationID int FK PK Name varchar(25) int FK PK StreetAddress varchar(200) int FK PK EmployeeID int FK PK FirstName varchar(25) int FK PK PhoneNumber integer(20) int FK PK EmailAddress varchar(40) int FK PK PhoneNumber integer(20) int FK PK AltPhoneNumber integer(20) int FK PK Password varchar(10) int FK PK Order_Count integer(20) int FK PK PurchaseSubtotal integer(10) int FK PK Tax integer(6) int FK PK DeliveryFee integer(5) int FK PK PurchaseTotal integer(10) int FK PK Status varchar(10) int FK PK SpecialInstructions varchar(30) int FK PK EmailAddress varchar(40) int FK PK UserName varchar(20) int FK PK Password varchar(10) int FK PK Description varchar(50) int FK PK PhoneNumber integer(20) int FK PK Manufacturer varchar(10) int FK PK ZipCode integer(10) int FK PK ZipCode integer(10) int FK PK LastName varchar(25) int FK PK StreetAddress varchar(200) int FK PK ZipCode integer(10) int FK PK LastName varchar(25) int FK PK EmployeeID int FK PK M1 M2 M3 M4 M1 M2 M3 M4 attribute name int FK PK ProductID int FK PK EmployeeID int FK PK M1 M2 M3 M4 RoleID int FK PK M1 M2 M3 M4 M1 M2 M3 M4 Price integer(6) int FK PK M1 M2 M3 M4
New folder/Course Project Report Group C - Milestone 4 v1.0.docx
:Customer:Picker:Driver:Grocery Order system:Inventory:Billing SystemPlace OrderShopping List ItemsAvailable StockOrder DetailsBilling ResultsDelivery ConfirmationDelivery InfomartionOrder ItemsPrepare Order
:Customer :Picker :Driver :Grocery Order system :Inventory :Billing System Place Order Shopping List Items Available Stock Order Details Billing Results Delivery Confirmation Delivery Infomartion Order Items Prepare Order
customerPickersDriversPlace OrderOrder ItemsPrepare OrderDelivery ConfirmationDeliveryinformationOrder DetailsAccountInfomationShopping ListItemsAvailable stockBilling resultsInventoryBilling systemsMerchant Services
Grocery Order System customer Pickers Drivers Place Order Order Items Prepare Order Delivery Confirmation Delivery information Order Details Account Infomation Shopping List Items Available stock Billing results Inventory Billing systems Merchant Services M1 M2 M3 M4 M1 M2 M3 M4 M1 M2 M3 M4 M1 M2 M3 M4 M1 M2 M3 M4 M1 M2 M3 M4 M1 M2 M3 M4 M1 M2 M3 M4 M1 M2 M3 M4
New folder/MIS581 - Week Seven.pdf
MIS-581 Sys Analysis, Plng. & Control
Week 7 – Final Project & Final Exam
Course Project Overview
Final Project Paper - (200 points)
Final Exam Review – (240 points)
Final Project - System Proposal
1. Cover letter 2. Cover or title page of project 3. Table of contents 4. Executive summary (including recommendations) 5. Outline of system study (all milestone lab assignments) 6. Detailed results of the system study (deliverables from each
milestone lab assignment) 7. System alternatives (use system alternative assessment and
feasibility matrix in Doc Sharing.) 8. System analysts' recommendation (use system alternative
assessment and feasibility matrix in Doc Sharing.) 9. Proposal summary (summarize information into a PowerPoint
presentation.) 10. Appendices (assorted documentation as needed)
Final Exam Review Keywords to be aware of:
List and Describe, Describe, Illustrate, Define, Provide examples What? How? Who? Why?
Review the following topics and issues:
Role of the Systems Analyst SDLC Agile Approach Outsourcing COTS JAD Training Disaster Recovery Structure Walkthrough Conversion from old to new system Types of security Website traffic Output technology Pricing options Ajax Web based form User Interfaces HCI Data Flow Diagrams Physical and Logical Diagrams Data Dictionary Metadata Structural Records Based elements Derived elements Normalization Denormalization Database tables
