Sequence Diagram .

Running head: SEQUENCE DIAGRAM
Sequence Diagram
Name of the Student
Name of the University
Author’s note:

1SEQUENCE DIAGRAM
Table of Contents
1. Placing Order:..............................................................................................................................2
2. Order Preparation and Serving:...................................................................................................4
3. Inventory Management:...............................................................................................................6
Bibliography:...................................................................................................................................8

2SEQUENCE DIAGRAM
1. Placing Order:
Figure 1: Sequence Diagram for Ordering Food
(Source: Created by Author)
The figure 1 shows a condition statement. The lifeline of the customer placing is order
seems like bigger than the waiter placing order. But as it is a condition statement, it is to be noted
that lifeline of both the message is same.
The above sequence diagram shows how the system will capture the scenario for
placement for order. Vallée de Goût wants its iDine system to accept order in two ways. The first
way will be directly by the customer. The customers will access the tablets installed in each table
for placing the order. As the tablet will have a digital menu that can adjust quantity and note
special notes, there will be no need for a waiter. However, not all customers can be confidence of
placing order directly. For those customers, the tablets will have a button called ‘Call Waiter’.

3SEQUENCE DIAGRAM
By clicking on this button, the customer can request for a waiter. Once the waiter arrives, the
customer can tell what to order verbally and the waiter through his tablet can place the order. The
sequence diagram shows that if waiter places the order then a parameter is added in the method.
This is because, the tabletop tablets already have the table number stored so the order() method
sends the table number automatically. However, the waiter have to put the table number while
placing the order. That is why table number is added as a parameter in the method. Another vital
reason for adding a parameter is implementing method overloading. The system will easily
identify which order is placed by waiter and which is placed directly.
Now once the order is confirmed, the system will create an object of the order class.
However, it has to be noted that the order shown in figure 1 is the object itself. Just for making
the scenario of system behavior more understanding, the createObject() method is called. This is
a self-calling method. This means that this method will be called by the internal object and its
lifecycle will end serving the purpose of its class. No other external objects can access this
method. The self-calling methods can be assigned as the protected or private access modifier. All
the other methods will have public access modifier. It is because, the methods will be called by
other objects too. Such as the Order() method is defined in order class but it is called by the
customer or the waiter. Each order has many foods with different quantities. The order object
must store the ordered food details for preparation, serving and invoice creation purpose. The
addFood() method is for adding the food name or number to the order class. It is essential to
remember that the system will have all the details of the food that is being ordered. The food that
is not listed in the system cannot be seen on the digital menu. If the food is added, the method
will generate a result that will show success message on the screen.