5/2/2016

System Proposal

Mohamed Abbas

Info 361 Section 001

Professor Albert Wynne

Table of Contents

Page

I. Description of Project…………………………………………………………………..3-6

II. Team Charter……………………………………………………………………………….7-10

III. Business Case……………………………………………………………………………….11-19

IV. Use Case Diagram………………………………………………………………………….19-26

V. Class Diagram………………………………………………………………………………...26-30

VI. Sequence Diagrams…………………………………………………………………………31-34

VII. State Machine Diagrams………………………………………………………………….34-38

VIII. User Interface Design………………………………………………………………………38-51

IX. Gantt Chart………………………………………………………………………………………52-56

Summary: This project was comprised in order to show examples of the functional, structural,

and behavioral modeling that takes place during the elaboration phase of the unified process by creating

UML diagrams to describe most of the major use cases and entity classes, as well as some of the dynamic

aspects of the system using sequence and state machine diagrams.

Business Need: The need is 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. It’s also to manage employee

work schedules, and to create management reports that will enable the business to make better

decisions to create a competitive advantage to make profit.

Executive Summary: I was able to design a Use-Case diagram showing an illustration of the

functional requirements and narratives describing Customer Orders, Flow of Events, Payment

Authorization information and Tracking Number plus shipping Costs information. I was able to

implement and design a Class Diagram and Sequence Diagram which shows information of the business

such as Order, Customer, Payment Provider, Account System, Account Payable, Create Schedule, and

Management Reports. What can be improved might be new systems that might be faster to use and

make it easier for customers to have a smooth and efficient transactions and orders as time goes by.

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 outas 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.

Functionality: The information system should allow customers to:

Purchase products in-store and through an Internet store website; this would

include the ability to:

View images of current product inventory through an Internet store

Website.

Display full product description.

Check availability of inventory.

Select delivery option (in-store pickup or delivery service)

Confirm and track Internet orders.

Determine delivery cost and date.

Provide customer delivery tracking identification number.

Specify customized products (special orders).

Confirm custom order within 24 hours.

Generate customer order invoice

Accommodate payment by micro payment system (credit & debit card)

Such as PayPal.

Manage Product Inventory to include the ability to:

Track all supply ingredient quantities (add/update/delete quantities)

Manage all product recipes (ingredient batch quantities)

Generate supply acquisition orders

Send order payment

Track damaged supplies

Manage Employee Schedules

Add/update/remove employees

Create employee work schedules

Track employee work hours

Generate Management Reports

Create production reports

Create employee work reports

Create sales reports

Create inventory reports

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)

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

The 4/4 Club

Purpose and Statement of Team Charter:

The team has been formed in order to cooperate together in order to complete a set of

assignments which is compiled into a group project. Our overall objectives are to integrate our

own research and become proficient in the materials taught in class in order to come to a

conclusion with our own individual presentations to create a unified project. We are confident in

each other’s abilities to bring out the best of the team, and to also work effectively, with

commitment to each other to create a learning experience.

Team Members:

Mohamed Abbas- abbasm@vcu.edu, 202-763-2778

Mouhanad Azzam- azzamma@vcu.edu, 540-556-7462

Yonis Ainab- ainabym@vcu.edu, 571-623-1055

Shivam Chhagan- chhagansv@vcu.edu, 434-485-9978

Omar Alshareef- alshareefof@vcu.edu, 757-773-9633

Roles and Responsibilities-

Mohamed Abbas- Mohamed’s role as the leader is to motivate the group and ensure objectives

are met and the steps to a successful team is underway.

Mouhanad Azzam- Mouhanad’s role is to accumulate all team collaborative information, data,

and research and organize it in a presentable fashion.

Shivam Chhagan- Shivam’s role in this team is make sure all work is presented correctly with

the needed information and details. Having the role of the enforcer, Shivam is responsible for

making sure all members are showing up, participating, and work completing their assigned

work.

Yonis Ainab- The role of Yonis will be defined as determining the right types of research and

information which will need to be presented in a professionally crafted document by making sure

the layout meets the ideal standards.

Omar Alshareef- The roles of Omar are:

1- motivate the group and ensure objectives are with the leader

2- to accumulate all team collaborative information, data, and research and organize it in a

presentable fashion with Mouhanad.

3- make sure all work is presented correctly with the needed information and details with

Shivam

4- determining the right types of research and information which will need to be presented in a

professionally with Yonis

Team Strengths and Weaknesses:

By analyzing each team member’s strength and weakness, we can work towards a productive

and improve ourselves in the criteria that we lack, even by motivating each other. As we

identified our skills and experiences, we can dictate where we are strong and where we lack in

ability.

Strengths

1. Interpersonal skills: All of the group members seem quite inept in this category, as they

come from a background of communicating and have leadership building experience.

2. Background: Each member has had experience with team-based settings dealing with

problems that require more than one solution. Whether it’s volunteering in an

organization or job based work, each member understands the definition of collaborative

projects.

3. Skills & Knowledge: As one member is able to juggle being in different organizations and

holding a job, this will provide a balance and a strong source of motivation to each

group member, and the group as a whole.

Weaknesses

Shivam Chhagan- Shivam tends to overthink problems or solutions that need to be

carried, which can consume more time.

Mouhanad Azzam- One weakness that Mouhanad possesses would be investing more

time and energy on part of a project and investing a significantly less amount on another. By

investing an appropriate amount of time

Mohamed Abbas- Mohamed’s lack of focus sometimes would be problematic, as he

tends to zone out and thinks of irrelevant things. By adhering to the objective of the group and

focusing on the outcome, this weakness can be overturned.

Yonis Ainab- Yonis tends to stress over the little details, which leads to consuming time

on things that don't matter. By focusing and using time management, Yonis can overcome these

weaknesses.

Omar Alshareef- Tends to stress over the little details, which leads to consuming time on

things that don't matter. By focusing and using time management.

Members’ Biographies:

Mohamed Abbas- As a student studying Information systems at Virginia Commonwealth

University, Mohamed is looking to gain the knowledge of Information Systems to better

understand what makes a business prosper in the age of technology. Having been at VCU for 1

year has taught Mohamed the meaning of being independent and self-sufficiency, which is an

experience in its own right. Mohamed hails from Arlington, Virginia and looks forward to an

outstanding college experience.

Mouhanad Azzam- Mouhanad Azzam is a Junior at Virginia Commonwealth University,

originally from Roanoke, Virginia. During his time at VCU, Mouhanad has maintained over a

3.0 GPA while working part time at MetroPCS and being involved in two organizations; United

Muslim Relief and Muslim Student Association. Maintaining a busy schedule has taught

Mouhanad time management, organization, communicating efficiently, and building leader

qualities. Building these qualities have become very helpful to Mouhanad in his major and his

professional career.

Yonis Ainab- Mr. Ainab is a junior at VCU, originally from Falls Church, Virginia. Also works

part time at Best Buy. Living on his own has taught Mr. Ainab, responsibilities, time

management, and organization. These responsibilities have given Mr. Ainab the right tools to be

self-sufficient.

Shivam Chhagan- In his junior year at VCU, Mr. Chhagan is an Information Systems major

from Lynchburg, Virginia who takes pride in programming, auditing, and infrastructure. Mr.

Chhagan is also a member of the Pi Kappa Phi Fraternity here at VCU part of the Epsilon Pi

chapter. Being involved with academics and extracurricular activities, Mr. Chhagan strives to

complete tasks efficiently through team-based projects.

Omar Alshareef- In his senior year at VCU, Mr. Alshareef is an Information Systems major at

VCU, Mr. Alshareef has engineering degree in communication and more than 6 years of

experience.

Team Expectations and Rules:

Each member will be responsible for completing their assigned task as an individual and be able

to present the material efficiently. Last each member is responsible for showing up to group

meetings on time and one should notify the whole group if they will not be present or late. If a

member misses three meetings without notifying any team member, that member will be

obligated to hold a mandatory meeting with the supervisor about their issues and whether they

can or cannot attend group meetings for the time being. Each member is expected to present their

pure, honest work and should equally divide the work equally within the team to ensure positive

results.

Meeting Times:

In each meeting, every member will discuss their ideas and thoughts and we will begin by

brainstorming. We will discuss our objective for the day and what will be expected from each

member. Each member will have the opportunity and time to express their thoughts and ideas.

Each meeting is expected to be met at the timely manner, if a member is unable to make it to a

meeting, he or she will have to address the group or leader ahead of time so adjustments will be

made. Everyone is expected to contribute equally so the group will function properly and

efficiently. Participation is critical to a successful project. Outside of meetings, the group will

have other resources to stay in touch with one another including emails, text messaging, video

chat, and Google Docs.

Code of Ethics:

The 4/4 Club strives on mutual respect. Each member will respect one another, and if a conflict

arises, we will discuss the matter in a professional manner. No slandering one’s work or ideas, or

use of profanity, as this is a professional setting. One will not take another’s work and submit it

as their own. Each member will be responsible for following the same practices of the VCU

Code of Conduct when working together as a team and individuals.

Signature of Agreement:

By adhering to the above information, I hereby, accept and more importantly, understands, and

agree to the rules, conditions, and expectations noted in the Team Charter, The 4/4 Club.

-Shivam Chhagan

-Mouhanad Azzam

-Mohamed Abbas

-Yonis Ainab

-Omar alshareef

The Richmond Millennial Chocolatier Company

2016

Team: 4/4 club

Members

(Mohamed Abbas, Yonis Ainab, Omar Alshareef, Mouhanad Azzam& Shivam Chhagan)

Class (Info 361)

A statement of purpose for the project:

The Richmond Millennial Chocolatier Company founded by Coco Caramel, an

entrepreneur who is experienced in the field of IT for 15 years, is devoted to making this starting

company a leading producer of chocolate by giving its customers high-quality chocolate. Driven

by her passion, Coco Caramel hopes to use her passion to produce the best chocolate possible.

Expected Business Value:

Functionality and Tangible Values include generating sales through in-store and online Business-

to-Consumer E-Commerce, efficient and reliable functionality of online store, proper inventory

management, employee schedule management, and management report generator. Intangible

Values include growing a customer base, promoting the business, developing a product brand,

creating high customer satisfaction, creating excellent customer service, knowing customer base,

knowing product demand, intelligent management reporting system, and developing excellent

supply chain relationships.

Scope Statement:

This project is to develop an information system for the Richmond Millennial Chocolatier

Company. The system will include, inventory management, a customer database, loan tracking,

financial accounting, POS capabilities, legal reporting and online presence.

Goals and Objectives:

This system is expected to innovate the staff and customer experience, cut down losses due to

clerical errors, reduce staffing costs, improve decision-making and price-setting in making loans,

smoothly operate transactions, and improve customer satisfaction and experience.

Technical Feasibility

Location: Medium

It can definitely impact the sales and the amount of customers would come to the store. A plaza

that's a busy shopping center or Mall would be a good location.

Project size: Low Risk

We are working with a small chocolatier so training users and managing the system should be

simply understood given all the full descriptions of products.

.

Shipping: Low

When customers are ordering their products from online would you charge them for shipping or

would the company pay for that service? It would be appealing and satisfying for customers if

they saw that they didn't have to pay for any shipping fees.

Legal requirements: Low

Company must meet the legal requirements of the state. Must be able to safely store correct

information of customers and accounting data.

Economic Feasibility (Medium Risk)

Assumptions

●Revenue will increase by 0.96%

The percentage reflects a moderate prediction of an increase of one additional customer per week

on average relatable to the information system the chocolatier has to offer.

●Clerk salary costs will be reduced by 15%

Confirmations of customer orders within 24 hours and generating customer order invoices will

create less work to monitor. Accommodating payments by the micro payment system (credit &

debit card) such as PayPal will keep track of customer order profiles creating an automated

tracking system.

●Discount Rate of 5% required rate of return by the firm.

Tangible Benefits:

●ROI over 5 years: 3%

●NPV over 5 years: 528,486

●Breakeven occurs after: 5 years

Intangible Benefits:

Maximize and know customer base

Promote business through advertisements

Develop store/product brand

Create high customer satisfaction and excellent customer service

Know product demand

Intelligent management reporting system

Develop excellent supply chain relationships

Developmental Costs

Consulting Fees: $5,050.25

-$849.99 annual service contract

Hardware Costs (Upfront): $1,245.55

Ongoing Maintenance Costs

Software Licensing Costs: $1,110.00 annually

Operational Costs

Manager Training: $2,000.00

Clerk Training: $1,425.00

Web Service Fees: $250.00

Risks

Security: Low

Establishing a secure payment service will encourage customers to make frequent purchases off

the web if PayPal is the entrusted service.

Expenses: Medium

Overhead costs of facilities & required human resource requirements will be relative to change

due to the small size of business. Therefore, consumer satisfaction can severely impact the costs

of facilities and what is required of the employees.

..

Organizational Feasibility:

Strategic Alignment: Low Risk

This project is strongly aligned with the business strategy of The Richmond Millennial

Chocolate Company as sales will increase, inventory errors will be reduced, improved

accounting and tax reporting, and new customers can be brought in through the company’s

website.

Making the new system prevalent: Low Risk

●Management plan: The owner and staff will be consulted as to what functionality would

improve their sales and workload. The system that will be designed will be user friendly. Shop

staff will receive training to use the system and will benefit from the ease of tracking inventory,

loan and sales records, and customer records.

●Customers will benefit from the capability of checking the status of their loans online and also

having in store transactions viewable.

Adapting to the new system: Medium Risk

●Staff will possibly have little experience in POS/inventory management software.

●Consistent training will be provided to the staff. With more knowledge implemented, the

system will improve the simplicity of transactions.

Legal and Contractual:Low Risk

The software fees will be month to month not involving a designated contract.

Cost Benefit Analysis

year 1 ($)

year 2 ($)

year 3 ($)

year 4 ($)

year 5 ($)

Total ($)

Benefits

Reduce inventory losses 0 0 0 0

Improve 0 0 0 0

Improve distribution logistics 0 0 0 0

Reduce cost of data collection 0 0 0 0

Total benefits 0 0 0 0 0 0

Development costs

Analysis 0

Design 0

Programming 0

Documentation 0

Installation 0

Test 0

Initial Training 0

Hardware 0

Software 0

Vendor Installation 0

Data Conversion Costs 0

Total development costs 0 0

Operational costs

Software upgrades 5,000 5,000 5,000 5,000 20,000

Software licensing (communications, network os, etc.) 1,000 1,000 1,000 1,000 4,000

Hardware upgrades 5,000 5,000 5,000 5,000 20,000

Web Services Fees 1,000 1,000 1,000 1,000 4,000

IS Support Staff 125,000 125,025 125,050 125,075 500,150

User training 12,000 12,002 12,005 12,007 48,014

Total operational costs 149,000 149,027 149,055 149,082 596,164

Total costs 0 149,000 149,027 149,055 149,082 596,164

Total benefits 0 0 0 0 0 0

Net benefits 0 -

149,000 -

149,027 -

149,055 -

149,082 -

596,164

Break-Even Analysis

ANNUAL NPV 0 -

141,905 -

135,172 -

128,759 -

122,650

CUMULATIVE NPV Cash Flow 0 -

141,905 -

277,077 -

405,836 -

528,486 -

528,486

Break-Even Point 1.00 years

Return on Investments -100%

Estimated Inflation 2% 2% 2% 2% 2%

Cost Benefit Analysis

year 1 ($) year 2 ($) year 3 ($) year 4 ($) year 5 ($) Total ($)

Benefits

Reduce inventory 1560.5 1943 =C5*($D$42/100+1) =D5*($E$42/100+1) =E5*($F$42/100+1) =SUM(A5:F5)

Improve distribution 2100 4384 =C6*($D$42/100+1) =D6*($E$42/100+1) =E6*($F$42/100+1) =SUM(A6:F6)

Reduce cost of data collection 2974 5820 =C7*($D$42/100+1) =D7*($E$42/100+1) =E7*($F$42/100+1) =SUM(A7:F7)

Total benefits 6634.5 =SUM(C5:C7) =SUM(D5:D7) =SUM(E5:E7) =SUM(F5:F7) =SUM(A8:F8)

Development costs

Analysis =640*100 =SUM(A11:F11)

Design =250*100 =SUM(A12:F12)

Programming =300*100 =SUM(A13:F13)

Documentation =50*75 =SUM(A14:F14)

Installation =300*100 =SUM(A15:F15)

Test =300*100 =SUM(A16:F16)

Initial Training 25000 =SUM(A17:F17)

Hardware 40000 =SUM(A18:F18)

Software 95000 =SUM(A19:F19)

Vendor Installation 20000 =SUM(A20:F20)

Data Conversion Costs 15000 =SUM(A21:F21)

Total development costs =SUM(B11:B21) =SUM(A22:F22)

Operational costs

Software upgrades =C25 =D25 =E25 =SUM(A25:F25)

0

20,000

40,000

60,000

80,000

100,000

120,000

140,000

160,000

1 2 3 4 5

Do

llars

Years

Break-Even Analysis

Total costs

Total benefits

Software licensing (communications, network os, etc.) =C26 =D26 =E26 =SUM(A26:F26)

Hardware upgrades =C27 =D27 =E27 =SUM(A27:F27)

Web Services Fees =C28 =D28 =E28 =SUM(A28:F28)

IS Support Staff =C29*($D$42/100+1) =D29*($E$42/100+1) =E29*($F$42/100+1) =SUM(A29:F29)

User training =C30*($D$42/100+1) =D30*($E$42/100+1) =E30*($F$42/100+1) =SUM(A30:F30)

Total operational costs =SUM(C25:C30) =SUM(D25:D30) =SUM(E25:E30) =SUM(F25:F30) =SUM(G25:G30)

Total costs =B22+B31 =C22+C31 =D22+D31 =E22+E31 =F22+F31 =G22+G31

Total benefits =B8 =C8 =D8 =E8 =F8 =G8

Net benefits =B8-B33 =C8-C33 =D8-D33 =E8-E33 =F8-F33 =G8-G33

Break-Even Analysis

ANNUAL NPV =B35 =C39-B38 =D39-C39 =E39-D39 =F39-E39

CUMULATIVE NPV Cash Flow =B35 =NPV(0.05,C35)+B38 =NPV(0.05,C35,D35)+B38 =NPV(0.05,C35,D35,E35)+B38 =NPV(0.05,C35,D35,E35,F35)+B38 =F39

Break-Even Point =(C38-C39)/C38+1 years

Return on Investments =G35/G33

Estimated Inflation 0.02 0.02 0.02 0.02 0.02

Use-Case Diagram:

Illustration of functional requirements

Richmond MillennialChocolatier CompanyInformation System

3rd PartyShippingProvider

Customer Order details

Payment amount & method

Shipping preference

Contact information

Customer

ACCTSystem

PaymentProvider

Payment authorizationinformation

3rd Party PaymentProvider

RMCCMGMT/Staff

Vendor

Manager

shipping option

Tracking #

Shipping cost information

Management Reports

Update confirmations

Report requests

Marketing Campaign information

Reports: (Financial,Inventory)

Vendor information

Item information

Completed order details

New inventory

details

Acct status request

Acct Payable &Receivable details

Transactionpayment

details

Order InvoiceConfirmation #

Create schedule

Use Case Narrative

Descriptions:

Actors:

Customer: Order chocolate products

3rd Party Payment Provider: Payment authorization information

3rd Party Shipping Provider: Tracking # Shipping cost information

MGTM/Staff: Report requests: (Vendor, Customer, Inventory, 3rd Party Shipping, 3rd Party Payment, Customer, Sales, Inventory) ,New/Updated Information (Vendor, Customer, 3rd Party Shipping, 3rd Party Payment, inventory) Marketing Campaign information

Vendor: Reports(Financial, Inventory) Order information Payments

ACCT System: Acct Payable & Receivable details

Use Case: Customer Order

Actors: Customer, Richmond Millennial Chocolatier Company(RMCC)

Purpose: Take Customer order details

Description: Customer will place an order

Flow of Events

1. Customer wants service 2. RMCC will place order in system 3. RMCC will take customer’s shipping and contact info 4. RMCC will identify payment amount & method 5. Customer places an order

Use Case: Payment

Actors: Richmond Millennial Chocolatier Company(RMCC), 3rd Party

Payment Provider

Purpose: To identify contact info, Payment method, and Payment

account

Description: RMCC and Payment provider will come to a conclusion if

method of payment is accepted

Flow of Events

1. RMCC will run payment method 2. Payment Provider will authorize funds 3. RMCC will a place completed order Information for shipment

Use Case: Order Shipment

Actors: Richmond Millennial Chocolatier Company(RMCC), 3rd Party

Shipping Provider

Purpose: Transportation of Product and Costs

Description: RMCC will receive tracking number and shipment price

Flow of Events

1. 3rd Party Shipping Provider will receive completed order info for shipment 2. RMCC will pay asking payment 3. 3rd Party Shipping Provider will send out tracking number of product to RMCC plus shipping cost

info

Use Case: Managing

Actors: Richmond Millennial Chocolatier Company(RMCC), MGMT/Staff

Purpose: Manage company operations and transactions.

Description: Management will command marketing campaign strategies,

Manage reports, keep and update inventory, take requests

from ,Vendor, Customer, Inventory, 3rd Party Shipping, 3rd

Party Payment, Sales, Inventory

Flow of Events

1. RMCC sends management reports and updated confirmations 2. Management and Staff will manage marketing campaigns to attract customers and potential

business partners 3. MGMT and Staff will take report requests from : (Vendor, Customer, Inventory, 3rd Party

Shipping, 3rd Party Payment, Customer, Sales, Inventory)

Use Case: Vendor

Actors: Richmond Millennial Chocolatier Company(RMCC), Vendor

Purpose: Distribution of products

Description: RMCC will receive distribution from its Vendor

Flow of Events

1. RMCC reports financial inventory to its Vendor 2. RMCC sends its order information and payment 3. Vendor sends completed order details and item details 4. Vendor also sends out an Acct status request

Use Case: Transaction

Actors: Richmond Millennial Chocolatier Company(RMCC), Account

System

Purpose: Balance accounting details

Description: RMCC sends its transaction payment details and Account

system balances the payables and receivables

Flow of Events

1. RMCC system will report its transactions to the account system 2. Account system will begin to balance the accounts.

Nonfunctional Requirements:

Description

Performance -The system will have to process all transactions in less than three seconds. -The system will need to be ready for use 24/7 all throughout the year. -Once transactions are made, the system will have to update the inventory.

Operational -The system has to contain an inventory management system. -The system will need to accessible to the Internet. -The system needs to be able to link credit card transactions with their associated companies. -The system will need to connect to the label printers, scanners, and receipt printers. -The system should be backing up all information routinely.

Cultural/Political -System will contain a simple design and be natural for non-technical staff. -The system will only accept currency from the U.S. -All descriptions/serial numbers of inventory must be recorded in real time. -The system will comply with all tax and accounting laws. -The system will comply with all state or federal laws in order to maintain legality.

Security -Customer and employee personal information must be kept protected at all times. -Only the general manager should have access to personal documents for applicable reasons.

System User

First and Last NameAddressPhone numberEmailDate of BirthRegister UserUpdate User Info

Customer

Customer IDCustomer NameDate of BirthPhone Number

Order

Order IDOrder Date OpenOrder Date Closed Registration DateRegistration TimeAdd OrderDelete OrderConfirm Order

Payment Provider

Payment Order IDDate PaymentConfirm Payment

Account System

Customer IDPayment IDOrder ID

Transaction Payment Detal

Order IDConfirmation IDPayment ID

Account Payable

Customer IDOrder IDPayable NumberDate Start Date End

Recievable Details

Customer IDOrder IDPayable IDDate StartDate End

Manager

Employee IDDate StartDate EndAssign ScheduleApprove ScheduleDetail UserApprove Request

Create Schedule

Customer IDEmployee IDOrder IDReport ID

Management Report

Employee IDSchedule IDRMCC IDAssign Schedule

RMCC Management

Employee IDReport IDStart DateEnd DateReport StartReport End

Payment Provider

Customer IDConfirmation NumberReciept Number

Vendor

Customer IDEmployee IDManager ID

Report

Efficient DateSchedule DateTotal PriceVendor IDCustomer IDAssign Time StartAssign Time End

Update

Update Efficient DateUpdate Schedule DateUpdate Total PriceUpdate Vendor IDUpdate Customer IDUpdate Assign Time StartUpdate Assign Time End

Provider

Customer IDOrder IDPayment ID

Shipping

Order IDPayment IDCustomer IDShipping NumberDate ShippingDate Arrival

Payment Authorization

Customer IDOrder IDPayment IDAuthorization StartAuthorization EndShipping Number

-memberName-memberName

Short Descriptions

Order: The order consists of what product or service the customer is trying to attain. It consists

of the order ID, date the order was opened and closed, registration date and time, and when the

order was added, deleted, and confirmed.

Customer: The customer is responsible for the purchase. Each customer has an ID, name,

date of birth, and phone number.

Payment Provider: The payment provider is the amount paid by a customer and includes the

customer ID, confirmation, number, and receipt number.

Account System: The system keeps track of all accounting activities and includes the

customer ID, payment ID, and order ID.

Account Payable: The account payable is what account the payment is being made and

includes the customer ID, order ID, payable number, start date, and end date.

Transaction Payment Deal: The individual that makes a transaction is part of the final deal and

includes the order ID, confirmation ID, and payment ID.

Receivable Details: The receivable includes which transactions are receivable. It includes the

customer ID, order ID, payable ID, start date, and end date.

System User: The system user is responsible for fulfilling all the criteria necessary to complete

a business deal from the customer to the employee. The system user includes the member’s

first and last name, address, phone number, email, date of birth, the registration of a user, and

updating the user’s info.

Create Schedule: The schedule refers to what times and days certain tasks have to be

completed and includes the customer ID, employee ID, order ID, and report ID.

Provider: The customer that completes the transaction. This includes Customer ID, Order ID,

and Payment ID.

Vendor: Supply the business with what it needs to run. Customer ID, Employee ID, and

Manager ID.

Shipping: Keeps track of orders coming in to the store and orders that are leaving. This

includes Order ID, Payment ID, Customer ID, Shipping number, Date of shipping and Date of

arrival.

Update: Updates everything about the store on a daily basis. This includes Update Efficient

Date, Update Schedule Date, Update Total Price, Update Vendor ID, Update Customer ID,

Update Assign Time Start, and Update Time End.

Report: A Report of the whole day. Example: Transactions, Inventory, Sales. This includes

Efficient Date, Schedule Date, Total Price, Vendor ID, Customer ID, Assign Time Starts, and

Assign Time Ends.

Payment Authorization: Authorizes and keeps track of each transaction that occurs. This

includes Customer ID, Order ID, Payment ID, Authorization Start, Authorization End, and

Shipping number.

RMCC Management: The managers of the business. This includes Employee ID, Report ID,

Start Date, End Date, Report Start, and Report End.

Management Report: Reports on performance of employees. This includes Employee ID,

Schedule ID, RMCC ID, and Assign Schedule.

Payment Provider: The middleman between the transactions. This includes Payment Order ID,

Date Payment, and Confirm Payment.

Manager: Manages the business and overseas duties. This includes Employee ID, Date Start,

Date End, Assign Schedule, Approve Schedule, Detail User, and Approve Request.

customer order screen shopping cart

views product items listed

selects product item

place in shopping cart

contenu shopping

contenu shopping/selects product item

select check-out

calculates & displays all selected product item(s),

charges

shipping charges

total order charge

personal contact information

payment information

prompts for confirmation

confirms order

confirms that customer order has been placed

emails confirmation and receipt

Main scenario Flow-of-Events for place-on-line order:

Richmond MillennialChocolatier Company

Top Package::Actor

Employee administrative screen System

selects fill-customer-order menu item

opens the fill-customer-order screen

enters customer order information

customer fill

displays customer order details

checks for product availability in product item inventory

there is sufficient product inventory

asks system to prepare receipt and packing slip

receipt and packing slip

prints receipt & packing slip

asks system to prepare mailing label

prepare mailing label

prints mailing label

updates product item inventory levels

updates customer order as filled

confirms update actions

Top Package::Actor

Main scenario Flow-of-Events for fill-on-line order

Richmond MillennialChocolatier Company

Object Descriptions: Customer: The customers views products listed. They select product item and select check out when

customers are ready to purchase.

Order Screen: Calculates and displays all selected product items. Shows shipping charges and prompts

for confirmation. Also confirms that customer order has been placed. Shows the items selected and

charges, total order charge, and confirms order.

Shopping Cart: Customer continues shopping. Emails confirmations and receipts.

Employee: Customer order menu item, enters customer order information, employee asks system to

prepare receipt and packing slip.

Administrative Screen: Shows customer order screen, displays customer order detail, checks for product

availability and product item inventory. Shows receipt and packing slip. Prepares mailing label and prints

mailing label. Updates product item inventory levels.

System: Customer fill, shows if there sufficient product inventory, prints receipts and packing slip,

Updates customer order as filled, confirms updates of actions.

Project Management:

CustomerOrder Descriptions:

Received: A new customer order is received as a created object and has to be checked for additional

features such as completeness and correctness.

In-Process: The order is being processed with all the necessary information to confirm a final shipment

which is filled by the employee.

Ready-to-be-Shipped: Once the order is checked to see if the product is in stock, the product item is then

retrieved from the inventory and packed for shipping.

On-Backorder: If the product that is ordered is not in stock, the customer is then notified and then a

request to make a new batch is made.

Shipped: The order is en route to its destination with a mailing label applied on the shipping container.

Completed-Order: Once the order is shipped from the facility, the customer will get a notification that

the order has been finalized. An order number and arrival details are also given in the notification.

ProductItem Descriptions:

NewProduct: A recipe is used to put all the contents together to create a product item.

In-Production: The product will be scheduled to go through a production process which will make it

presentable to customers.

In-Stock: When the product is finalized after production, it is packaged and counted to make it available

in-stock.

Out-of-Stock: If the quantity of the product reaches zero, a new request will be made to begin the

production schedule for the product to be available again to customers.

Out-of-Production: The product item is sold out and no longer being produced to be put on the shelves

again. Whatever quantity is left of the product will conclude in a 50% price decrease for the item.

Discontinued: Once the item remains out-of-production where the last batch was made more than seven

days ago, then the item will no longer be available and will be marked as discontinued.

Out-of-Production

Out-of-Production

Out-of-Production

The Richmond Millennial

Chocolatier Company

Contents Interface Designing ....................................................................................................................... 40

Windows Navigation Diagram: ..................................................................................................... 49

Dialogue Diagrams/Windows Navigation Diagram: ..................................................................... 49

Ms Project Plan: ............................................................................................................................ 51

Interface Designing RMCC homepage:

RMCC shopping cart page:

RMCC shopping cart page :

RMCC payment page:

RMCC purchase confirmation Page:

Windows Navigation Diagram:

Dialogue Diagrams/Windows Navigation Diagram:

Usability Testing:

We have conducted the usability test by asking some questions from the user. We have taken

the contact information and their information about their job too. These people were unfamiliar with our

website. They have given us a good response in general. Some of them easily grabbed the concept what

we were trying to do. But few was not sure what our website was. But we gave some information about

our project they understood it right away. Majority of the people liked our concept and our theme and

color and font of the website. But as it was too basic so they told us to increase the content of the website.

But overall they were impressed.

They said that this website was very helpful and ease to use for the Chocolate order. This

website includes many advantages like online registration and online order system. They also encouraged

the online transaction that we were to introduce. But they had their some reservations regarding the

security issue of the payment. Some of them has seen the chocolate system, but they said that the formal

chocolate order process is very time taking. People cannot take out time from their busy schedule going

shop for order. But it was very difficult for them, so that’s why they appreciated our concept because of

this, they can fulfill their hobbies without taking out some special time.

We are just a website away from them. But there was not a single person who disliked our

theme of the website. They said that our website is attractive, user friendly and they hope that it will not

be slow. The website provided ease to use, it is very user friendly, email and contact no is provided in

case of any problem.

MS Project Plan:

Gantt chart Task Mode Task Name Duration Start Finish Predecessors

Manually Scheduled

EC Project 0 days? Fri 2/19/16 Fri 2/19/16

Manually Scheduled

Testing 0 days? Fri 2/19/16 Fri 2/19/16

Manually Scheduled

Test Plan 0 days Fri 2/19/16 Fri 2/19/16

Manually Scheduled

Define features and functionality to test

4 days Fri 2/19/16 Wed 2/24/16

Manually Scheduled

Define test methodology 3 days Fri 2/19/16 Tue 2/23/16

Manually Scheduled

Design test cases 2 days Fri 2/19/16 Mon 2/22/16

Manually Scheduled

Develop responsibility matrix 1 day Fri 2/19/16 Fri 2/19/16

Manually Scheduled

Review plan with developer 1 day Fri 2/19/16 Fri 2/19/16

Manually Scheduled

Develop test schedule 5 days Fri 2/19/16 Thu 2/25/16

Manually Scheduled

Milestone: PM signs off on test plan 0 days Fri 2/19/16 Fri 2/19/16

Manually Scheduled

Test Results Report 4 days Fri 2/19/16 Wed 2/24/16

Manually Scheduled

Review test plan with client 1 day Fri 2/19/16 Fri 2/19/16

Manually Scheduled

Carry out test plan 5 days Fri 2/19/16 Thu 2/25/16

Manually Scheduled

Analyze results 4 days Fri 2/19/16 Wed 2/24/16

Manually Scheduled

Prepare test results report and presentation

5 days Fri 2/19/16 Thu 2/25/16

Manually Scheduled

Present test results to client 1 day Fri 2/19/16 Fri 2/19/16

Manually Scheduled

Address any software issues or problems

3 days Fri 2/19/16 Tue 2/23/16

Manually Scheduled

Milestone: Client signs off on Test results

0 days Fri 2/19/16 Fri 2/19/16

Manually Scheduled

Milestone: Testing Completed 0 days Fri 2/19/16 Fri 2/19/16

Manually Scheduled

Use Case 2 days Fri 2/19/16 Mon 2/22/16

Manually Scheduled

Case Diagram 6 hrs Fri 2/19/16 Fri 2/19/16

Manually Scheduled

Flow Charet 4 hrs Fri 2/19/16 Fri 2/19/16

Manually Scheduled

Detaliled Description Of Actors 6 hrs Fri 2/19/16 Fri 2/19/16

Manually Scheduled

Non_funtional requirements 2 hrs Fri 2/19/16 Fri 2/19/16

Manually Scheduled

UML Diagramming 3 days Thu 2/25/16

Mon 2/29/16

Manually Scheduled

Identify Actors 3 hrs Thu 2/25/16 Thu 2/25/16

Manually Scheduled

Identify Attributes 1 hr Thu 2/25/16 Thu 2/25/16

Manually Scheduled

Identify objects 1 hr Thu 2/25/16 Thu 2/25/16

Manually Scheduled

Identify functions 1 hr Thu 2/25/16 Thu 2/25/16

Manually Scheduled

creat UML diagram 3 hrs Thu 2/25/16 Thu 2/25/16

Manually Scheduled

Review Diagram 3 hrs Thu 2/25/16 Thu 2/25/16

Manually Scheduled

creat short description of diagram 2 hrs Thu 2/25/16 Thu 2/25/16

Manually Scheduled

make deliverable prepard 6 hrs Thu 2/25/16 Thu 2/25/16

Manually Scheduled

submit UML Diagram 0 hrs Thu 2/25/16 Thu 2/25/16

Manually Scheduled

Sequence Diagramming 2.5 days Tue 3/1/16 Thu 3/3/16

Manually Scheduled

Identify Actors 2 hrs Tue 3/1/16 Tue 3/1/16

Manually Scheduled

Identify Attributes 2 hrs Tue 3/1/16 Tue 3/1/16

Manually Scheduled

Appoint Lifelines 1 hr Tue 3/1/16 Tue 3/1/16

Manually Scheduled

Display Appropriate messages 2 hrs Tue 3/1/16 Tue 3/1/16

Manually Scheduled

Execution Occurrence 2 hrs Tue 3/1/16 Tue 3/1/16

Manually Scheduled

Validate Diagram 4 hrs Tue 3/1/16 Tue 3/1/16

Manually Scheduled

create short description of sequences

1 hr Tue 3/1/16 Tue 3/1/16

Manually Scheduled

State Machine Diagramming 3 days Tue 3/8/16 Thu 3/10/16

Manually Scheduled

identify Material 3 hrs Tue 3/8/16 Tue 3/8/16

Manually Scheduled

identify objects 1 hr Tue 3/8/16 Tue 3/8/16

Manually Scheduled

Appoint Lifelines 1 hr Tue 3/8/16 Tue 3/8/16

Manually Scheduled

Display Appropriate messages 2 hrs Tue 3/8/16 Tue 3/8/16

Manually Scheduled

Execution Occurrence 2 hrs Tue 3/8/16 Tue 3/8/16

Manually Scheduled

Validate Diagram 4 hrs Tue 3/8/16 Tue 3/8/16

Manually Scheduled

Create short description of sequences

1 hr Tue 3/8/16 Tue 3/8/16

Manually Scheduled

Make deliverable prepard 2 hrs Tue 3/8/16 Tue 3/8/16

Manually Scheduled

Submit sequence Diagram 0 hrs Tue 3/8/16 Tue 3/8/16

Manually Scheduled

Risk Speculation 1 hr Tue 3/8/16 Tue 3/8/16

Manually Scheduled

interface desiging 3 days Thu 4/14/16

Mon 4/18/16

Manually Scheduled

interface defining 1 day Thu 4/14/16 Thu 4/14/16

Manually Scheduled

interface desig 1 day Thu 4/14/16 Thu 4/14/16

Manually Scheduled

Determiniation 1 day Thu 4/14/16 Thu 4/14/16

Manually Scheduled

Relation with user 1 day Thu 4/14/16 Thu 4/14/16

Manually Scheduled

Useability report 1 day Thu 4/14/16 Thu 4/14/16

Manually Scheduled

project management plan 1 day Thu 4/14/16 Thu 4/14/16

Manually Scheduled

windows navigation 1 day Thu 4/14/16 Thu 4/14/16