Final Project

The Richmond Millennial Chocolatier Company
Systems Analysis and Design
Section: 001
Spring 2016
Jamie Ricks

2
Table of Contents
Brief Description of the Project 3
Executive summary 4
System Request 5
Team Charter 8
Business Case: Feasibility Analyses 12
Cost & Benefits Analysis 16
Use-case Diagram 17
Primary Use-Cases Descriptions 18
Primary Actors Descriptions 28
Non-Functional Requirements 31
Class Diagram 32
Class Descriptions 33
Sequence Diagrams 39
Object Descriptions 41
State Machine Diagram 42
State Descriptions: Customer Order 44
State Descriptions: Product Item 45
User Interface Prototype Screens 46
Usability Test Report 51
Complete Gantt Chart 52

3
Brief Description of the Project
The Richmond Millennial Chocolatier Company information
system development project is a system that is easy to learn,
access, and use. The purpose of the system is to allow
customers purchase our product online and in the store. Also,
allow employees to process customers’ orders. The general
requirements for this system are to process inventory, orders,
payments, customers’ profiles, etc. In order to manage
inventory, the system will need to have the ability to manage
recipes, track supplies, and damage supplies. The system’s
capabilities to manage the work flow of employees by keeping
track of employees, employees’ hours, and schedule. The last
requirement for the information system would be having the
ability to create management reports. What is included in the
scope of development project are the feasibility and
cost/benefit analyses, class diagram, sequence diagrams, state
machine diagrams, user interface prototype screens, usability
test report, and Gantt chart.

4
Executive summary
We formed a group called The Rams. We wrote a team
charter, which is a contract regarding requirements and
responsibilities. We begin to construct a business case with
feasibility studies to show where the information system
would be technical, economical, and organizational. After doing
the feasibility studies, we did a cost and benefit analysis test to
see the return on investment, which was 33%. We developed a
use case diagram to show the actions that actor(s) would
perform within the system. After developing the use case
diagram, we use the classes of the use case to create a class
diagram to describe the attributes and their methods. My team
created a sequence diagram to show the process in filling and
placing on online order in a time sequence. After creating a
sequence diagram, we develop a state machine to show the
condition of a customer order and product item. Completing all
the diagram, we begin to sketch a user interface prototype
screens and a usability test to see what customers think about
the website far as visuals, user friendly, and easy access.
The Richmond Millennial Chocolatier Company
information system development project is plan and layout to
do the internal and external design. There are no
recommendation and suggestions for improvements to the
system once the original user requests have been
implemented.

5
System Request
Project Name: The Richmond Millennial Chocolatier Company
Project Sponsor: Coco Caramel (Chocolatier Entrepreneur)
Coco Caramel has decided that she wants to make a career change and venture out
as a chocolatier entrepreneur. She has always had a flair for anything chocolate
when it comes to desserts and has spent most of her free time inviting close friends
and associates to chocolate parties when she wasn’t busy consulting with Fortune
500 companies to help them resolve their complex IT problems. Over the last 15
years working in IT, she has developed professional associations with a number of
very successful CEOs and entrepreneurs. A group of these associates has offered to
provide the initial funding necessary to help get her up and running as a chocolatier
and she has decided to accept the challenge. The first thing they have asked her to
do is create a business plan that will help assure them that she is capable of
understanding how to make this new business a success.
Business Need: To generate a level of sales through brick-and-mortar and virtual
store fronts and to lower the cost of business operations by enabling effective and
efficient business processes for customer ordering processing and inventory
management; to manage employee work schedules, and to create management
reports that will enable the business to make better decisions to create a
competitive advantage.
Functionality: The information system should allow customers to:
 Purchase products in-store and through an Internet store website; this would
include the ability to:
o View images of current product inventory through an Internet store
website.
o Display full product description.
o Check availability of inventory.
o Select delivery option (in-store pickup or delivery service)
o Confirm and track Internet orders.
o Determine delivery cost and date.
o Provide customer delivery tracking identification number.
o Specify customized products (special orders).
o Confirm custom order within 24 hours.
o Generate customer order invoice
o Accommodate payment by micro payment system (credit & debit
card) such as PayPal.
o Keep track of customer order profiles (customer or employee
created—add/modify/delete)

6
 Manage Product Inventory to include the ability to:
o Track all supply ingredient quantities (add/update/delete quantities)
o Manage all product recipes (ingredient batch quantities)
o Generate supply acquisition orders
o Send order payment
o Track damaged supplies
 Manage Employee Schedules
o Add/update/remove employees
o Create employee work schedules
o Track employee work hours
 Generate Management Reports
o Create production reports
o Create employee work reports
o Create sales reports
o Create inventory reports
o Create customer reports
Business Value:
Tangible:
 Gross customer order sales of $400,000 during the first year of operations
 Keep inventory supplies’ costs @ or below $150,000
 Keep employee costs @ or below $100,000
 Keep Website costs @ or below $12,000
Intangible:
 Maximize customer base
 Promote business
 Develop store/product brand
 Create high customer satisfaction
 Create excellent customer service
 Know customer base
 Know product demand
 Intelligent management reporting system
 Develop excellent supply chain relationships
Special Issues or Constraints:
 Lead time for specialty products & custom orders
 Determine competition
 Timely implementation—by summer season
 Determine IT hardware, software, and communication systems
requirements
 Determine Website hosting responsibilities
 Dedicated operation’s location (brick-and-mortar)

7
 Determine overhead costs of facilities & required human resource
requirements
 Establish work schedule
 Provide for warehousing and inventory control (expiration dates are
important for ingredients)
 Establish secure payment service
 Establish delivery service contracts (FedEx, UPS, USPS)
 Establish link to accounting service
 Create Business Case for Investment Group
 Kitchen equipment
 Brick-and-mortar store location

8
Team Charter
Members:
 Margherita Marannano
marannanom@vcu.edu
(804) 239-0210
 Jamie Ricks
ricksjv@vcu.edu
(757) 304-1429
 Yolibeth Benitez
Benitezy2@vcu.edu
(804) 338-5294
 Patrick Llamas
llamasp@vcu.edu
(804) 123-4567
 Zainab Bakarr Kamara
kamarazb@vcu.edu
(804) 939-9946
Team Leader:
Team leads will rotate throughout the semester.
Strengths and Weaknesses:
Strengths
 Knowledge from previous business coursework
 Ability to use various business related software and statistical tools
 Previous experience working in groups settings
 Strong communicators.
 Computer savvy
Weaknesses
 Time constraints
 Limited synchronized team availability
 Limited previous knowledge on systems analysis and design
 Unfamiliar with chocolatier industry

9
Roles and Responsibilities
Leader/Accountability Lead I: Responsible for assigning work to each member and holding
each member accountable for completing their assignments.
Accountability Lead II: Responsible for holding each member accountable for completing
their assignments and submits them to Editor.
Editor: Responsible for receiving and editing all assignments from Accountability Lead II for
content, clarity, and grammar.
Deadline Lead: Responsible for collecting all completed and edited assignments from the
Editor to insure they are submitted on time.
Final Submission Lead: Responsible for receiving and double checking all assignments
received from the Deadline Lead. Responsible for submitting all work through Blackboard.
Individual Contributions to Team:
 Jamie: Responsible for creating spreadsheets for documents and any additionally
assigned work on time.
 Patrick: Responsible for holding each team member accountable for completing their
work and doing so in a timely fashion. Any additionally assigned work.
 Margherita: Responsible for assignment completion accountability and acting as
Person-of-Contact for all completed and submitted work. Reminders will be sent via text
message or email. Any additionally assigned work.
 Yolibeth: Responsible for reserving conference rooms for meetings and notifying team
members of the location and time. Any additionally assigned work.
Meeting Times:
Meeting will be held on Fridays from 10am to 12pm throughout the semester. Additionally,
team members will occasionally hold Skype conference sessions as needed.

10
Rules and Expectations:
 All team members are expected to complete their assigned work to meet
deadlines.
 All team members are expected to be in attendance for all group meetings/skype
conferences unless previously discussed with team members.
 All team members are expected to communicate with group members to ensure
each member is updated on what is occurring with assignments and logistics of
the project.
 All team members are expected to effectively contribute to team meetings,
conferences, and assignments.
Code of Ethics:
 Each member is accountable for their work.
 Positive and fluid communication
 Punctual
 Freedom to voice opinions and an open space to constructively discuss opinions.
Biographies:
Yolibeth Benitez was born in El Salvador. She moved to the United States when she was 9
years old. She speaks and writes in both Spanish and English fluently. Her parents own three
Latino markets and a restaurant in the city and she has worked in the family business her
whole life. She looks forward to exploring other horizons after she graduates.
Margherita Marannano speaks English and Italian Fluently. She has have worked at a local
Italian restaurant in the south side of Richmond since she was 14. Since working at this
restaurant she has received 4 promotions. She will graduate with a degree om Business
Administration and Management in May 2016. Though she enjoys being a waitress and
working in the food industry, she is looking forward to utilizing the skills she has learned
through the business school in real life settings.
Jamie Ricks was born in Franklin, VA and moved to Chesterfield, VA after she graduated high
school. In the fall of 2012, she attended John Tyler Community College, where she earned an
associate’s degree in Business Administration. She began attending Virginia Commonwealth
University in the spring of 2015, where she is currently double majoring in Accounting and
Information Systems. She also participates in living and learning program called “VCU Lead.”

11
Patrick Byrum was born in Washington, DC and moved to Fairfax County, Virginia when he
was 4 years old. After high school, he attended Christopher Newport University and after a
year transferred to Northern Virginia Community college. His final step towards graduation is
exceling in his final courses at Virginia Commonwealth University.
Signatures of Agreements: I have read, understand, and agree to the terms, rules, conditions,
and expectations defined in The Rams Team Charter.
Yolibeth Benitez: ___________Yolibeth Benitez_______________________________
Margherita Marannano: ______Margherita Marannano________________________
Jamie Ricks: __________________Jamie Ricks______________________________
Patrick Byrum: _____________Patrick Bynum________________________________

12
Business Case: Feasibility Analyses
Statement of Purpose
Coco Caramel has a passion to build a chocolatier business that offers gourmet and
specialty chocolates. For the last several years, she has hosted chocolatier festivities
for her friends and colleagues. These events have given her confidence and the
necessary experience to pursue her current business venture of establishing her
own chocolatier company.
After working as an information technology professional for the past 15 years, Coco
Caramel understands the importance of a well-designed information system to
effectively run her business. After careful review of our technical, economic, and
operational feasibility analyses, we believe Coco Caramel can obtain the necessary
capital she needs to establish The Richmond Millennial Chocolatier Company and
implement an effective information system to insure the smooth functionality of
day-to-day business demands. An effective system will allow The Richmond
Millennial Chocolatier Company the ability to:
 Track inventory to prevent overproduction and allow customers to view
products that are available for ordering and/or pickup
 Perform customer service and sales analytics to meet the demands of
customers and determine cost-effective ways to improve the business
 An inventory indicator that reports when supplies are low and connects
directly to suppliers to process new orders
 Process online orders and a system to track deliveries
Scope Statement
To establish a chocolatier company effectively to produce profits, the information
system needs to be able to manage employee work schedules, customer requests,
supply ordering/ inventory, and reports. Additional functions include tracking
business costs such as rent, utilities, employee wages/salaries, inventory,
equipment/maintenance, business insurance, professional fees (accountants,
consultants, etc.), advertising costs, and one-time developmental costs.
Technical Feasibility Study
There is high familiarity with the creation of the product including the necessary
materials, required labor, and process of making chocolate. Since it is Coco
Caramel’s first time establishing a chocolatier company, there is low familiarity on
the day-to-day running of the business. The Richmond Millennial Chocolatier
Company will begin as a medium project with aspirations of it growing
exponentially. Since it will be a retail store, customers will have the opportunity to
experience and sample the product before making purchases. This will assist in the
growth of the business by allowing customers to enjoy the product and share their
positive experiences with their peers.

13
Technical Risks
 Computer System failure (High): This would be resolved by continuous
technical support from The Signature Group.
 Loss of internet connection (Low): Use of a reputable internet provider
(Verizon) and implementation of a backup information system that tracks
the most recent inventory and allows orders to be made without the use of
the main system.
 Machinery breakdown (Medium): This would be resolved by manually
preparing the chocolate.
 Unsynchronized onsite and online inventory (low)- This issue will be
addressed by communicating to the customer about the malfunction and
working extra hours to prepare the needed inventory to maintain customer
satisfaction. The Signature Group would also be contacted to address the
system malfunction.
Economic Feasibility
We have projected a financial loss during the first year of business due to the high
development and operational costs, which include the purchase of the necessary
computer hardware (backup computer and POS system). Kitchen appliances and
machinery will also be purchased and other initial costs listed in our attached cost
and benefits analysis.
We project that The Richmond Millennial Chocolatier Company will break even in
the beginning of the second year of operation (Refer to Cost & Benefit Analysis). The
projected growth for the following three years will be a steady growth in revenue
(average of net profit growth each year). Payments towards the $36,000 loan
(including 15% interest) will be made after the first year of business. Payments will
be made over a period of 24 months.
Risk Assessment
 Low Revenue and not accruing adequate revenue to cover operational costs
(High): This will be resolved by seeking alternative ways of producing
income, such as partnerships with other businesses that will sell the product.
Offering internship programs will also provide local students with
knowledge in the chocolatier business in exchange of free labor, which will
decrease the cost of wages.
 Bad publicity (Medium): This will be handled by maintaining excellent
customer service as a core value and always providing a good quality
product. Use of review sites such as Yelp, Google Reviews, and Facebook will
also be implemented to interact directly with satisfied customers to thank
them for their business and unsatisfied customers so their concerns can be
resolved promptly.

14
 Competition- (Medium): Offering price matching and a rewards program to
create customer loyalty. As an exclusive reward member, our customers will
be able to take advantage of exclusive loyalty members promotional offers.
Organizational feasibility
Project Champion: Coco Caramel has many years of professional experience in the
IT industry. She will learn hastily to use the system to properly schedule employees,
keep track of expenses, and health inspector reports.
Users: Through training, Coco Caramel’s two initial employees will learn how to
properly use the system in order to manage inventory of ingredients for the
successful fulfillment of customer orders.
An information system that integrates the different functions of the business will
enable the company to strategically align their business demands, thus creating a
competitive advantage.
Risks and level of impact:
 POS machine theft (Low): Someone will be up front at all times. Cameras will
be on site to discourage theft.
 Data breach (High): Will use confidential practices such as setting up unique
ID and multi-level identification passwords to prevent easy unauthorized
access to customer information.
 Natural Disaster (High): Hurricanes, earthquakes, floods and tornadoes are
very unlikely to occur, however our information system could severely be
affected. To avoid the risk of losing our data, we will back up to a server
maintained in a secured location and carry insurance on the information
system
 Legal litigation (Low): A lawyer will be hired in the case of a lawsuit.
However, the proper safety and health procedures will be followed to lower
risk of food contamination.
 Political (very low to none): Everybody loves chocolate; no one will
persecute us for selling it.

15
Additional Comments
 For the first year they anticipate to not have any profit and only have enough
sales to cover all operational and development cost.
 To ensure that the system in installed and developed properly, a professional
third party will be hired. (The Signature Group)
 Initially they will start off with a low cost Dell server, but with taking into
account that there may be a need for an upgrade due to future growth.
 For the first 2 years 2 additional people (one full-time and one part-time)
other than Coco Caramel will be employed. As the business grows, it will
anticipate to hire a full-time desk clerk in year two.
 There is an increasing allowance yearly for employee salaries and wages
(promotions) budgeted due to projected increased sales.
 The full-time clerk will be responsible with maintaining the database.
 Hardware and software upgrades have been budgeted but are not
anticipated to be needed until year 4.

16
Cost & Benefits Analysis
$-
$50,000
$100,000
$150,000
$200,000
$250,000
1 2 3 4 5 6
Dollars
Years
Breakeven Point
Net Benefits
Total Costs

17
Use-case Diagram
Employee
Clerk Manager
Process customer order
Schedule production
Record availability
Online Customer
Owner
View current product list
Place online order
<<extend>>
Manage recipes
Part time Full time
Chocolatier
Assistant
<<include>>
Purchasing transactions
<<include>>
<<include>>
Manage schedule
Manage inventory
<<include>>
Payment options
Generate
management reports
Manage employees
Register to database
Generate supply order

18
Primary Use-Cases Descriptions
Use Case Name: Process Customer
Order
ID: 1 Importance Level: High
Primary Actor: Employee Use Case Type: Essential
Stakeholders and Interests:
Employees at RMCC- Need to be able to process customers’ orders.
Brief Description: The use case describes how the Chocolatier company can
process the customer’s orders efficiently.
Trigger: A store employee has a need to process a customer transaction.
Type: External
Relationships:
Association: Employee
Include: Purchasing Transactions, Payment Options
Extend:
Generalization:
Normal Flow of Events:
1. Open a new ticket
2. Input customer order
3. Confirm order to customer and provide total
4. Process the customer’s order
SubFlows:
Alternate/ Exceptional Flows:

19
Use Case Name: Manage Recipes ID: 2 Importance Level: Medium
Primary Actor: owner Use Case Type: Detail
Chocolatier owner-Coco Caramel wants to add, update, and/or delete recipes for her menu
items.
Brief Description: This use case describes how the Chocolatier shop can maintain an up-to-date
listing of the recipes.
Trigger: Coco Caramel (owner) wants to keep and up to date recipe within the information
system.
Type: Internal
Relationships:
Association: Chocolatier owner
Include:
Extend:
Generalization:
1. Capture the Chocolatier owners pin for security
2. Add/update/delete recipes
SubFlows:

20
Use Case Name: Record Availability ID: 3 Importance Level:
Primary Actor: Employee Use Case Type: Essential
Employee- wants to record availability for work to fit their desired schedule.
Brief Description:
This use case describes how the RMCC employees can record their availability for work
weekly.
Trigger: Employees want an easy way to let manager know what days they are available for
work so that their schedule can be created in a more effective manner.
Type: Internal
Relationships:
Association: Employee
Include: manage schedule
Extend:
Generalization:
1. Capture the employee’s pin number
2. Authenticate the pin number
3. Employee enters availability and hits submit button
SubFlows:

21
Use Case Name:
View Current Product List
Primary Actor: Online Customer Use Case Type: Essential
Online Customer- wants to view current items for sale
Richmond Millennial Chocolatier Company- wants to provide their customers the ability
to view the full list of products for online customers.
Brief Description: This use case describes how the RMCC can provide online customers
with a virtual menu of all the items currently in stock. This use case will allow customers
to view name of product, quantity available, and price.
Trigger: Online customers want to be able to view online the product for sale.
Type: External
Relationships:
Association: Online Customer
Include:
Extend: Place online order
Generalization:
1. Customer clicks through the different product categories
2. Customer clicks on specific chocolate item
3. Customers views quantity available
4. Customer views price
SubFlows:

22
Use Case Name:
Generate Management Reports
Primary Actor: Chocolatier Use Case Type: Essential, Detail
Chocolatier owner- wants to have access to management reports
Brief Description:
This use case describes how the owner of the RMCC can have access to reports that
provide insight about the business in a more detailed and focused manner.
Trigger: The owner wants to be able to generate different reports to better manage
her business.
Type: Internal
Relationships:
Association: Chocolatier
Include: Sales Report, Customer Reports, Production Reports, Inventory Report
Extend: Print Report
Generalization:
1. Chocolatier owner enters security password
2. System authenticates password
3. Chocolatier owner chooses type of report to generate
SubFlows:

23
Use Case Name: Manage Inventory ID: 6 Importance Level: High
Primary Actor: Owner and
Manager
Use Case Type: Internal
Head Chocolatier: wants to make sure that there is always enough inventory on stock
for sales and at same time it is fresh chocolate
Customers: wants Coco Caramel Chocolatier to always have their chocolate
wants/needs.
Brief Description:
Track, Order, generate monthly orders, manage recipes
Trigger:
An order is placed A change in inventory levels
Relationships:
Association: Owner and Manager
Include:
Extend:
Generalization: Chocolatier and Employee
Supplier shipments are needed to be tracked
Once shipment arrives payment is place
Monthly orders are made for supplies
New and old recipes are managed on a daily basis

24
Use Case Name: Manage
Employees
Primary Actor: Owner and
Manager
Use Case Type: Internal
Head Chocolatier: Wants schedules to be agreed upon with all employees.
Wants payroll to be imputed on time.
Employees: Wants to know when they have to work and want to get paid
Brief Description:
Creating a monthly schedule and Imputing payroll bi-weekly
Trigger:
End of a pay period or end of the month
Relationships:
Association: Manager and Employee
Include:
Extend:
Generalization: Employee and Chocolatier
Collect Time Cards every two weeks
Input and process payroll so employees get paid
Ensure that employee schedules are relatively similar from Month to month

25
Use Case Name: Schedule
Production
Primary Actor: Owner and Manager Use Case Type: Internal
Owner and Manager: Want to efficiently keep stock of all menu items, to do so, she
needs to have the ability in the IS to schedule production quantities.
Brief Description:
The use-case describes how the owner and manager of the RMCC can schedule the
production of the items they produce in house.
Trigger:
Coco Caramel and manager need to be able to schedule the production of chocolate
products.
Relationships:
Association: Manager and Owner
Include: Manage Schedule
Extend:
Generalization: Employee and Chocolatier
1. Owner or manager enter pass code
2. System authenticates the pass code
3. Owner or manager schedule different production quantities
4. Owner or manager finalize submission request

26
Use Case Name: Register Customer
to Database
Primary Actor: Online Customer Use Case Type: External
First time and returning customers want to be able to register online in order to have
their name, address, and phone number stored for future orders.
Brief Description:
The use case describes how the customers will be able to create a personal profile that
will store vital information for faster check out in the future.
Trigger:
The need for returning customers to have an easier time placing their online order.
Relationships:
Association: Online Customer
Include:
Extend:
Generalization:
1. Customer clicks on register option
2. Customer enters their personal information and saves it

27
Use Case Name: Generate Supply
Order
ID: 10 Importance Level: Med
Primary Actor: Chocolatier Use Case Type: Internal
Chocolatier: Wants to be able to order supplies through the information system.
Brief Description:
The Use-Case describes how the chocolatier and her assistant can generate a supply
order for the vendors to receive via email.
Trigger:
The need for supplies to arrive on time and for Coco Caramel to be able to order
supplies in an organized, effective manner.
Relationships:
Association: Chocolatier
Include:
Extend:
Specialization: Owner, Assistant
1. Chocolatier enters pass code
2. Pass Code in authenticated
3. Chocolatier selects supplies needed
4. Chocolatier submits supply order

28
Primary Actors Descriptions
Use Case Name: ID: 1 Importance Level:
Primary Actor: Chocolatier Use Case Type:
Head Chocolatier/Owner of the business
Assistant concerned with generating management reports
Brief Description:
Owner and Assistant involved in managing inventory, employees, and generating
management reports
Trigger:
The Hiring on of an individual
Type:
Relationships: Owner and Assistant
Association:
Include:
Extend:
Generalization:
SubFlows:

29
Primary Actor: Employee Use Case Type:
Clerk responsible for recording availability
Manager responsible for employees, inventory, and production schedules
Brief Description:
Clerk and Manager are responsible for day to day flows of events
Trigger:
Daily happenings within the store and online
Type:
Relationships: Clerk and Manager
Association:
Include:
Extend:
Generalization:
SubFlows:

30
Primary Actor: Online Customer Use Case Type:
Chocolatier wants for customers to be interested in the product
Employees want to make sure they are able to supply above average customer
service
Brief Description:
Individuals who view current product lists and place orders online
Trigger:
Perusal of website
Type:
Relationships:
Association: Chocolatier and Employee
Include:
Extend:
Generalization:
SubFlows:

31
Non-Functional Requirements
Operational requirements
 System should be able to connect to printers wirelessly
 Automatic Back-up daily
 Website will maintain accurate inventory levels
Performance Requirement
 System will pull up customer order in 3 seconds
 System will provide clerk and assistant chocolatier with inventory levels in 3
seconds or less
 System will allow employee and administration to view schedule in 3
seconds or less
 System will allow owner to access payroll in 5 seconds or less
Security Requirements
 Only the owner can set schedule and manage inventory
 Employee will need a pin to process a transaction and startup the system
Cultural and Political Requirements
 No Special Cultural or Political requirements are anticipated

33
Class Descriptions
Class Name: Participant ID: 1 Type: Concrete, Domain
Description:
A stakeholder that holds interest in the Richmond
Millennial Chocolatier Company
Association: 0
Generalization: 2
Responsibilities:
Purchase a product
Be an employee
Collaborators:
Payment
Schedule
Class Name: In-Store Customer ID: 2 Type: Concrete, Domain
Description: An individual that purchases a product
inside the actual store.
Association: 2
Generalization: 1
Responsibilities:
Select a product
Make a payment
Collaborators:
Transactions
On-line customer
Product
Class Name: Payment ID: 3 Type: Concrete, Dominant
Description: A type of transaction that is made by either
an in-store customer or online customer.
Association: 1
Generalization: 0
Responsibilities:
Cash
Credit/Debit
Check
Collaborators:
Transactions
Calculate Payment
Product

34
Class Name: Employee ID: 4 Type: Concrete, Domain
Description:
An individual that is on the Richmond Millennial
Chocolatier Company
Association: 0
Generalization: 2
Responsibilities:
Tend to customers
Employee ID #
Handle Transactions
Collaborators:
Payment
Online Customer
In-store Customer
Class Name: Full-Time Clerk ID: 5 Type: Concrete, Domain
Description: An individual that is employed as a clerk and
is paid a salary.
Association: 0
Generalization: 1
Responsibilities:
Process customer requests
Keep track of Schedule
Collaborators:
Transactions
Customers
Head Chocolatier
Class Name: Head Chocolatier ID: 6 Type: Concrete, Dominant
Description: The owner of the Richmond Millennial
Chocolatier Company.
Association: 1
Generalization: 1
Responsibilities:
Manage Inventory
Manage Employee
Make Employee Schedule
Collaborators:
Supplies/Inventory
Recipes
Schedule

35
Class Name: Purchase ID: 7 Type: Concrete, Dominant
Description: Items that a customer selects to purchase. Association: 1
Generalization: 0
Responsibilities:
Type of chocolate
Collaborators:
Single Chocolate
Gift Basket
Class Name: Online Customer ID: 8 Type: Concrete, Domain
Description: An individual that visits and makes
purchases through the online store.
Association: 0
Generalization: 1
Responsibilities:
make payment for purchase
makes order selection
confirms purchase
enters personal information for delivery
Collaborators:
Payment
Purchase

36
Class Name: Inventory ID: 9 Type: Concrete, Domain
Description: The supplies and for sale items currently
stored in the factory.
Association: 1
Generalization: 2
Responsibilities:
Keep count of each item in stock
Alert when an item is out of stock
Maintain a list of available product
Collaborators:
Supply
Product
Head Chocolatier
Class Name: Recipe ID: 10 Type: Concrete, Domain
Description: The list of ingredients needed to create each
product/chocolate item.
Association: 0
Aggregation: 1
Generalization: 0
Responsibilities:
List all ingredients required for a product
Update recipes
Delete recipes
Add new recipes
Print recipes
Collaborators:
Supply
Inventory
Head Chocolatier

37
Class Name: Assistant ID: 11 Type: Concrete, Domain
Description: An employee who works directly under the
head chocolatier (Coco Caramel).
Association: 0
Generalization: 1
Responsibilities:
Update inventory
Order supplies
Run management reports
Collaborators:
Head Chocolatier
Inventory
Product
Supply
Class Name: Part- Time ID: 12 Type: Concrete, Domain
Description: Employee that works hourly. Association: 0
Generalization: 1
Responsibilities:
Clock in
Clock out
Record availability
Request vacation
Create customer orders
Collaborators:
Purchase
Payment
Employee

38
Class Name: Product ID: 13 Type: Concrete, Domain
Description: List of items produced at the chocolatier
shop.
Association: 0
Generalization: 1
Responsibilities:
List products from A-Z
Show images of each product
Display size and weight of each product
Update/add/delete product(s) from list
Collaborators:
Inventory
Supply
Head Chocolatier
Class Name: Supplies ID: 14 Type: Concrete, Domain
Description: Items that need to be ordered regularly. Association: 0
Aggregation: 1
Generalization: 1
Responsibilities:
Place supply order
Track supply order
View supply order
Send supply order inquiry to vendors
Collaborators:
Head Chocolatier
Inventory

41
Object Descriptions
Order Screen Description: Portal where the customer and employee can
input or gather information regarding a particular order
Packing/Shipping Description: A control where information from the order
screen regarding the shipping and packaging aspects of the
order are sent. From there the employee can print a mailing
label.
Object: Shopping Cart Description: A portal where a customer can place the items it
desires to purchase in holding before they proceed to
checkout.
Object: Customer Description: An individual that places an online order
Object: Employee Description: An individual that fills an online order

42
State Machine Diagrams
Customer Order

44
State Descriptions: Customer Order
State:
Received
Description:
Terminology used when customer sends order to RCCC.
State:
In Process
Description:
Terminology used when an employee schedules an order for
filling.
State:
Backorder
Description:
When a product item is not in stock and customer receives a
notification that a new batch would be requested.
State:
Ready-to-be-
Shipped
Description:
Terminology used to describe when an item is retrieved from
inventory, packed, and ready to be shipped out.
State:
Shipped
Description:
When the packer confirms original customer order and
mailing label is applied.
Completion:
Completed Order
Description:
Customer is notified that customer order is shipped

45
State Descriptions: Product Item
State:
New Product
Description:
Initial state where Chocolatier uses a new recipe to create a
product item.
State:
In Production
Description:
An item or group of items is set for creation.
State:
Out of stock
Description:
An item is not available. Not currently in inventory.
State:
In stock
Description:
An item is available. It has been made, packaged, and counted.
Item is inventory.
State:
Out of production
Description:
Product item is at initial production amount for over 7 days.
While item is in this state, the price is reduced by 50% until all
items are sold.
Discontinued Description:
An item that will no longer be produced or stocked by RMCC.

46
User Interface Prototype Screens
Staff Portal

47
Milk Chocolate Dark Chocolate Assorted Chocolate
Richmond
Millennial
Chocolatier
Company

48
CART
Milk Chocolate 2 $14.00
Dark Chocolate 1 $7.00
Assorted Chocolate 1 $7.00

50
Richmond Millennial
Chocolatier Company
Milk
Chocolate
$14.00
Dark
Chocolate $7.00
Assorted
Chocolate $7.00
Customer Order #: 0000000000
Item Total: $28.00
A copy of the receipt will be sent to
the e-mail address that was
provided on the previous screen
Flat Rate: $5.00
Grand Total: $33.00

51
Usability Test Report
We conducted a usability report by testing it on 2 people,
one a general tester and one had a background in IT. When we
conducted the test, we showed each of them the homepage and
they both liked it. The 2nd tester liked the white space of it and
how almost everything could be reached on the first page. We
then asked them to look at the product page and they wished
that it wasn’t as messy so we changed our product page to have
more white space and smaller images. We asked for feedback
on the font and they didn’t like Times New Roman for this so
we changed it to Helvetica, making it look a bit more modern.
We took them to the shopping cart page, and the 2nd
tester liked how it resembled the layout of Amazon’s. The 1st
tester commented that the payment page font size was too
small so we changed it from size 11 to size 16. The purchase
confirmation page was satisfactory to both of the testers.
Overall, when we asked them how the aesthetics looked like,
they liked the color scheme. We believed it was easy to
navigate because they were able to locate what they wanted
within 3 clicks. We took a look at their comments and made
changes to the website and we believe it is much better than
the first prototype.

Final Project

Recommended

Recommended

More Related Content

Similar to Final Project

Similar to Final Project (20)

Final Project