Running Head FINAL PROJECT PLAN1TECHNICAL PAPER FINAL PROJEC.docx

Running Head: FINAL PROJECT PLAN1
TECHNICAL PAPER: FINAL PROJECT PLAN6
Technical Paper: Final Project Plan
Marcos A. Ortiz Albino
CIS 510 - Advanced Systems Analysis and Design
Dr. Mark Cohen
Strayer University
December 13, 2015
Introduction
Especially for You Jewelers is a small jewelry company in a
college town. Over the last couple of years, it has experienced a
tremendous increase in its business. However, its financial
performance has not kept pace with its growth. Especially for
You Jewelers wants to increase repeat sales to its existing
customers; thus, it needs to develop a customer database. It also
wants to install a new direct sales and accounting system to help
solve the outlined problems. (Satzinger, Jackson, & Burd, 2012)
This is not a unique scenario; in fact it is all too common for
small businesses to experience this situation. The business
world is constantly changing in many ways, new consumer
devices, new services, and new technologies are always
emerging. In order to keep space with these changes, the way
organization developed software must also change. The
implementation and deployment of any new system is a set of
complex processes because they consist of so many
interdependent activities. Of the right strategies are

implemented, the benefits will outweigh the costs for these
deployments and Especially for You Jewelers will be able to
continue developing new systems for their daily processes.
In order to provide the answers to the research questions, the
technical paper will outline five expected business benefits that
Especially for You Jewelers Company might derive from a new
system. It will also propose at least five system capabilities for
the company. Furthermore, it will ascertain the three possible
scenarios in this new direct sales and accounting system. At
last, the paper will present a system vision document for
Especially for You Jewelers, detailing the overall vision or plan
for the new direct sales and accounting system.
Expected Business Benefits from New System
The reason for presenting the business benefits from a new
system are simple, to determine whether the benefits outweigh
the cost. Every company has its own culture, and the new
system must be in-line with it. Of course there is always a risk
of the new system not meeting specified norms, making it
virtually impossible to be deployed. The areas were Especially
for You Jewelers will most benefit from are:
· Reducing error rates through automated editing or validation:
When recording the amount a customer owes Especially for You
Jewelers, the total of the amount is recorded on the debit of the
accounts receivables. These accounts pose a major challenge to
management as they can turn out to be liabilities when the
customers fail to pay. This error can be overturned with the new
system since lost profits will be visible once more for the
organization
· Increasing market share in existing markets: Even though
Especially for You Jewelers is doing well in the market, the
employment of a new strategy always bids a good outcome for
the company. The strategy for inducing growth in existing
markets, with current products involves little risk since it
utilizes resources and capabilities the company already has. It
also is a strategy that is limited in that once the market is
saturated; a new strategy must be employed. (Bains, 2010)

· Reducing bad accounts or bad credit losses: The current
system, which is partly manual and partly automated, doesn’t
track accounts receivables sufficiently. (Strayer, 2015) The new
system will be fully automated, making it possible to keep daily
update records of both creditors and debtors.
· Increase repeat sales to its existing customers: the new system
will increase the sales figures since it will analyze charges and
payments made by the customers. This will be done to increase
the assets or decreasing their values depending on the service
offered and the payments charged.
· Enhancing cross-sales capabilities with existing markets:
because buyers increasingly demand a tailored solution to their
needs (Ledingham, Kovac, Heric, & Montaville, 2013), this new
system will enhance cross-sales capabilities. Customers will be
able to compare products bought from Especially for You
Jewelers with other stores in the area. Buyers will be able to
gather basic information about the various products the
company has to offer.
System Capabilities for the Company
The system capabilities for the new system will help support the
proposed business benefits. These capabilities focus on the
system itself and are as follows:
· Provides a shopping cart capability: this future will support
customer sales with high automation, it will also recommend
related product purchase and comparison shopping and allows
customer ratings and recommendations.
· Provide customer account and billing capability: the new
feature will provide individualized customer account, support
electronic billing and payments and accumulate customer points
and allow for transfer and sharing.
· Market functions for promotions and specials: this feature will
provide flexible promotions and sales and it will accumulate
and track points from suppliers directly to customers.
· Produce daily profit and loss reports: this feature will allow
creating reports for making management decisions about the
different offering available in Especially for You Jewelers.

· Report on cost data for inventory items: this feature will allow
for better handling of inventory items. It will give a general
idea of items that are over inventoried and those who are in
high demand to successfully and efficiently manage the
inventory.
Scenarios in New System
Standard Order
The standard order is the process that shows the one-time
customer demand for products inside the standard delivery and
the accounting parameters. This scenario manages the following
activities:
· Helping the customer decide what to buy
· Processing customer orders
· Coordinating distribution and associated logistics
· Producing customer invoices
This scenario integrates the order handling activities with the
workflow of the downstream delivery and the logistics
operations. This scenario is used by Especially for You
Jewelers.
Contract Handling and Scheduling Agreements
This scenario varies in the way customers can specify delivery
quantities and the dates but are same in coordinating delivery
and in producing invoices. These scenarios integrate the
activities of the customer management with the workflow
related with the downstream delivery and logistic functions. The
appropriate cash management, accounts receivable and the
profitability systems are u-to-date.
Third Party Order Handling
Third party direct sales arrangements leverage the relations
between the company and their customers. By controlling
customer service activities and associated accounts receivable
operations, a surviving framework is used to give the flow of
the services and the products to the customer even when they
are not normally sold or produced by the company. The business
process scenario for the third party handling is presented by the
third party order processing scenario. The third party scenario

starts by recording the sales activities with the customers like
phone calls and the presentation of the jeweler.
The system makes the purchase demand detailing the products,
quantities and the dates of delivery. This purchase demand is
related with the known resources of the supply. The delivery to
the customer has been full and the invoice of the supplier
processed, billing is taken out for the third party order. The
additional activities in this scenario involve the customer credit
and the debit notes and the processing of the superior vendors
management.
Especially for You Jewelers System Vision Document
Introduction
Over the last few years, Especially for You has experience a
growth in their business. However, its financial performance
has not kept pace with its growth. The current system is
partially manual and automated, but it does not track account
receivables sufficiently. For this reason, the company is having
a difficult time why receivables. The company performs
specials to atrack customers but has no ideas if these are
profitable.
Business Needs
The company requires enhancing their business. Its financial
performance has not kept pace with its growth. The recent
system, does not track the accounts receivable and they want to
increase their sales, they need a customer database for this. It
also needs to install the new direct sales and the accounting
system to help resolve the outlined difficulties.
Solution
overview
The proposed solution will provide costumer account and billing

capabilities, provide a shopping cart, provide flexible
promotions and sales, include comprehensive order fulfillment
and provide individualized customer accounting.
Major Features
The major features of the new system are that it will reduce
error rates through automated editing and validation, will
increase market share in existing markets, will reduce bad
accounts or bad credit losses, will increase repeated sales to its
existing customers, and will enhance cross-sales capabilities
with existing markets.
Scope and Limitations
The scope of this document is limited to the coordination and
facilitation of a new sales and accounting systems requests
between customer and the company
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:
examples
Review the following topics and issues:
ole of the Systems Analyst
s

UML Class Diagram
UML Sequence Diagram

: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
Logical and Physical Data Flow Diagrams

Logical and Physical Entity Relationship Diagrams
Logical Entity Relationship Diagram
Physical Entity Relationship Diagram
CustomerCustomer1ShippingAvailibility2IdentifyItems3PriceLo
okup4Fill 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
CustomerOrderRoleProductStoreLocationEmployeeCustomerID
PKFirstNamevarchar(25)StreetAddressvarchar(200)OrderIDPKC
ustomerIDvarchar(50)FKCountinteger(20)RoleIDPKNamevarch
ar(10)ProductIDPKSKUinteger(20)Namevarchar(25)StoreLocati
onIDPKNamevarchar(25)StreetAddressvarchar(200)EmployeeID
PKFirstNamevarchar(25)PhoneNumberinteger(20)EmailAddress
varchar(40)PhoneNumberinteger(20)AltPhoneNumberinteger(20
)Passwordvarchar(10)Order_Countinteger(20)PurchaseSubtotali
nteger(10)Taxinteger(6)DeliveryFeeinteger(5)PurchaseTotalinte
ger(10)Statusvarchar(10)SpecialInstructionsvarchar(30)EmailAd
dressvarchar(40)UserNamevarchar(20)Passwordvarchar(10)Desc
riptionvarchar(50)PhoneNumberinteger(20)Manufacturervarchar
(10)ZipCodeinteger(10)ZipCodeinteger(10)LastNamevarchar(25
)StreetAddressvarchar(200)ZipCodeinteger(10)LastNamevarcha
r(25)EmployeeIDFKattribute
nameProductIDFKEmployeeIDFKRoleIDFKPriceinteger(6)
Customer
Order

Role
Product
StoreLocation
Employee
CustomerID
int
FK
PK
FirstNamevarchar(25)
int
FK
PK
StreetAddressvarchar(200)
int
FK
PK
OrderID
int
FK
PK
CustomerIDvarchar(50)
int
FK
PK
Countinteger(20)

int
FK
PK
RoleID
int
FK
PK
Namevarchar(10)
int
FK
PK
ProductID
int
FK
PK
SKUinteger(20)
int
FK
PK
Namevarchar(25)
int
FK
PK
StoreLocationID
int

FK
PK
Namevarchar(25)
int
FK
PK
int
FK
PK
EmployeeID
int
FK
PK
int
FK
PK
PhoneNumberinteger(20)
int
FK
PK
EmailAddressvarchar(40)
int
FK

PK
int
FK
PK
AltPhoneNumberinteger(20)
int
FK
PK
Passwordvarchar(10)
int
FK
PK
Order_Countinteger(20)
int
FK
PK
PurchaseSubtotalinteger(10)
int
FK
PK
Taxinteger(6)
int
FK
PK

DeliveryFeeinteger(5)
int
FK
PK
PurchaseTotalinteger(10)
int
FK
PK
Statusvarchar(10)
int
FK
PK
SpecialInstructionsvarchar(30)
int
FK
PK
int
FK
PK
UserNamevarchar(20)
int
FK
PK
Passwordvarchar(10)

int
FK
PK
Descriptionvarchar(50)
int
FK
PK
int
FK
PK
Manufacturervarchar(10)
int
FK
PK
ZipCodeinteger(10)
int
FK
PK
ZipCodeinteger(10)
int
FK
PK
LastNamevarchar(25)
int

FK
PK
int
FK
PK
ZipCodeinteger(10)
int
FK
PK
LastNamevarchar(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
Priceinteger(6)
int
FK
PK
M1
M2
M3
M4
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:
_____________________________________________________
_________

28
Course Project Report
MIS-581
e-Grocer System Analysis
Group C
Anders Berg
Glenn Garrett
Dixon Stapleton
Ydannie Boncenor

Professor Masullo
December, 2015

Table of Contents
Statement of the Business Problem (System Request Form)3
2. Business Requirements3
3.Context Level Data Flow Diagram (Visio)5
4.Use CASE List (normal business activities/work flows)6
5Use CASE Diagram (Visio)10
6. Use CASE Scenarios Case ID: CIS (Description or
narrative of steps in each use case)14
7. Project Charter18
8. Logical and Physical Data Flow Diagrams22
9. Logical and Physical Entity Relationship Diagrams24
10. UML Use Case Diagram26
11. UML Class Diagram27
11. UML Sequence Diagram28

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
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 Requirements1. 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 CDate: 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
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
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
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
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 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
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
Post-condition
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
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

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
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
Delivery Service
Project ID:
Version: 1

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:
_____________________________________________________
_________
Logical and Physical Data Flow Diagrams

Logical and Physical Entity Relationship Diagrams
Logical Entity Relationship Diagram
Physical Entity Relationship Diagram
UML Use Case 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
CustomerCustomer1ShippingAvailibility2IdentifyItems3PriceLo
okup4Fill 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
CustomerOrderRoleProductStoreLocationEmployeeCustomerID
PKFirstNamevarchar(25)StreetAddressvarchar(200)OrderIDPKC
ustomerIDvarchar(50)FKCountinteger(20)RoleIDPKNamevarch
ar(10)ProductIDPKSKUinteger(20)Namevarchar(25)StoreLocati
onIDPKNamevarchar(25)StreetAddressvarchar(200)EmployeeID
PKFirstNamevarchar(25)PhoneNumberinteger(20)EmailAddress
varchar(40)PhoneNumberinteger(20)AltPhoneNumberinteger(20
)Passwordvarchar(10)Order_Countinteger(20)PurchaseSubtotali
nteger(10)Taxinteger(6)DeliveryFeeinteger(5)PurchaseTotalinte
ger(10)Statusvarchar(10)SpecialInstructionsvarchar(30)EmailAd
dressvarchar(40)UserNamevarchar(20)Passwordvarchar(10)Desc
riptionvarchar(50)PhoneNumberinteger(20)Manufacturervarchar
(10)ZipCodeinteger(10)ZipCodeinteger(10)LastNamevarchar(25

)StreetAddressvarchar(200)ZipCodeinteger(10)LastNamevarcha
r(25)EmployeeIDFKattribute
nameProductIDFKEmployeeIDFKRoleIDFKPriceinteger(6)
Customer
Order
Role
Product
StoreLocation
Employee
CustomerID
int
FK
PK
int
FK
PK
int
FK
PK
OrderID
int
FK
PK

CustomerIDvarchar(50)
int
FK
PK
Countinteger(20)
int
FK
PK
RoleID
int
FK
PK
Namevarchar(10)
int
FK
PK
ProductID
int
FK
PK
SKUinteger(20)
int
FK
PK
Namevarchar(25)

int
FK
PK
StoreLocationID
int
FK
PK
Namevarchar(25)
int
FK
PK
int
FK
PK
EmployeeID
int
FK
PK
int
FK
PK
int

FK
PK
int
FK
PK
int
FK
PK
AltPhoneNumberinteger(20)
int
FK
PK
Passwordvarchar(10)
int
FK
PK
Order_Countinteger(20)
int
FK
PK
PurchaseSubtotalinteger(10)
int
FK

PK
Taxinteger(6)
int
FK
PK
DeliveryFeeinteger(5)
int
FK
PK
PurchaseTotalinteger(10)
int
FK
PK
Statusvarchar(10)
int
FK
PK
SpecialInstructionsvarchar(30)
int
FK
PK
int
FK
PK

UserNamevarchar(20)
int
FK
PK
Passwordvarchar(10)
int
FK
PK
Descriptionvarchar(50)
int
FK
PK
int
FK
PK
Manufacturervarchar(10)
int
FK
PK
ZipCodeinteger(10)
int
FK
PK
ZipCodeinteger(10)

int
FK
PK
LastNamevarchar(25)
int
FK
PK
int
FK
PK
ZipCodeinteger(10)
int
FK
PK
LastNamevarchar(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
Priceinteger(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
17
Course Project Report - Milestone 1
MIS-581
Group C
Anders Berg
Glenn Garrett

Dixon Stapleton
Ydannie Boncenor
Professor Masullo
November, 2015

Table of Contents
Business Requirements5
3.Use CASE Diagram (Visio)10
4.Use CASE Scenarios (Description or narrative of steps in each
use case)14

Project Sponsor:
Name:

deployment.
Customer
As a Customer
As a Customer
order
As a Customer
I want to checkout
As a Customer
As a Customer

will be delivered
As a Customer
Picker
As a Picker
As a Picker
Driver
As a Driver
delivery
As a Driver

the order
Administrator
As an Administrator
As an Administrator
As an Administrator
Business Benefits:

market.
Special Issues or Constraints:Business Requirements1. Context
Level Data Flow Diagram (Visio)
USE CASE LISTS
Version: 2.0
USE CASE NAME:
USE CASE TYPE
USE CASE ID:
CIS
Abstract:
PRIORITY:

Extension:
INVOKED BY:
Customer
Customer
DESCRIPTION:
PRE-CONDITION:
TYPICAL COURSE
OF EVENTS:

ALTERNATE COURSES:
POST-CONDITION:
USE CASE NAME:
USE CASE TYPE
USE CASE ID:
CPP
Abstract:
PRIORITY:
Extension:
INVOKED BY:
e-Grocer System

PayPal, etc.),
DESCRIPTION:
PRE-CONDITION:
TYPICAL COURSE
OF EVENTS:
online
payment status

ALTERNATE COURSES:
POST-CONDITION:
USE CASE NAME:
USE CASE TYPE
USE CASE ID:
OPP
Abstract:
PRIORITY:

Extension:
INVOKED BY:
e-Grocer System
DESCRIPTION:
ready for delivery
PRE-CONDITION:
TYPICAL COURSE
OF EVENTS:
carriers

ALTERNATE COURSES:
POST-CONDITION:
USE CASE NAME:
USE CASE TYPE
USE CASE ID:
DCH
Abstract:

PRIORITY:
Extension:
INVOKED BY:
e-Grocer System
DESCRIPTION:
PRE-CONDITION:
TYPICAL COURSE
OF EVENTS:

ALTERNATE COURSES:
POST-CONDITION:
customer home

E-Grocer System
Customer
Checkout
Browse Inventory
Add Product To Cart
E-Grocer
Database
Status
E-Grocer System
Customer
Order Status
Payment Approved
Payment Declined
Payment Choice

And Information
Payment Processor
Payment Status
Picking/Packing
E-Grocer System
E-Grocer Associate
Stock Items Picked
Delivery Driver
Assigned & Notified
Out of Stock /
Non Inventory Items
Order and Gathered
Delivery Carrier

Cold Storage
Ready For Delivery
E-Grocer
Database
Order Approved
Items Received
Order Complete

I WILL BE IN CHARGE OF THE COVER LETTER ,
EXECUTIVE SUMMARY AND OUTLINE OF SYSTEM
STUDY
1. Cover letter
presentation.)
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/1.docx
I WILL BE IN CHARGE OF THE COVER LETTER ,
EXECUTIVE SUMMARY AND OUTLINE OF SYSTEM
STUDY

1. Cover letter
presentation.)
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
Group C
Anders Berg
Glenn Garrett
Dixon Stapleton
Ydannie Boncenor

Professor Masullo
November, 2015
Table of Contents
Business Requirements5
3.Use CASE Diagram (Visio)10
4.Use CASE Scenarios (Description or narrative of steps in each
use case)14

Project Sponsor:
Name:

deployment.
Customer
As a Customer
As a Customer
order

As a Customer
I want to checkout
As a Customer
As a Customer
will be delivered
As a Customer
Picker
As a Picker
As a Picker

Driver
As a Driver
delivery
As a Driver
the order
Administrator
As an Administrator
As an Administrator

As an Administrator
Business Benefits:
market.
Special Issues or Constraints:Business Requirements
1. Context Level Data Flow Diagram (Visio)

USE CASE LISTS
Version: 2.0
USE CASE NAME:
USE CASE TYPE
USE CASE ID:
CIS
Abstract:
PRIORITY:
Extension:
INVOKED BY:
Customer
Customer
DESCRIPTION:
PRE-CONDITION:

TYPICAL COURSE
OF EVENTS:
ALTERNATE COURSES:
POST-CONDITION:

USE CASE NAME:
USE CASE TYPE
USE CASE ID:
CPP
Abstract:
PRIORITY:
Extension:
INVOKED BY:
e-Grocer System
PayPal, etc.),
DESCRIPTION:
PRE-CONDITION:
TYPICAL COURSE
OF EVENTS:

online
payment status
ALTERNATE COURSES:
POST-CONDITION:

USE CASE NAME:
USE CASE TYPE
USE CASE ID:
OPP
Abstract:
PRIORITY:
Extension:
INVOKED BY:
e-Grocer System
DESCRIPTION:
ready for delivery

PRE-CONDITION:
TYPICAL COURSE
OF EVENTS:
carriers
ALTERNATE COURSES:

POST-CONDITION:
USE CASE NAME:
USE CASE TYPE
USE CASE ID:
DCH
Abstract:
PRIORITY:
Extension:
INVOKED BY:
e-Grocer System
DESCRIPTION:

PRE-CONDITION:
TYPICAL COURSE
OF EVENTS:

ALTERNATE COURSES:
POST-CONDITION:
customer home

Use Case Name
Trigger Event
Description

Actors
Pre-condition
Post-condition
Flow of Activities
availability

Use Case Name
Trigger Event
Description
Actors
Customer
Pre-condition
information
Post-condition
Flow of Activities

Use Case Name
Trigger Event

Description
to pull
Actors
Pre-condition
Post-condition
Flow of Activities
order

Use Case Name
Trigger Event
Description
Actors
Driver, Customer

Pre-condition
Post-condition
Flow of Activities
delivery
vehicle
E-Grocer System

Customer
Checkout
Browse Inventory
Add Product To Cart
E-Grocer
Database
Status
E-Grocer System
Customer
Order Status
Payment Approved
Payment Declined
Payment Choice
And Information
Payment Processor

Payment Status
Picking/Packing
E-Grocer System
E-Grocer Associate
Stock Items Picked
Delivery Driver
Assigned & Notified
Out of Stock /
Non Inventory Items
Order and Gathered
Delivery Carrier
Cold Storage
Ready For Delivery

E-Grocer
Database
Order Approved
Items Received
Order Complete
New folder/Course Project Report Group C - Milestone 1-4
v4.2.docx
28

MIS-581
Group C
Anders Berg
Glenn Garrett
Dixon Stapleton
Ydannie Boncenor

Professor Masullo
December, 2015
Table of Contents

2. Business Requirements3
5Use CASE Diagram (Visio)10
6. Use CASE Scenarios Case ID: CIS (Description or
narrative of steps in each use case)14
7. Project Charter18
8. Logical and Physical Data Flow Diagrams22
9. Logical and Physical Entity Relationship Diagrams24
10. UML Use Case Diagram26
11. UML Class Diagram27
11. UML Sequence Diagram28

Project Sponsor:
Name:

deployment.
Customer
As a Customer
As a Customer

order
As a Customer
I want to checkout
As a Customer
As a Customer
will be delivered
As a Customer
Picker
As a Picker

As a Picker
Driver
As a Driver
delivery
As a Driver
the order
Administrator
As an Administrator
As an Administrator

As an Administrator
Business Benefits:
market.
Special Issues or Constraints:Business Requirements
1. Context Level Data Flow Diagram (Visio)
USE CASE LISTS

Version: 2.0
USE CASE NAME:
USE CASE TYPE
USE CASE ID:
CIS
Abstract:
PRIORITY:
Extension:
INVOKED BY:
Customer
Customer
DESCRIPTION:
PRE-CONDITION:
TYPICAL COURSE
OF EVENTS:

ALTERNATE COURSES:
POST-CONDITION:
USE CASE NAME:

USE CASE TYPE
USE CASE ID:
CPP
Abstract:
PRIORITY:
Extension:
INVOKED BY:
e-Grocer System
PayPal, etc.),
DESCRIPTION:
PRE-CONDITION:
TYPICAL COURSE
OF EVENTS:
online

payment status
ALTERNATE COURSES:
POST-CONDITION:

USE CASE NAME:
USE CASE TYPE
USE CASE ID:
OPP
Abstract:
PRIORITY:
Extension:
INVOKED BY:
e-Grocer System
DESCRIPTION:
ready for delivery
PRE-CONDITION:
TYPICAL COURSE
OF EVENTS:

carriers
ALTERNATE COURSES:
POST-CONDITION:

USE CASE NAME:
USE CASE TYPE
USE CASE ID:
DCH
Abstract:
PRIORITY:
Extension:
INVOKED BY:
e-Grocer System
DESCRIPTION:
PRE-CONDITION:
TYPICAL COURSE
OF EVENTS:

ALTERNATE COURSES:
POST-CONDITION:
customer home

Use Case Name
Trigger Event
Description
Actors
Pre-condition
Post-condition
Flow of Activities
availability

Use Case Name
Trigger Event
Description
Actors
Customer
Pre-condition

information
Post-condition
Flow of Activities

Use Case Name
Trigger Event
Description
to pull
Actors
Pre-condition
Post-condition
Flow of Activities
order

Use Case Name
Trigger Event
Description
Actors

Driver, Customer
Pre-condition
Post-condition
Flow of Activities
delivery
vehicle

Corner Market, Inc.Project Charter
Delivery Service
Project ID:
Version: 1
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.

Running Head FINAL PROJECT PLAN1TECHNICAL PAPER FINAL PROJEC.docx

Running Head FINAL PROJECT PLAN1TECHNICAL PAPER FINAL PROJEC.docx

Recommended

Recommended

More Related Content

Similar to Running Head FINAL PROJECT PLAN1TECHNICAL PAPER FINAL PROJEC.docx

Similar to Running Head FINAL PROJECT PLAN1TECHNICAL PAPER FINAL PROJEC.docx (16)

More from charisellington63520

More from charisellington63520 (20)

Recently uploaded

Recently uploaded (20)

Running Head FINAL PROJECT PLAN1TECHNICAL PAPER FINAL PROJEC.docx