- 2069 Poush · 6 marks
Food ordering system sequence diagram
Short answer
Customer requests a seat; system coordinates with SeatingManager for table assignment. The customer then views menu, adds items in a loop, confirms order, requests bill, makes payment, and releases the table. System responds with table number, menu, order number, bill, and receipt.
Construct a system sequence diagram for customer from a "Food ordering system" of a very busy restaurant where seating and ordering is regulated by seating manager.
A system sequence diagram (SSD) treats the whole system as one black box (:System) and shows the events that the actor (Customer) generates and the system's responses, in time order.
Assumptions: the restaurant is busy, so the seating manager gives the customer a table (seat) first, then the customer orders, eats, and pays. The customer interacts with the system through a tablet/terminal. Actors: Customer, SeatingManager (supporting actor).
Customer :FoodOrdering System SeatingManager
| requestSeat(partySize) | |
|----------------------->| |
| | findTable() |
| |-------------->|
| |<- - - - - - - |
|<- - - tableNo or wait--| |
| viewMenu() | |
|----------------------->| |
|<- - - - menu - - - - - | |
| loop [more items] |
| addItem(itemId, qty) | |
|----------------------->| |
|<- - - - - item added - | |
| end loop |
| confirmOrder() | |
|----------------------->| |
|<- - - orderNo, total - | (sent to kitchen)
| requestBill() | |
|----------------------->| |
|<- - - - - bill - - - - | |
| makePayment(amount) | |
|----------------------->| |
|<- - - - receipt - - - -| |
| | releaseTable()|
| |-------------->|
Explanation of the events
requestSeat- system asks the seating manager for a free table; if none is free, the customer is put in a waiting queue.viewMenu- system returns the menu.addItemrepeated in a loop for each dish.confirmOrder- order number and total returned; kitchen is notified.requestBill,makePayment- bill and receipt are produced.- Table is released so the next party can be seated.
Dashed lines are returns. The loop fragment shows repetition of addItem.
✓ Answer checked by Claude Opus 5.5 (high effort)
Related questions
- External actors and library system sequence diagram · Object Oriented Analysis and Design, chapter 2
- KUKL customer system design and code · Object Oriented Analysis and Design, chapter 4
- ATM withdrawal sequence diagram · Object Oriented Analysis and Design, chapter 2
- Event management system summary and class diagram · Object Oriented Analysis and Design, chapter 2
- Explain online order sequence diagram · Object Oriented Analysis and Design, chapter 2
- Money transfer sequence diagram questions · Object Oriented Analysis and Design, chapter 2
- Restaurant information system requirements · Software Engineering, chapter 1
- Sequence detector 1011 state diagram and VHDL · Embedded System, chapter 9
- Plot sequence; properties of LTI system · Digital Signal Analysis and Processing, chapter 1
- Reactance diagram of eight-bus system · Power System Analysis I, chapter 3
All Object Oriented Analysis and Design chapter 2 questions →