Detailed UML Sequence Diagrams for the iDine Restaurant System Project

This project provides a detailed analysis of a restaurant system, likely named iDine or Vallée de Goût, using UML sequence diagrams. The assignment focuses on visualizing and understanding the interactions within the system, including order placement, payment processing, report generation, and inventory management. The diagrams illustrate the flow of events and messages between various actors and objects, such as customers, waiters, chefs, and the database. The sequence diagrams cover key processes like giving an order, paying for an order, generating reports, and updating inventory details. The project demonstrates the use of UML for modeling software systems and documenting their behavior, providing insights into the system's design and functionality. The diagrams are created by the author to depict the interaction between the actors and the objects involved in the system. The project also discusses the different UML diagram elements like actors, lifelines, messages, and their types such as synchronous, asynchronous, and creating messages.

Running head: VALIDATION PHASE
Assignment 3
Name of the Student
Name of the University
Author’s note:

1VALIDATION PHASE
Table of Contents
Give Order Sequence Diagram:.................................................................................................2
Pay for Order Sequence Diagram:.............................................................................................4
See Report Sequence Diagram:..................................................................................................6
Update Inventory Details Sequence Diagram:...........................................................................9
Bibliography:............................................................................................................................11

2VALIDATION PHASE
Give Order Sequence Diagram:
UML stands for Unified Modelling Language which is a well-known modeling
language in the domain of software engineering. It aims to make use of certain number of
standard which is needed for visualizing the overall design of the system (Shen et al., 2016).
UML aims in guiding certain number of ways which needed for creating different kind of
diagrams like interaction, structure and associated behaviors based diagrams. A sequence
diagram is considered to be mostly used interaction diagram.
Interaction diagram: This particular diagram is mainly used for establishing
interaction behavior of this system. It is mainly needed for visualizing the interaction in this
system which can be an important task (Mohapatra, Godbley & Dutta, 2017). There are
different kind of interaction diagram which is needed for capturing the various features and
aspect of this interaction system.
Sequence Diagram: A sequence diagram is mainly used for understanding the
interaction between objects in proper way. The order in which various kind of interaction
comes into picture. An individual can easily make use of term events or even current
scenarios for this sequence diagram (Zhang et al., 2016). Sequence diagram helps in having a
proper kind of understanding how and in what way the objects are placed in system function.
This particular kind of diagram is mainly used by software developers for documenting and
understanding the needs of new and existing system.

3VALIDATION PHASE
Figure 1: Give Order Sequence Diagram
(Source: Created by Author)
Vallée de Goût is well-known cuisine restaurant which is located outside Sydney. It
tends to offer luxurious and fine dining experiences. It emphasizes maintaining the quality
standard for their business which has been growing at a fast pace. In the last few years, there
venue has been overcrowded particularly during the weekends. For overcoming the present
issues in this organization, they are focus to upgrade the present information system. In this,
the main actor is customer which comes up three object that is order, food, and ingredient.
The system will forward each of the order which has been confirmed by the present
customers. The orders mainly come up with different kind of food items. The order system
has been designed in such a way that it can easily provide required information on certain
areas of kitchen and more another category of food. The system will be connected to a printer
so that each of the order can be printed in very easy. It will help the organization in

4VALIDATION PHASE
minimizing any order related problems which can occur due to bad handwriting of waiters.
The cook has simple user interference which is needed for marking the order marked as
ready. The cost of ingredient reflects on the amount used to the given food identity. The food
identity will be reflected back order stage and lastly, the ordered food will be given to the
customer.
Pay for Order Sequence Diagram:
Actors: An actor is kind of UML diagram which is needed for representing a kind of
role by which interaction comes into picture in both the system and its objects. The fact
should be taken into account that actors are always outside the scope of this system. It
focuses on certain number of things for making use of this UML diagram (Barokati, Wajdi &
Barid, 2017). Actors are generally used for understanding the roles which are inclusive of
human users and another kind of external subjects. An actor is mainly provided in the UML
diagram by the help of stick person notation. The organization mainly comes with various
kind of actors in the given sequence diagram.
Lifelines: A lifeline can be easily stated as an element which focuses on individual
participation in the given sequence diagram which provided by the help of lifeline. All the
given lifeline elements are mainly placed on the top of any sequence diagram (Rhmann &
Saxena, 2016). The general structure of UML for naming a lifeline is provided in the given
format that is Instance name is equal to Class name. A lifeline is generally rectangular in
structure which is its head along with name and its type. The head is generally located on the
top of this vertical dashed line. For the model of some unknown instance, a pattern is
followed for understanding the lifeline provided in the bank.
Obliviously, there is certain number of factors between lifeline and actor. A lifeline
can be easily portrayed on different kind of object which is internal to this system (Minhas et

5VALIDATION PHASE
al., 2015). Actors can be easily used for understanding the external objects in this particular
system.
Figure 2: Pay for Order Sequence Diagram
(Source: Created by Author)
In the above diagram, the pay order sequence diagram has been provided. In this, the
food can be ordered by two methods that are tablet and waiter. After the processing of the
food, the invoice of the order item is provided to the customers. Each of the tables of this
restaurant comes up with individual tablet. This particular kind of tablet is known as tabletop
tablet. Each of this tablet comes up with installed digital menu by which order has been
made. Some of the given customers is unable to understand the digital menu which is
considered to be old way of giving orders. Customer can easily click on the given button and
the head waiter will take the order. Waiter can easily handle this device as it comes up with
digital menu. Waiters are considered to be an important part of technological development by

6VALIDATION PHASE
the organization. Waiter is needed for both taking order and delivering orders. Waiter is
needed for managing the orders from customer along with managing the food on customer
tables. Head waiter needs to be assigned for taking order for food from the guests.
See Report Sequence Diagram:
Messages: Communication between various kinds of object can be easily used for
understanding the messages. The given messages mainly come up in sequential order on this
lifeline. Generally, the messages are provided with the help of arrows (Yao et al., 2015). Both
lifelines and messages are considered to be an important part of any sequence diagram.
Messages can be easily classified large number of categories like synchronous messages,
asynchronous messages, creating messages, deleting messages, sending messages, reply
messages, found messages and lastly lost messages.
Synchronous messages: This particular kind of message mainly waits for reply just
before the interaction can move forward (Lecocq et al., 2015). The sender aims to wait until
and unless the receiver has completed the whole process of messaging. Caller tends to
continue until and unless the receiver has completed the method of processing the given
messages. It mainly tends to have a reply message. Generally, there is large number of calls
in object-oriented programming which are known as synchronous in nature (Shen et al.,
2016). A solid arrowhead is used for representing the synchronous messages.
Asynchronous messages: This type of message does not wait for a reply from the
receiver. In this interaction tends to move forward irrespective of the processing of the
receiver of the previous messages (Mohapatra, Godbley & Dutta, 2017). A line of arrow is
mainly used for representing this asynchronous messages.
Creating messages: This particular message is needed for creating new instances of
an object which is provided in the sequence diagram (Zhang et al., 2016). There is certain

7VALIDATION PHASE
number of situation in which a given message needs the creation of new kind of object. It is
mainly needed for creating new kind of objects which is needed for specifying the created
message symbol. For creating new kind of e-commerce website, it would require object of
new order class.
Delete messages: It is mainly used for deleting an object. In this object is mainly
deallocated memory or even destroying within the present system. It mainly makes use delete
message symbol (Barokati, Wajdi & Barid, 2017). It is needed for destroying the occurrence
of any object in the given system. It is generally represented by the help of an arrow ending
with x. In this particular scenario, the order is mainly received by various user so that object
of order class can be easily destroyed.
Self-messages: There is certain number of scenes in which object may need to send
messages to itself (Rhmann & Saxena, 2016). This type of message is called self-messages
which are represented by a U shaped arrow.
Reply messages: This type of messages is mainly used for understanding the
messages which are being from the receiver end to the sender. A return message is provided
by the help of open arrowhead by making use of dotted line (Minhas et al., 2015). The
interaction mainly tends to move forward when the reply messages are being sent by large
number of receiver.
Found messages: It is mainly used for representing a scenario when the source aims
to send the messages (Yao et al., 2015). It is mainly represented by the help of arrow which is
directed towards the lifeline from the given endpoint.

8VALIDATION PHASE
Figure 3: Pay for Order Sequence Diagram
(Source: Created by Author)
The sequence diagram has one actor and two objects. The owner of the organization
asks the system for report. This is initialized by the Report() message. The Report() message
will process which kind of report is to be developed. The report is based on the information
stored in the database. The database holds the information like ordered foods, order details,
ingredients used, inventory details and many more. Based on the type of the report, the
system will collect the data and process those data to generate various information. Taken as
an example, by processing all the order and customer details, the system can determine who
has ordered most food or who is a regular customer and more. All these information along
with the requested data are presented in the report. The system, after generating the report,
distributes all those reports or a single report to authorized staff or only management of
Vallée de Goût. This sequence diagram visualizes the report accessing process of the iDine

9VALIDATION PHASE
system. This process is also mentioned in the functional requirement and use case diagram.
The database is not an actual object in the iDine system.
Update Inventory Details Sequence Diagram:
Figure 4: Update Inventory Details Sequence Diagram
(Source: Created by Author)
The sequence diagram shows that an actor will communicate with an object to
complete the update inventory process. The actor will call the system’s ingredient class to
check the ingredient amount related information stored in the database. The system then
shows the actor the list of ingredient and available amount. After the management check the

10VALIDATION PHASE
inventory and find that actual available amount. If the data does not match, the management
will update the stock by calling the updateStock() message. After the stock is updated, the
system shows the available amount. The updateStock() message is also called when new
stock of ingredient is delivered to Vallée de Goût.

11VALIDATION PHASE
Bibliography:
Barokati, N., Wajdi, N., & Barid, M. (2017). Application Design Library With gamification
concept. Jurnal Lentera: Kajian Keagamaan, Keilmuan dan Teknologi, 3(1), 93-102.
Knapp, A., Mossakowski, T., & Roggenbach, M. (2015). Towards an Institutional
Framework for Heterogeneous Formal Development in UML. In Software, Services,
and Systems (pp. 215-230). Springer, Cham.
Lecocq, F., Teufel, J. D., Aumentado, J., & Simmonds, R. W. (2015). Resolving the vacuum
fluctuations of an optomechanical system using an artificial atom. Nature
Physics, 11(8), 635.
Mani, P., & Prasanna, M. (2017). Test case generation for embedded system software using
UML interaction diagram. J Eng Sci Technol, 12(4), 860-874.
Meedeniya, D., Perera, I., & Bowles, J. (2016). Tool support for transforming Unified
Modelling Language sequence diagram to coloured Petri nets. Maejo International
Journal of Science and Technology.
Minhas, N. M., Qazi, A. M., Shahzadi, S., & Ghafoor, S. (2015). An Integration of UML
Sequence Diagram with Formal Specification Methods—A Formal Solution Based on
Z. Journal of Software Engineering and Applications, 8(08), 372.
Mohapatra, D. P., Godbley, S., & Dutta, A. (2017). Measuring Hit ratio of Software Systems
using UML Sequence Diagram.
Osman, H., & Chaudron, M. R. (2018). Correctness and Completeness of CASE Tools in
Reverse EngineeringSource Code into UML Model. GSTF Journal on Computing
(JoC), 2(1).