p.report
p.report
SUBMITED TO
DEPARTMENT OF INFORMATION
TECHNOLOGY
(INFORMATION TECHNOLOGY)
2024-2025
SUBMITED BY:
Certificate
This is to certify that of
T .Y. B.Sc. (IT). Seat no has successfully completed the
project work in the subject of as prescribed by University of
Mumbai during the year 2024 – 2025.
Internal Examiner
External Examiner
HOD Stamp
SUMMARY
PRELIMINARY INVESTIGATION
1 Organizational overview 6
SYSTEM ANALYSIS
8 Activity Diagram. 15
9 Database Diagram 20
SYSTEM IMPLEMENTATION
9 Test Cases 21
10 Screenshots 25
● Login: it will involve user login options and get access into the system.
● Home: it’s dashboard having components like bookings, property and
meetings.
● Client: It shows the client details.
● Bookings: the record of all the bookings and one can modify the bookings.
Advantages of the Proposed System for Hotel Select
Actors
An actor portrays any entity (or entities) that perform certain roles in a given system. The
different roles the actor represents are the actual business roles of users in a given system. An
actor in a use case diagram interacts with a use case. For example, for modeling a banking
application, a customer entity represents an actor in the application. Similarly, the person
who provides service at the counter is also an actor. But it is up to you to consider what
actors make an impact on the functionality that you want to model. If an entity does not affect
a certain piece of functionality that you are modeling, it makes no sense to represent it as an
actor. An actor is shown as a stick figure in a use case diagram depicted "outside" the system
boundary.
Use Cases
A use case in a use case diagram is a visual representation of distinct business functionality
in a system. The key term here is "distinct business functionality." To choose a business
process as a likely candidate for modeling as a use case, you need to ensure that the business
process is discrete in nature. As the first step in identifying use cases, you should list the
discrete business functions in your problem statement. Each of these business functions can
be classified as a potential use case. Remember that identifying use cases is a discovery
rather than a creation. As business functionality becomes clearer, the underlying use cases
become more easily evident. A use case is shown as an ellipse in a use case diagram.
System Boundary
A system boundary defines the scope of what a system will be. A system cannot have infinite
functionality. So, it follows that use cases also need to have definitive limits defined. A
system boundary of a use case diagram defines the limits of the system. The system
boundary is shown as a rectangle spanning all the use cases in the system.
Relationships: The following relationships can be established among use cases
• Extends: A use case may extend another. This relationship indicates that the behavior
of the extension use case may be inserted in the extended use case under some conditions.
The notation is a dashed arrow from the extension to the extended use case, with the label
“«extend»".
• Includes: A use case may include another. Include is a Directed Relationship between
two use cases, implying that the behavior of the included use case is inserted into the
behavior of the including use case. The first use case often depends on the outcome of the
included use case. This is useful for extracting truly common behavior from multiple use
cases into a single description. The notation is a dashed arrow from the including to the
included use case, with the label "«include»".
ER diagram
Sequence Diagram
Activity diagram
Deployement Diagram
Test
Cas Modul Test Expected Actual Stat
e ID e Form Conditions Steps Input Test data output Output u s
TC1 Registe User To register 1) 1)Username , Email and Sign up into Sign Pass
r Registe user with Clicks password with proper system into
r the help of on sign manner system
Username, up
email and button
password