[Document title]

[Document subtitle]

Abstract
[Draw your reader in with an engaging abstract. It is typically a short summary of the document.
When you’re ready to add your content, just click here and start typing.]

[Email address]
Table of Content
Introduction...........................................................................................................................................1
Use Case.................................................................................................................................................1
Sequence Diagram.................................................................................................................................3
Domain Model Diagram.........................................................................................................................3
Class Diagram.........................................................................................................................................5
Reflection...............................................................................................................................................6
Conclusion..............................................................................................................................................6
Introduction

This report deals with an online booking system of a birthday party club, which will help to handle
birthday party reservations. The Club presently operates on a manual booking system, which is getting
increasingly difficult to manage. The existing system is inefficient and takes a long time to complete.
Customers can currently book a party by calling or visiting the Club in person. The club's administrator
assists them in selecting a Party room based on a variety of parameters, including Day, Time, Number of
Hours, Number of People, and Availability. They are making a new system with the following
requirements:

1. To create a new booking, a customer must first login or register.

2. The customer will specify the day, time, and number of individuals for whom they like to reserve
a space, as well as the food and beverage options for the party.
3. The system will then select available rooms based on the Customer's needs.
4. The customer can choose from a variety of options offered by the system.
5. The customer can then select the item(s) in which he or she is interested and complete the
payment process.
6. The Customer will receive a print or email copy of the Booking confirmation after a successful
payment.

Objectives of new system

1. Book for a party
Customers will be able to reserve a Birthday Party Room using this method.
2. Online payment
Customers will be able to pay for their reservations online using this technology.
3. Better knowledge
This system will provide all of the details of the Party Room, as well as a map of the room, to the
customer before they confirm their bookings.
4. Reduce paperwork
Because the majority of the work will be done online, the Club will use less paper.
5. Improves Efficiency
Staff will have it easier with this approach because the entire booking system will be online
6. Improved Customer Services
Customers must first register before making a reservation through the new Online Booking
System.

1
Use case

This UML diagram deals with the sequence of activities or event stages that explain how a role (called an
actor in UML) interacts with the system to accomplish its objectives. This UML diagram consists of
actors, they can be a person or any external systems. This diagram is used at a higher, and they usually
represent missions and stakeholder’s goal.

Figure 1: Use case diagram

The above diagram shows the functional interpretation of the system. The actor customer here interacts
with different functions of the system.

2
System: On the website, the system registers/logs in a customer. The algorithm examines all of the
information provided by the consumer and suggests the best and most convenient accommodations.
Similarly, the system prints a statement or sends an email once the customer has completed all of the
selection steps and completed the transaction.

Customer: A customer must first register on the system, after which they must provide the day, hour,
and number of people who will be attending, all of which will be reviewed by the system, and the
available accommodations will be displayed. The customer can then browse the various room
alternatives and choose the one that best meets their requirements. Customers then go to the payment
section, where they will receive an email or a printed copy confirming their valid reservation for
purposes of explanation.

Pre-conditions:

 The consumer is now1logged in with the appropriate credentials after registering with the
system, and his or her information has been saved in the system.

Main flow:

 The consumer enters the date, location, and number of guests for the birthday celebration into
the system, which then processes the information and displays room availability.

Alternative flow:

 If a customer provides erroneous information, the system will still indicate room availability, but
not the one they desire; if a customer makes a slight error while making a payment, the entire
process may have to be repeated.

Post-conditions:

 The customer selects the accommodation that is best suited to their needs after checking the
room availability.
 The customer then proceeds to pay for their room in advance.
 Following a successful transaction, the system often sends an email or prints a record.

Sequence Diagram

3
A sequence diagram is one of interaction diagram types that illustrates how the objects in the system
interact with each other. Developers and businesspeople can use these diagrams to understand
requirements for a new system or describe any existing process. A sequence diagram can also be knows
as an event diagram or an event scenario, this shows a visual representation of a succession of events.
Sequence diagrams describe how the orders of various components of a system interacts.

Figure 2: Sequence Diagram

The above diagram shows the interaction of customer with the various objects of the system within the
time. Different messages are shown will the objects in the system interacts with each other.

Domain Model Diagram

In the Unified Modelling Language, a Domain Model is a representation of conceptual or real-world

objects and classes. Conceptual classes and domain object models are terms used to describe domain

4
models. A domain model is represented by a collection of class diagrams with no operations in UML
notation. Domain models describe entities or things, as well as their relationships. To model diverse
domains, a number of diagrams and methodologies can be utilized. It's critical to design visually
appealing diagrams to demonstrate how entities interact.

Figure 3: Domain Model class

Class Diagram

Object-oriented modelling requires the use of a class diagram. This diagram is useful for both conceptual
and detailed modelling, as well as the conversion of the models into computer code. This diagram can
also be used to model data. A class diagram is used to show an application's fixed perspective. The only
diagrams that can be readily converted to object-oriented languages are class diagrams, which makes

5
them handy in the construction process. Class diagrams are used to build forward and reverse
executable code as well as to define the system's static perspective.

1..*

1..*

1..*

1..*

1..*

Figure 4: Class Diagram

The graphic depicts the many classes that are included in the system and how they interact with one
another.

Reflection

I have learned about the different UML diagrams that are present. This report has given me a brief idea
of what UML diagrams are and what are the uses of the UML diagrams. I have learned to make the UML
diagrams and learnt to interpret them. I have learnt that use case diagram shows the functional

6
operations of the system, while sequence diagram shows the time of the interaction and class diagrams
how the different classes that will be presented in the system. I also learned the difference between a
domain model diagram and a class diagram.

Conclusion

Finally, this report specifies the new system the party club is making. The Club now has a manual
booking system, which is getting increasingly difficult to manage. The existing system is inefficient and
takes a long time to complete. Customers can currently book a party by calling or visiting the Club in
person. The new system will help them to track the customers and remove the manual records keeping.
The club's administrator assists them in selecting a Party room based on a variety of parameters,
including Day, Time, Number of Hours, Number of People, and Availability. This report also contains the
UML diagrams for the new system.