Below attached are 2 files, I have completed almost half of the assignment the only thing left to do are the diagrams there is a use case diagram, activity diagram, class diagram and sequence diagram. the other file is template on how the diagrams must be done you need to compare the 2 files with each other after the work is done. The question is urgent and require it about in 1 hour.
Robert’s Overview of the Furniture Stores
Owners View
Online Purchasing
Customers place orders
online.
Menu is maintained
Customer chooses
payment option
Delivery Time notification
to customer
Sales person
Management
Assigning Orders to the
person making the sale
Calculate commisions
accurately
Record Online Sales
Details
Inventory management
Processing of the
orders.
Record Arrivals of
items
Assign Prices of Items
Record of items in
warehouse
Accounting
Management
Processing credit card
facilities.
Record discounts
Manage online
payments
Generate reports of
revenue
Furniture Delivery
Scheduling
Ensure on time
delivery.
Ensure multiple
deliveries for maximum
efficeincy
Notification if payment
is cash on delivery
1
I. Domain Analysis [15 marks]
1. Write domain definitions and, from there, proceed to establish the domain scope for the
system and each subsystem. The following table provides a template for your answer.
Robert’s Furniture Stores
Domain Definitions & Scope
Scope Outline
Domain
Online
Purchasing
•
•
•
Inventory
Management
•
•
•
•
•
Accounting
Management
•
•
•
•
•
Sales Person
Management
•
•
•
•
Furniture
Scheduling
and Delivery
•
•
•
•
Ensure that the customers place their orders online without any
hitches.
The online menu should be well maintained at all times.
Ensure that there a number of payment options that the customers
can use online.
Send customers notifications of expected turnaround time.
Notify inventory and delivery departments of the order.
.
Staff Records the current and future arrivals of items
Staff assigns prices of furniture based on quality, materials and
styles.
Staff maintains the records of items in the warehouse
Staff Updates Stock regularly
Keep a record of discounts on items
Generate business and finance reports and provide it to the
manager monthly
Manage all the online payments and the credit card facilities and
cash.
Ensure that the order is assigned to right person who pitched the
sale.
Ensure proper management of the customer information.
Ensure that the commissions of the sales agents are calculated
properly.
Aid the sales agent in promoting the products through providing
them with the required materials.
Process and bundle orders.
Ensure right planning of furniture preparation.
Ensure on-time serving, conveyance, and pickup.
Route multiple deliveries for most extreme efficiency
2
2. Identify the domain concepts from the domain definition and scopes. Categorise the
concepts into processes, functions, roles, objects, and business rules. You need to list them
in a domain dictionary table using the following template:
Furniture Stores
Domain Dictionary
Name
Furniture
Customer
Commission
Credit card
Exchange
Online inventory
Order
Payment
PayPal
Website Staff
Discounts
Salespeople
Delivery Company
Accountant
Incentive Program
Pricing
Menu
Payment
Processing
News Alerts
Type
Object
Role
Business
rule
Object
Process
Object
Function
Function
Object
Role
Description
The purchasable item from their website.
The person who purchases and receives the orders
If furniture is purchased a commission applies to the sale.
Process
Customer receives newsletters via email monthly for new
events or promotions
The payment method used for orders
Purchasing furniture with the use of the exchange credits
The number of furniture in stock
The act of ordering for the product
The act of paying for the function.
A method of payment.
They are able to manage and perform the tasks that the
system is not in a position to perform.
Business Loyal Customers are offered discounts for their furniture
Rule
purchases.
Role
People who provide information about the item to the
customers and sell it to them.
Role
They have the responsibility of delivering the products to
the customer.
Role
Generate Business and Finance Reports and report them
to the manager monthly.
Business Greater commission percentages for salespeople as they
Rue
sell more items.
Process The prices of the furniture must be decided based on
their quality, material and style.
Object
It shows a list of categories of furniture. The menu can
be available on the website or printed in the form of
brochures.
Process Receiving, recording and applying payments of orders
3
II. Behavioural Modelling [45 marks]
After completing the domain analysis, you are ready to start use case modelling. Using
subsystem “Furniture Sales” in the proposed Furniture Stores information system for
behavioural modelling. Please make sure that you use the domain concepts identified during
the domain analysis activity as the basis for behavioural modelling.
3. Identify stakeholders of the whole system. List them with descriptions using the following
table template.
Name
Production
Manager
Customer
Delivery staff
Administrative
Staff
Quality
Assurance Officer
Accounting
Officer
Furniture Sales
Stakeholders & Actors
Description
Ensures that the furniture’s are ready, oversees obtaining and stock
of crude materials, plans for ordinary and occasions, and keeps up
quality confirmation for getting ready and conveying of item
Spots the item on the web, makes an order, pays for the furniture
with money or credit card. Finally, gives input on items and
administrations
Conveys the furniture, plans for advanced conveyance routing, and
gets installment after conveying the furniture.
Ensure that issues that include customer complaints and feedback are
handled comprehensively.
Ensure that the orders being delivered to customer are in good shape.
Handles all the payments and preparation of sales, expenses and
revenue reports.
4. Create a use case summary for the Furniture Stores IS using the template table below.
Describe the scope of you identified use cases in textual information. Your textual
description should clearly summaries the use case in the following table:
Furniture Stores
Online Pruchasing Management Use Case Summary
ID
Name
Description
Actors
200 Process Orders
Staff gets orders set by clients on the
Sales Staff
web, by bring in, or in-house. When the
request is set, the sales rep, approve the
request individually as per the menu.
Then the staff allocates a request number
and a code that recognizes the kind of
requests in term of in-house, take-out or
conveyance. He/she at that point sends
the coded and numbered requests to the
kitchen. For conveyance orders, he/she
records conveyance address with the
request number.
210 Process
The sales staff records money
Sales Staff
Payments
installment. On the off chance that the
4
220 Record Sales
Details
230 Organize
Delivery
client pays with Mastercard, the sales rep
needs to approve the charge card. If not
legitimate, the online request is dropped
and the client is informed. On the off
chance that Mastercard is substantial, it is
charged at the cost of request. The sales
rep tracks installments by sort of
administration and installment.
Sales staff record and separate deals by
Sales Staff
days of the week and sorts of items sold
and give business insight reports that
would empower the business owner(s) to
recognize famous and disliked items,
repetitive client inclinations, etc. Client
data is likewise overseen for VIP
markdown capability
Sales staff once has gotten the notice
Administrative Staff
from production department that the
furniture is ready for dispatch. They get
the details of the customer and coordinate
the delivery.
5. Complete a use case template for a use case that relates to a customer acquiring a furniture
at a store. Use the blank template below.
Use Case:
ID:
Scope:
Priority:
Summary:
Primary Actor:
Supporting Actors:
Stakeholders:
Generalization:
Include:
Extend:
Precondition:
Trigger:
Normal Flow:
Order online
240
Online Purchasing Management
5/10
To manage the sales portfolio through the coordination of
the sales operations and implementation of sales techniques.
Customer
System
Sales Staff
Service Staff
Not Applicable
250: Charge credit card
Not Applicable
Order the furniture, furniture type, furniture information, the
delivery time.
Customer wants to purchase item
1. Customer explores to the online page of the furniture
stores.
2. Customer chooses an item from the menu.
3. Website informs the customer of the total of what things
have been chosen.
4. Framework calculates the aggregate, deducts special
conclusions (assuming any), includes deals assessment,
and showcases the sum that the client must compensate.
5
5. Customer chooses administration technique (conveyance
or pickup) and the ideal time.
6. Customer enters contact data (telephone and email).
7. Customer enters credit card data.
8. Customer submits request.
9. Framework restores a request number to the customer.
10. Framework informs Sales Staff of the request.
11. Deals Staff surveys request and affirms it.
12. Framework charges Visa. (Incorporate 250: Charge
Credit Card.)
13. Framework submits the request in administration line
(for serving in-house, conveyance or pickup.)
14. Framework prints two duplicates of the request for the
business staff. (One duplicate for the mark if credit card
is utilized; the second for the customer to keep.)
15. Framework messages affirmation to Customer.
16. Staff chooses the issue type from a choice displayed by
the framework. Framework sends the issue to Manager.
17. Chief recommends action(s) and courses to proper staff
member(s).
18. Staff makes a move recommended by Manager.
19. Staff records the consequence of the activity. Î Loop:
Repeat 5 through 6 until all recommended activities are
completed.
20. Staff sends the case to Manager.
21. Chief audits the activities.
22. Supervisor shuts the case.
Sub-Flows:
Alternate Flow/ 2.a. Thing isn’t accessible. Framework covers up (or
Exceptions:
handicaps) the thing.
5.a. Administration technique is conveyance. Customer
includes address.
7.a. Customer chooses money. Client sidesteps credit card
data.
11.a. Request has issues. Deals Staff drops the request and
imparts the issue to Customer (by telephone as well as
email).
Post-Condition: Not Applicable
Non-Behavioral Not Applicable
Requirements:
Open Issues: The administration staff should be able to address any issues
raised by customers online.
Source: Not applicable
Author: Member
Revision & Date 10/10/2020
6
6. Create a use case diagram for “sales management” of Furniture Stores including all use
cases you identified in step a) plus any derived use cases in the subsystem. Make sure you
identify the dependency (include & extend) relationships where applicable.
7. Create an activity diagram for the purchase furniture in the sales subsystem(s).
III. Structural and Dynamic Modelling [30 marks]
After completing the behavioural modelling, you will continue with structural and dynamic
modelling.
8. Identify classes for the Furniture Stores IS. List each class, along with responsibilities and
the use cases they are associated with, using the following table templates.
Class
Staff
▪
▪
Furniture Stores
Preliminary Class Candidates
Responsibilities
Use Cases
Customer name, age, address,
▪ 100: Upload online inventory.
and contact.
▪ 150: Purchase furniture
Sends notifications to
▪ 160: Purchase furniture
customers.
▪ 180: Track furniture
▪ 200: Record deliveries
▪ 300: Finalize deliveries
Payment type
▪ 170: Purchase furniture
The amount paid
▪ 400: Credit exchange for furniture
The commissions applied
▪ 430: Verify payment
Final price calculation
▪ 440: Payment charged
Forward funds
▪ 450: Applied Commission
▪ 460: Forward the funds
Payment
▪
▪
▪
▪
▪
Credit
Card
▪
▪
▪
▪
▪
▪
The card holder’s name
The card’s number
The type of the credit card
The issuer
Charge the card
Number of furniture online
▪
▪
▪
▪
110: Order Online
120: Approve order
430: Authenticate Payment
440: Charge Payment
▪
190: Update online inventory
▪
▪
▪
▪
Furniture information
Delivery information
Customer information
The amount paid
▪
▪
▪
200: Delivery record
210: Finalize delivery
220: Notify the buyer
Online
inventory
Order
7
9. Create a complete class diagram of Purchase furniture of a customer for the point of
view on associations and multiplicity information in the Furniture Stores IS.
Questions: Is there any relationship between classes that can be described by
aggregation/composition? Are there classes that can be generalized/specialized?
Note: Answer the questions separately from the diagram.
Classes visitor and members can be summed up into one single class for obtaining and
making request which can be named purchaser/purchasers.
10. Create a sequence diagram for the process of a custom selecting furniture and completing
an online order on the Furniture Stores website.
8
INFORMATION SYSTEMS
DEVELOPMENT
Table of Contents
Owners view…………………………………………………………………………………………………………………………………………………. 2
Domain Definitions ……………………………………………………………………………………………………………………………………….. 3
Domain Concepts ………………………………………………………………………………………………………………………………………….. 4
Stakeholders & Actors……………………………………………………………………………………………………………………………………. 6
Use Case Summary………………………………………………………………………………………………………………………………………… 7
Use Case Template ………………………………………………………………………………………………………………………………………… 8
Use Case Diagram ……………………………………………………………………………………………………………………………………….. 10
Activity diagram ………………………………………………………………………………………………………………………………………….. 11
Class Candidates …………………………………………………………………………………………………………………………………………. 12
Class Diagram ……………………………………………………………………………………………………………………………………………… 14
Sequence Diagram ………………………………………………………………………………………………………………………………………. 15
Owners view
–
Overview of the different areas of the business
o Not people
e.g., no ‘accountant’, ‘salespeople’, ‘manager’, instead use ‘Accounting’, ‘Sales’, ‘Operations’
or something of that nature
o Not too many
No exact guideline but 4 – 8 would be the ballpark
–
3 – 5 dot points per area (only a few words each – very broad)
Domain Definitions
–
Similar to owner’s view, but with more details in the scope outline
The Pizza Shop
Domain Scope
Domain
Online Ordering
Sales & Order
Management
Food Preparation
Payment Processing
Delivery
Product
Management
Sales Accounting
Customer
relationship
management
Scope Outline
Enable customers to order online.
Present the option for picking up or take away
Enable customers to pay online.
Notify customers of order status.
Notify staff & kitchen of the order.
Manage online, call-in and in-house sales orders.
Coordinate orders with kitchen and delivery
Record customer sales details.
Promote the shop through coupons, advertising, community relations, etc.
Process and package orders.
Ensure correct timing of food preparation.
Ensure on-time serving,
Route multiple deliveries for maximum efficiency.
Process credit card payments.
Accept cash.
Track payments.
Receive the package orders.
Ensure correct address.
Ensure on-time delivery, & pickup.
Route multiple deliveries for maximum efficiency.
Select & formulate the food sold by the shop.
Price the food & prepare menus (in-house, promotion & online).
Select special dishes for holidays.
Manage raw material inventory.
Provide kitchen with recipes.
Control the quality of the food prepared by the kitchen.
Provide on-demand profit & loss statements.
Provide business intelligence (BI) analysis reports.
Manage customer relations information
Update customer VIP information such as adding the number of purchase, and the
total expenditure —not only for qualifying VIP discount, but also for use with
business intelligence (BI) analysis reports.
Record, organize, and handle customer complaints and/or suggestions.
Record, organize, and handle problems with customers, such as invalid credit cards,
absence when food is delivered, bad attitude towards delivery personnel, and so
on.
Domain Concepts
–
Lists the different people (roles), tasks (processes), data (objects), and rules (business rules) that the new
information system will have
Advice:
o Start with ‘Role’ and list all the people that will directly interact with the information system
o Next move to ‘Process’ and think of all the actions/tasks that would need to be executed in this
information system (e.g., ‘Register Account’, ‘Purchase Online’, ‘Request Refund’, etc.)
o Then under ‘Object’ list anything where data is store about an object/entity – making sure it is an
object and not one piece of data, e.g.,
‘Customer’ – contains customerID, firstname, lastname, etc.
‘Order’ – contains orderID, date, time, etc.
‘Item‘ – contains itemID, price, colour, etc.
o Last ‘Business Rules’ will list the rules of the business that are technology independent, e.g.,
A customer get every 10th coffee free
Customers who spend over $100 become VIP
Salespeople receive 5% commission on all sales
The Pizza Shop
Domain Dictionary
Name
Type
Description
Cashier
Role
Accepts and processes payments.
Credit/Debit Card
Object
Used by the customer to make a payment for food
Customer
Role
Person who orders food from the pizza shop.
Delivery Method
Process
The method by which the pizza shop delivers food to the customer; it can
be in-house (served or picked up), or offsite (known as “delivery” in
general)
Delivery Staff
Role
Personnel who deliver the food to the customer off-site
Discount
Business Rule
Reduction in combined prices charged to the customer for promotional
goals
Inventory
Process
Purchase, stocking, and tracking of raw material and other items (gas,
containers, garnishes, etc.) necessary for the preparation of food
Kitchen Staff
Role
Personnel who prepare and package the order.
Menu
Object
List of available food from the pizza shop, along with prices and
discounts. A menu may be electronic (for online ordering) or printed
(for in-house use, promotions or special orders).
Order
Process
Placing, processing, and fulfillment of an order by a customer to the
pizza shop. Order can be given online, by phone or by the walk-in
customer
Order
Object
Specifications of the food requested by the customer; prepared and
sold by the pizza shop, and paid for by the customer.
Payment
Object
Amount received by the pizza shop for the ordered food delivered to
the customer. Payment may be in cash or in electronic form (e.g.,
credit card)
Payment Processing
Process
Receiving, applying and recording payments for orders.
Revenue Tracking
Process
Recording and analyzing the revenue.
Sales Analysis
Function
Harvesting detailed sales data for business intelligence analysis to
enhance revenue and promote the pizza shop
Sales Staff
Role
Person who manages the order cycle
VIP card
object
Card for qualified customers
Stakeholders & Actors
–
List anyone who is affected by the implementation of the information system
o Not always people (e.g., ‘Bank’, ‘PayPal’, ‘RTA’, ‘Tax Office’, etc.)
The Pizza Shop
Stakeholders & Actors
Name
Description
Product Manager
Prepares menu, manages purchasing and inventory of raw materials, prepares
recipes for everyday & holidays, and maintains quality assurance for preparing and
delivering of products
Customer
Places order online, by phone, or in -house, for takeout, delivery or in-house service;
pays for the food with cash or credit card; provides feedback on products and
services.
Sales Manager
Coordinates orders, preparation, and delivery of products; records sales and manages
customer relationship including complaints; handles promotion and advertising.
Delivery Staff
Delivers food, plans for optimized delivery routing*, and receives payment upon
delivering food
Accounting Staff
Processes credit card, records cash payments, handles promotional coupons;
periodically prepares sales, expenses, and revenue reports
Administrative Staff
Handles issues and customer complaints & feedback
Cook
Prepares and packages food
Use Case Summary
–
Give a list of all the use cases (processes) in an area of the business or the entire business
Notes:
o The ID should be unique and follow some meaningful pattern
Easiest way is start at 100 and add 10 each time (100, 110, 120, etc.)
o The name should directly state what the primary actor is trying to do, and should be specific enough
that a list of steps could be given for that process, e.g.,
‘Register account’ is a good use case as it is what the primary actor (e.g., customer)
Order & Sales Management: Use Case Summary
ID
Name
Description
Actors
100 Process
Order
Sales staff receives orders placed by customers online, by call-in, or in-house.
Once the order is placed, the salesperson, validate the order one by one
according to the menu; then assigns an order number and a code that
distinguishes the type of orders in term of in-house, take-out or delivery. The
staff then sends the coded and numbered orders to the kitchen. For delivery
orders, he/she records delivery address with the order number.
Sales Staff
140 Process
Payment
Sales staff records cash payment. If the customer pays with credit card, the
salesperson has to validate the credit card. If not valid, the online order is
canceled and the customer is notified. If credit card is valid, it is charged for the
price of order. The salesperson tracks payments by type of service and
payment.
Sales Staff
160 Record
Sales
Details
Sales staff record and separate sales by days of the week and types of products
sold to provide business intelligence reports that would enable the business
owner(s) to distinguish popular and unpopular products, cyclical customer
preferences, and so on.
Sales Staff
Bank system
Customer information is also managed for VIP discount qualification
170 Organize
delivery
Sale staff once has received the notification from kitchen staff that the meals
are ready to deliver.
Administrative
Staff
The sale staff inform the delivery person
Delivery
person
The name of the customer and address of the customer and the required time
schedule will be passed on to delivery person’s hand.
180 Promote
Pizza
Shop
Administrative staff records details about coupons and specials of the day (or
holidays). The staff schedules the distribution of flyers and organizes efforts to
build community relations.
Administrative
Staff
Use Case Template
–
Goes into detail regarding a particular use case
Notes:
o Use same ID and name from use case summary
o ONE primary actor
o Normal flow – the list of steps that will be follow most times this use case is undertaken
o Sub-Flows – detailed steps from a normal flow
E.g., if the normal flow has a step such as “3. Enter customer details”, the sub-flow would
be:
3a. Enter firstname
3b. Enter lastname
3c. Enter address
3d. Enter phone number
o Alternate/Exception flow – lists the ‘ELSE’ part of a steps. E.g., if we have “2. Select item”, then we
could have an exception flow for this step as:
2a. Item doesn’t exist – select new item
2b. Item doesn’t exist – customer cancels order
Use Case:
ID:
Scope:
Priority:
Summary:
Primary Actor:
Supporting
Actors:
Stakeholders:
Generalization:
Include:
Extend:
Precondition:
Trigger:
Normal Flow:
Process Order
100
Order & Sales Management
1/10
Sales Staff receives orders placed by a customer (call-in or in-house). Sales Staff validates the
availability of items on the order, asks customer’s payment, prints receipts, and queues the
order for the kitchen and serving. If order is for delivery, Sales Staff records delivery address on
the order.
Sales Staff
System (Sales)
Customer
Kitchen Staff: Must prepare food on time and package it correctly.
Service Staff: Must serve (or deliver) the order.
•
510: Charge Credit Card.
500: Validate Credit Card
Customer wants to place an order.
1.
Customer selects an item and quantity.
2.
Sales Staff picks the order item from an on-screen menu and verifies that the item is
available.
Loop: Repeat 1 through 2 until all items are validated and recorded.
3.
Sales Staff totals the price for all items.
4.
Sales Stuff applies discount and promotional deductions (if applicable).
5
Sales Staff records service type and the time when the order should be ready.
6.
Sales Staff records credit card information ( extend 500: validate credit card)
7.
Sales Staff commits the order to the system
8. Staff asks customer to pay the order
(Include 510:Charge Credit Card.)
9.
System places the order in kitchen queue to be processed according to the schedule.
10.System places the order in service queue (for serving in-house, delivery or pickup.)
11.System prints two copies of the order for the sales staff. (One copy for the signature if credit
card is used; the second for the customer to keep.)
Sub-Flows:
Alternate Flow/
Exceptions:
Post-Condition:
Non-Behavioral
Requirements:
Open Issues:
2.1. Service types are as follows:
Delivery
In-House
Pick-up
11.1.Copies of the order must include:
Order Items, quantities and item prices
Applicable sales tax
Total
Date & Time
Payment method with partial credit card info (for security)
Service Method & scheduled time (if not in-house or immediate)
1.a. Item is not available. Sales Staff notifies the customer to select another item
1.b. Item is not available and customer does not want the entire order. Sales Staff cancels the
process.
6.a. Customer pays by cash. Credit Card information is not recorded.
6.b. Customer is ordering in-house. Sales Staff swipes the card and does not record
information manually.
8.a. Customer pays by cash. System does not charge credit card.
Order is taken and is ready for fulfillment.
Source:
Author:
Revision & Date
Step 2: What if the order is for the future? An item may not be available for today, but
what about tomorrow or the day after?
Step 10: We need rules that define how the system queues orders for the kitchen.
Evidently, kitchen should not prepare “future” foods now. If a “timed” order conflicts
with an “immediate” order, which one takes precedence? We need a system use case,
Queue Kitchen Orders.
The whole use case is organized for a “waiter-less” shop. What if the shop has table
service where the customer sits, is served by a waiter in stages, pays last, and may add
a tip to the total? Probably we need a new use case, Fulfill Table Order.
Use Case Diagram
–
–
Shows:
o
o
o
o
Also:
o
o
The system – represented by an outside rectangle
The external actors – represented by stick-figures
The process – shown as ovals with the name of the use case
The associations – A straight line between actor and use case
Include -> this relationship shows another use case that must occur in order for the primary use case
to be executed
Extend -> this shows an optional use case that may be used to achieve the goal of the primary use
case
uc Pizza Order Usecase Diagram
System Boundary
Take order
Sales Staff
Customer
Take Phone
order
«include»
Order Onlline
«extend»
Validate Credit
Card
Credit Card
Company
«include»
«include»
Charge Credit
Card
Queue Kitchen
Orders
Sale system
Activity diagram
–
This diagram shows the flow of events that a user may undertake for a specific process (note: a process here
may be larger than one individual use case)
Note:
o It should show exceptions
E.g., if an items doesn’t exist give the option to pick a new item OR cancel the process
o It will generally have more than one end-point (due to the previous point)
Class Candidates
–
Identify any classes/objects/entities that occur in the system (or given subsystem)
o Same idea in object-orientated programming, or databases (tables)
o The responsibilities list what the class needs to have (i.e., attributes & actions)
o Can ‘mine’ these from use case flows
Use Case:
Take Order
Normal
Flow:
1.
Customer selects an item and quantity.
2.
Sales Staff picks the order item from an on-screen menu and verifies that the item is
available.
Loop: Repeat 1 through 2 until all items are validated and recorded.
3.
Sales Staff totals the price for all items.
4.
Sales Stuff applies coupons and promotional deductions (if applicable).
5. Sales Staff records service type and the time when the order should be ready.
6.
Sales Staff records credit card information ( extend 500: validate credit card)
7.
Sales Staff commits the order to the system
8.
System charges credit card.
(Include 510: Charge Credit Card.)
9.System places the order in kitchen queue to be processed according to schedule.
10.System places the order in service queue (for serving in-house, delivery or pickup.)
11. System prints two copies of the order for the sales staff. (One copy for signature if credit card is
used; the second for the customer to keep.)
Grammatical Objects
Action
Address
Case
Cash
Contact Information
Coupons
Credit Card
Customer
E-mail
Issue
Issue Type
Item
Kitchen Queue
Menu
OnlineOrder Page
Grammatical Objects
Order
Order Item
Order Number
Order Number
Price
Promotional Deductions
Quantity
Sales Staff
Sales Tax
Schedule
Service Method
Class
Comments
Attribute
Value: Payment Type
Attribute
Attribute
Class
Design Class
Comments
Same as Item
Attribute
Attribute
Attribute
Attribute
Actor
Attribute
Attribute
Service Queue
Service Type
Time
Attribute
Attribute
Grammatical Objects
Class
Order
Order Item
Order Number
Order Number
Price
Promotional Deductions
Quantity
Sales Staff
Sales Tax
Schedule
Service Method
Service Queue
Service Type
Time
Class
Order
Responsibilities
Customer Information
Date
Items
Serving Time &Date
Payment Method (Cash or
Credit Card)
Service Method: Delivery,
Pickup or In-House Service)
Sets Order Status: Submitted,
Confirmed, Cancelled, In
Kitchen Queue, In Service
Queue, Served, etc.
Deducts Coupons.
Calculates Total.
Item Name
Item Type: Appetizer, Main
Course, Side Dish, Drink, etc.
Item Price
Quantity
Availability
Payment Type
Payment Amount
Customer
Order
Delivery Type
Delivery Schedule
Sequence in Queue
Order Item
Payment
Service Queue
Comments
Same as Item
Attribute
Attribute
Attribute
Attribute
Actor
Attribute
Attribute
Attribute
Attribute
Use Cases
100: Take Order
210: Order Online
100: Take Order
210: Order Online
100: Take Order
210: Order Online
100: Take Order
210: Order Online
Class Diagram
–
Shows the interrelationships between the different classes
Sequence Diagram
–
Show the time-order events for a specific task/process