Creating UML diagram for online booking system

This document provides a step-by-step guide on creating a UML diagram for an online booking system. It covers the use case diagram, use case description, activity diagram, sequence diagram, domain model class diagram, state machine diagram, and user interface. The guide also explains the importance of UML diagrams in system development.

Creating UML diagram according to the
case study
1

Contents
INTRODUCTION...........................................................................................................................3
MAIN BODY..................................................................................................................................3
Use case diagram.........................................................................................................................3
Use case description....................................................................................................................4
Activity Diagram.........................................................................................................................6
Sequence Diagram.......................................................................................................................8
Domain model class diagram.......................................................................................................9
State machine diagram...............................................................................................................11
User interface.............................................................................................................................12
CONCLUSION..............................................................................................................................12
REFERNECES..............................................................................................................................14
2

INTRODUCTION
UML stands for unified modelling language that standardized language which mainly
consists of an integrated set of diagram. In order to develop the system and developers for
specifying, visualising, constructing and documentation software system. The report is mainly
focused on the hotel online booking system where customer, staff member, receptionist
performed the significant role in which providing the better service to the customer. This type of
online booking system will always support for improving and enhancing overall business
capabilities. It is to be consider as efficient system where potential consumer check the
availability of room. Moreover, it also performing the bill payment service through online
option. Each and every system process will be representing through UML diagram. It is the
mostly graphical way to express flow of information or data. Before developing new system
which require to understand the flow of information in step by step manner.
MAIN BODY
Use case diagram
Figure 1 Use case Diagram
3

A use case diagram is the simplest way to representation of user’s interaction within online
booking system (Roy, Shahdeo and Kaluri, 2019). It mainly shows the relationship between
users and different use cases. In above figure: 1, it has been represented the use diagram where
system, system and employee are performing the different action for exchanging data between
them. It is way to establish the relationship between them (Dadeau, Fourneret and
Bouchelaghem, 2019).
By using use case diagram, it is mainly understanding the behavior through diagrams and
describe to set of action that some system. It should be collaboration with one or more external
user of system.
Use case description
Use case Name Use case of online booking system
Description The online booking system use case is mainly
described the different process where
performed the task. Customer want to register
and create account so that they can easily
check availability rooms and other facilities.
Actors  Customer
 System
 Employee/ reception/manager
Flow of action  Initially, customer register on the
online booking system in order to
create account.
 Afterwards, user can enter username,
password to login their own account.
 Clicking on the room while identifying
availability of room.
 System will automatically store or
collect the information of person who
4

will check the room.
 Afterwards user make payment through
online and receiving confirmation
message.
Pre-condition User can login the account by using own
username, password
Post condition After selecting room, user can make payment
through credit card.
Exceptional case In some situation, user forget the password of
account and it cannot received confirmation
from admin side.
Table: 1
5

Activity Diagram
Figure 2 Activity Diagram
An activity diagram is illustrate the flow of control in the online booking system. It is mainly
refer to the steps which involved in the execution of user case. The activity diagram is the
sequential and concurrent activities (Khazri, Fahli and Naddami., 2019). Generally, it depicts
workflow that visualise by using activity. It is focused on the different condition and flow of
information in which it occurs. In order to describe that what cause a particular event.
6

In above diagram, it has summarised that customer access the system to inquire about the
booking/ reservation about the particular room in the hotel. If they are not registered on the
system so that they mainly following steps to create account (Roy, Shahdeo and Kaluri, 2019).
Furthermore, use will check the availability of room. System will easily identify that particular
customer login or not within system. If online system has found and further move another step.
On the other hand, if it cannot find the identity which automatically terminated (Lima, Tavares
and Nogueira, 2019). In order to give instruction for client regarding the detail submission.
Afterwards, it automatically store the customer detailed in proper manner. At last, consumer will
select the credit for entering the information in the system and then complete the process.
in this way, it has been representing the flow of activity diagram where user perform
different role within booking system. it provide the better facilities where individual person can
easily clear their doubts.
7

Sequence Diagram
Figure 3 Sequence Diagram
Sequence diagram is based on the interaction diagram that mainly useful for describing the
online booking system in proper manner. By using this diagram, it will be understanding the
interaction between customer and system. customer sending the request in the system for purpose
of room booking where they can easily access the information to check availability (Roy,
Shahdeo and Kaluri, 2019). Afterwards, administartor send back the response and confirm the
booking status. Furthermore, customer has been selecting the online option to make payment and
transfer money. Afterwards, it will get back the recepit details when booking has been
successfully completed. Therefore, it will be performed the communication between customer,
administrator within online system.
8

Domain model class diagram
Figure 4 Domain model class diagram
A class diagram is mainly providing the overview of target system which mainly describing
objects, classes inside the system. It will be creating a relationship between one or more classes.
Furthermore, this provide wide range of usage from modelling the domain specific data structure
in detailed design of online booking system (Tampubolon and Triana, 2019). In above figure: 4,
It is describing the class diagram where existing customer, rooms, receptionist, owner/
employee/manager. Each and every contained the unique id so that they can established the
relationship between them.
Customer  Id
 Name
 telephoneNo
 Address
Owner/ manager/  Id
 Name
 telephoneNo
9

 Address
Receptionist  Id
 Name
 telephoneNo
 Address
Bill  Bill no
 Customer name
Room  Room no
 Location
Table: 1
A domain class model generally implemented as an object model within different layers. It is
mainly used to lower level which prescribed and publish as an application. In order to gain
access to data as well as behavior of model (Tampubolon and Triana, 2019). It is consider the
most understanding and benefits of new system design. The object based nature always support
for creating architecture which govern the development of application. Sometimes, it also insists
on the basis of their reusability as well as cohesiveness of objects.
10

State machine diagram
Figure 5 State Machine Diagram
State machine diagram is basically describe the state-dependent behaviour for different
object. In this way, it give a proper responds different way to perform same event. Sometimes, it
is depending on what state it applicable. State machine diagram is representation that applied to
the object but identify the behaviour of another entities such as subsystem, methods, actors and
other cases (Tampubolon and Triana, 2019). Apart from that they are typically used in the
conjunction with interaction between different ways.
In figure-5, it has followed the steps from first end to last end. Initially, use will be doing
registration on the system while checking the availability of room according to demand of
customer. Afterwards, it will be providing the confirmation through online system. Another step
is to choose payment option where they can easily completed the booking process in proper
manner.
11

User interface
The user interface is based system design which mainly explaining the system works by
processing secure online booking (Tampubolon and Triana, 2019). There will be data passed
onto backend system which can easily accessed by hotel to manage booking. Another way, it
may come with the automation of booking system which will provide confirmation message to
client.
Generally, user interface design is basically produced a user which make it easier, efficient to
understand. On the other hand, it also operates a machine in the way which identified the
desirable result or outcome (Roy, Shahdeo and Kaluri, 2019). It means that operator needs to
provide the minimal input and achieve the better outcome. User interface are composed of
multiple layers that machine perform task. In additional, it may interact with one or more human
sense to include different activities.
12

CONCLUSION
From above discussion, it has concluded that UML stands for unified modelling language
that standardized language which mainly consists of an integrated set of diagram. In order to
develop the system and developers for specifying, visualising, constructing and documentation
software system. It has been summarised about the online booking system where customer, staff
member, receptionist performed the significant role in which providing the better service to the
customer. The online booking system provide the facilities and services of potential customer
such as bill payment, transaction, search information, check availability of rooms. It is the best
way to increase the business performance as well as efficiency in global marketplace. It has
understand the graphical way to express flow of information or data. Before developing new
system which require to understand the flow of information or data effectively.
13

REFERNECES
Book and Journals
Dadeau, F., Fourneret, E. and Bouchelaghem, A., 2019. Temporal property patterns for model-
based testing from UML/OCL. Software & Systems Modeling. 18(2). pp.865-888.
Khazri, Y., Fahli, A., Moussetad, M. and Naddami, A., 2019. Design and Implementation of a
Reservation System and a New Queuing for Remote Labs. International Journal of
Online and Biomedical Engineering (iJOE). 15(12). pp.57-68.
Lima, L., Tavares, A. and Nogueira, S.C., 2019. A framework for verifying deadlock and
nondeterminism in UML activity diagrams based on CSP. arXiv preprint
arXiv:1910.13638.
Roy, A., Shahdeo, V. and Kaluri, R., 2019. A Comparative Study in Online Movie Ticket
Booking System. Research Journal of Engineering and Technology. 10(1). pp.16-20.
Tampubolon, F.J. and Triana, Y.S., 2019. ANALYSIS AND DESIGN OF ORDERING
SYSTEM OF BUILDING MATERIAL AND EQUIPMENT CASE STUDY: SERBA-
JAYA BUILDING SHOP. Science. 5. pp.160-167.
14