Professional Documents
Culture Documents
Blackbook - 448 Sem 6 Final
Blackbook - 448 Sem 6 Final
A Project Report
Submitted in partial fulfilment of the
Requirements for the award of the Degree of
By
Prof. Omprakash
Assistant Professor
CERTIFICATE
This is to certify that the project entitled, "Hotel Management System", is bonafide work of Rohima Arun
Phalke bearing Seat No: 448 submitted in partial fulfilment of the requirements for the award of degree of
BACHELOR OF SCIENCE (COMPUTER SCIENCE) from University of Mumbai.
External Examiner
I express my sincere thanks to the Professor Omprakash Prajapati, Guru Nanak Khalsa
College of Arts, Science & Commerce, University of Mumbai who has given me the
opportunity to pursue my BACHELOR OF SCIENCE (COMPUTER SCIENCE) also
express my thanks to CO-ORDINATOR and other staff of the CS Section.
I would like to thanks my guide (Omprakash Prajapati Sir) for his encouragement and
guidance, which helped me in completing the project.
A. Introduction 6
2. Gantt Chart 8
9
B. System Analysis
10
1. Class diagram
2. Activity diagram 12
3. Context diagram 15
4. Sequence diagram 18
C. System Design 23
1. Database Connection 28
2. Validations 31
3. Conclusions 32
Project Synopsis
Room Enquiry and Reservation: This module deals with reservation enquiry and
Reservation
Bills and Payment Module: The modules deals with the generation and tracking of bills
and payments made by the guest
Staff Management System: This module keeps the record of the staff
a)Hardware Requirement
Operating System : Windows 10
Hard Disks : 1TB
RAM : 8GB
b) Software Requirement
Visual Studio
Excel
MySQL
5) CONCLUSION
The application “Hotel Management System” reduces the drawbacks like burden
of maintain records. It saves time and provides twenty-four hours accessibility .
GUI makes the interface very much user friendly. The system is highly user
friendly and is well efficient to interactions with the users of the system
SYSTEM
ANALYSIS
1.CLASS DIAGRAM
Class diagram is a main building block of object-oriented modelling. It is
used for general conceptual modelling of structure of application, and for detailed
modelling translating the models into programming code.
Class diagram can be used for data modelling. The classes in class diagram
represents both the main elements, interactions in application, and classes to be
programmed.
In the diagram, classes are represented with boxes that contain three compartments:
• The top compartment contains the name of the class. It is printed in bold,
centred and the first letter is capitalized.
• The middle compartment contains the attributes of the class. They are
leftaligned and the first letter is lowercase.
• The bottom compartment contains the operations the class can execute. They
are also left-aligned and the first letter is lowercase.
In the design of a system, a number of classes are identified and grouped together
in a class diagram that helps to determine the static relations between them. With
detailed modelling, the classes of the conceptual design are often split into a number
of subclasses.
Class Diagram:
2.ACTIVITY DIAGRAM
Activity diagram is another important diagram in UML to describe the dynamic
aspects of the system.
Activity diagram is basically a flowchart to represent the flow from one activity to
another activity. The activity can be described as an operation of the system.
The control flow is drawn from one operation to another. This flow can be
sequential, branched, or concurrent. Activity diagrams deal with all type of flow
control by using different elements such as fork, join, etc
The basic purposes of activity diagrams is similar to other four diagrams. It captures
the dynamic behaviour of the system. Other four diagrams are used to show the
message flow from one object to another but activity diagram is used to show
message flow from one activity to another.
Activity is a particular operation of the system. Activity diagrams are not only used
for visualizing the dynamic nature of a system, but they are also used to construct
the executable system by using forward and reverse engineering techniques. The
only missing thing in the activity diagram is the message part.
It does not show any message flow from one activity to another. Activity diagram
is sometimes considered as the flowchart. Although the diagrams look like a
flowchart, they are not. It shows different flows such as parallel, branched,
concurrent, and single.
The purpose of an activity diagram can be described as −
Draw the activity flow of a system.
• Describe the sequence from one activity to another.
• Describe the parallel, branched and concurrent flow of the system.
• Start symbol
Represents the beginning of a process or workflow in an activity diagram. It
can be used by itself or with a note symbol that explains the starting point.
• Activity symbol
Represents a decision and always has at least two paths branching out with
condition text to allow users to view options. This symbol represents the
branching or merging of various flows with the symbol acting as a frame or
container.
• Connector symbol
• End symbol
Marks the end state of an activity and represents the completion of all flows
of a process.
Activity Diagram:
3.CONTEXT DIAGRAM
The context diagram is used to establish the context and boundaries of the system to
be modelled: which things are inside and outside of the system being modelled, and
what is the relationship of the system with these external entities.
The process of establishing the analysis framework by drawing and reviewing the
context diagram inevitably involves some initial discussions with users regarding
problems with the existing system and the specific requirements for the new
system. These are formally documented along with any specific system
requirements identified in previous studies.
Having agreed on the framework, the detailed investigation of the current system
must be planned. This involves identifying how each of the areas included within
the scope will be investigated. This could be by interviewing users, providing
questionnaires to users or clients, studying existing system documentation and
procedures, observation and so on. Key users are identified and their specific roles
in the investigation are agreed upon.
In order to produce the context diagram and agree on system scope, the following
must be identified:
• external entities
• data-flows
Context Diagram(dfd): LEVEL 1
Context Diagram(dfd):
LEVEL 2
4.SEQUENCE DIAGRAM
A sequence diagram is a type of interaction diagram because it describes
how—and in what order—a group of objects works together. These diagrams are
used by software developers and business professionals to understand requirements
for a new system or to document an existing process. Sequence diagrams are
sometimes known as event diagrams or event scenarios.
Sequence diagrams can be useful references for businesses and other organizations.
Try drawing a sequence diagram to:
To understand what a sequence diagram is, you should be familiar with its
symbols and components. Sequence diagrams are made up of the following icons
and elements:
Actor Shows entities that interact with or are external to the symbol
system.
SEQUENCE DIAGRAM:
5.USE CASE DIAGRAM
To model a system, the most important aspect is to capture the dynamic
behaviour. Dynamic behaviour means the behaviour of the system when it is
running/operating.
Only static behaviour is not sufficient to model a system rather dynamic
behaviour is more important than static behaviour. In UML, there are five diagrams
available to model the dynamic nature and use case diagram is one of them. Now
as we have to discuss that the use case diagram is dynamic in nature, there should
be some internal or external factors for making the interaction.
These internal and external agents are known as actors. Use case diagrams
consists of actors, use cases and their relationships. The diagram is used to model
the system/subsystem of an application. A single use case diagram captures a
particular functionality of a system.
Hence to model the entire system, a number of use case diagrams are used.
Purpose of Use Case Diagrams
The purpose of use case diagram is to capture the dynamic aspect of a system.
However, this definition is too generic to describe the purpose, as other four
diagrams (activity, sequence, collaboration, and State chart) also have the same
purpose. We will look into some specific purpose, which will distinguish it from
other four diagrams.
Use case diagrams are used to gather the requirements of a system including internal
and external influences. These requirements are mostly design requirements.
Hence, when a system is analysed to gather its functionalities, use cases are
prepared and actors are identified.
When the initial task is complete, use case diagrams are modelled to present the
outside view.
the purposes of use case diagrams can be said to be as follows −
Used to gather the requirements of a system.
• Used to get an outside view of a system.
• Identify the external and internal factors influencing the system.
• Show the interaction among the requirements are actors.
USECASE DIAGRAM:
SYSTEM
DESIGN
When user logins first on the website he meets with the Login Page :
Before Booking any hotel room a user must have to register
Registration Page:
Once the registration is done admin is able to take control of everything that is
happening on the application
Home Page:
Here, The Admin have to fill the customers detail and have the privilege to add
any new user and delete, reset or update any existing user through this
dashboard and the admin can search the registered user by their contact
number or email adress
Customer Details:
This is Room Booking Page where the admin can check the availability of the
room and can fetch the previous data using their contact number. Even the
admin can search the required users
Room Booking Details:
From this page the admin can add the room details according to the customers
preference
Room Details Page:
DATABASE CONNECTION
There are three section in collection which stores customers, registration and
rooms information
The customer section stores all the information about the customers stored in
Customer Page while booking
This collection is used to see the all the registered users in the database and all
the information related to them
VALIDATIONS