Академический Документы
Профессиональный Документы
Культура Документы
{Pizza Vera}
Author (s): _______Lushan Chokalingam ________ Date: ____2015/03/28_______
Version: ___1.0________
Step 19: the clerk confirms the order Step 20: the system adds a new order to the order
details on the system table and notifies the kitchen staff of a new order
Step 21: the system notifies the clerk that the order
was successfully placed.
Step 22: the system generates an invoice with an
order number , client name, surname, address,
contact number, items ordered with quantity and price
as well as order total
Step 23: the clerk communicates the
order total to the client and requests the
payment information.
Step 24: the client provides the payment
information to the clerk
Step 25: the clerk requests the system to Step 26: the system asks the clerk to choose the type
record the payment information of payment (cash or card)
Step 27: the clerk chooses the type of Step 28: the system asks the clerk to confirm the
payment and adds the payment payment information
information
Step 29: the clerk confirms the payment Step 30: the system records the payment information
information
Step 31: the system notifies the clerk that the
payment information was successfully recorded.
Step 32: the system generates a receipt with order
details and payment information.
Step 33: the system generates a preparation order
which includes the order details (order number,
products and quantity)
Step 34: the user action information is added to the
audit trail
ALTERNATE COURSES: Alt step 3: the client is not registered and use case 2.1 – Register client is invoked
Alt step 14: the client selects the order for delivery and the order is added to the a delivery list and
the use case continues at step 15
Alt step 23: the clerk communicates the order total to the client and if the order is for delivery, the
use case concludes.
CONCLUSION: The use case concludes when the order is placed and payment is received.
POST-CONDITION: The order number is generated.
BUSINESS RULES The client can request a delivery or pick up, order options for receiving order method.
IMPLEMENTATION None
CONTRAINTS AND
SPECIFICATIONS
ASSUMPTIONS: None
OPEN ISSUES: None
USE CASE NAME: Update Order USE CASE TYPE
USE CASE ID: 3.2 Business Requirements:
PRIORITY: High System Analysis:
SOURCE: Pizza Vera System Design:
PRIMARY BUSINESS ACTOR Client
PRIMARY SYSTEM ACTOR Clerk
OTHER PARTICIPATING Kitchen staff
ACTORS: Driver
OTHER INTERESTED None
STAKEHOLDERS:
DESCRIPTION: This use case describes the event of a client updating or changing any details of his/her order. The
client requests the clerk to edit the order on the system and provides his/her changes and
concludes when the order is updated.
PRE-CONDITION: There must be an existing order
TRIGGER: The client wants to update an order
TYPICAL COURSE Actor Action System Response
OF EVENTS: Step 1: The client wants to update an
order
Step 2: the clerk requests the client to
provide the order details
Step 3: the client provides the order
details to the clerk
Step 4: the clerk requests the system to Step 5: the system invokes use case 3.7 search order
update an order
Step 6: the system asks the clerk to update the order
details
Step 7: the clerks requests the client to
provide the updated information for the
order
Step 8: the client provides the updated
order information
Step 9: the clerk add the updated order Step 10: the system asks the clerk to confirm
information onto the system updating the order
ALTERNATE COURSES: Alt Step 8: the client doesn’t confirm that the order be canceled. The use case terminates
Alt step 9: the clerk doesn’t confirm that the order be canceled. The use case terminates
CONCLUSION: This use case concludes when an order is successfully canceled.
POST-CONDITION: Order is canceled
BUSINESS RULES Refunds on card payments will be given in cash.
Canceling order must be done within five minutes of placing the order.
IMPLEMENTATION None
CONTRAINTS AND
SPECIFICATIONS
ASSUMPTIONS: The client cancels the order within five minutes of placing the order.
OPEN ISSUES: None
USE CASE NAME: Confirm Prepared Order USE CASE TYPE
USE CASE ID: 3.4 Business Requirements:
PRIORITY: High System Analysis:
SOURCE: Pizza Vera System Design:
PRIMARY BUSINESS ACTOR Kitchen Staff
PRIMARY SYSTEM ACTOR None
OTHER PARTICIPATING Clerk
ACTORS: Client
OTHER INTERESTED None
STAKEHOLDERS:
DESCRIPTION: This use case describes the event of an order completing its preparation and being handed over to
the clerk for the client to collect. The kitchen staff updates the order status to complete and the
clerk and client are notified.
PRE-CONDITION: An order must have been placed
TRIGGER: The order is prepared and ready
TYPICAL COURSE Actor Action System Response
Step 1: The order is prepared and ready
OF EVENTS: Step 2: the kitchen staff request the Step 3: the system displays a list of orders which are
system to update the order status not ready and prompts the kitchen staff to select the
order which is prepared and ready
Step 4: the kitchen staff selects the order Step 5: the system updates the order status of that
order to prepared and ready
Step 6: the system adds the order to the prepared
order list
Step 7: the system notifies the client and the clerk
that the order is ready
Step 8: the user action information is added to the
audit trail
ALTERNATE COURSES: None
CONCLUSION: The use case concludes when the order status is changed to prepared and ready and the client
and the clerk are notified.
POST-CONDITION: The order is prepared.
BUSINESS RULES None
IMPLEMENTATION None
CONTRAINTS AND
SPECIFICATIONS
ASSUMPTIONS: none
OPEN ISSUES: None
USE CASE NAME: Deliver order USE CASE TYPE
USE CASE ID: 3.5 Business Requirements:
PRIORITY: High System Analysis:
SOURCE: Pizza Vera System Design:
PRIMARY BUSINESS ACTOR Driver
PRIMARY SYSTEM ACTOR None
OTHER PARTICIPATING Client
ACTORS:
OTHER INTERESTED Clerk
STAKEHOLDERS:
DESCRIPTION:
IMPLEMENTATION None
CONTRAINTS AND
SPECIFICATIONS
ASSUMPTIONS: The order prepared was correct for the appropriate client
OPEN ISSUES: None
USE CASE NAME: Reconcile Delivery Payments USE CASE TYPE
USE CASE ID: 3.6 Business Requirements:
PRIORITY: High System Analysis:
SOURCE: Pizza Vera System Design:
PRIMARY BUSINESS ACTOR Driver
PRIMARY SYSTEM ACTOR Clerk
OTHER PARTICIPATING None
ACTORS:
OTHER INTERESTED Owner and manager
STAKEHOLDERS:
DESCRIPTION: This use case describes reconciliation delivery payments, in which the system reconciles that a
payment received from a delivery matches the payment for the order delivered.
IMPLEMENTATION None
CONTRAINTS AND
SPECIFICATIONS
ASSUMPTIONS: Check
OPEN ISSUES: None
USE CASE NAME: Search order USE CASE TYPE
USE CASE ID: 3.7 Business Requirements:
PRIORITY: Medium System Analysis:
SOURCE: Pizza Vera System Design:
PRIMARY BUSINESS ACTOR Manager
PRIMARY SYSTEM ACTOR None
OTHER PARTICIPATING none
ACTORS:
OTHER INTERESTED none
STAKEHOLDERS:
DESCRIPTION: This use case describes the event of performing a search of orders and selecting an order and
displaying that order information.
PRE-CONDITION: The manager must be logged into the system.
An order must already exist
TRIGGER: The manager wants to search an order
TYPICAL COURSE Actor Action System Response
OF EVENTS: Step 1:The manager wants to search an Step 2: the system asks the manager to add order
order search information
step 3: the manager adds the search step 4: the system displays a list of all relevant orders
information that meet the search information
Step 5:the system asks the manager to select an
order
Step 6: the manager selects an order Step 7: the system displays the selected order
information
ALTERNATE COURSES: None
CONCLUSION: The use case ends when an order has been successfully searched and information regarding the
order is displayed.
POST-CONDITION: Order information is displayed.
BUSINESS RULES none
IMPLEMENTATION none
CONTRAINTS AND
SPECIFICATIONS
ASSUMPTIONS: none
OPEN ISSUES: none