Hotel Management System

SDMS
Use - Cases
Table of Contents
1. Use cases 5

2. Use Case Diagram 9

-2-
1. Use cases

Use Case UC1: Owner Profile

Scope: Ownership of the whole system
Level: Owner goal
Primary actor: Owner
Stakeholders and Interests :

Preconditions:
1 Must have ownership
Post-conditions:
1 Must be able to change and improve system anytime.
Main flow :
1 Full access to the system.
2 Owner can view all the details in a graphical way.
3 The authority to change the Cost of Room, Room Availability, Service Details
4 Check the details of the receptionist
5 Check the details of the staff member currently working at that Hotel.

Use Case UC2: Manager Profile.

Scope: Management of the hotel.
Level: User goal
Primary actor: Manager
Stakeholders and Interests :

Preconditions:
1 User is known and his identity has been authenticated.
Post-conditions:
1 Invite respond has been sent to the initiator and saved by the system.
Main flow :
1 Partial access to the System
2 View the availability and can change the cost of the room and other service details
3 Special interface to manage the staff of the hotel
4 Addition of new people.
5 Removal of people as needed.
6 Owner receives the notification through email of all operations

-3-
 Use Case UC3: Customer Management
Scope: Management of customers
Level: User goal
Primary actor: Customer
Stakeholders and Interests :

Preconditions:
Post-conditions:
Main flow :
1. Check the availability of rooms.
2. Book a room.
3. Contains name, Contact details, address, and other necessary details of the customer.
4. Need to sign-up for booking the hotel

Use Case UC4: Booking

Scope: Booking of the hotel.
Level: User goal
Primary actor: Customer
Stakeholders and Interests :

Preconditions:

Post-conditions:

Main flow :
1. Easily search their Room from the various option available
2. Check-in
3. Check-out
4. Limitation for people for a single room
5. After everything ask for money.
6. Forward to payment gateway.

Use Case UC4: User Authentication

Scope: User authentication according to his/her role
Level: User goal
Primary actor: Customer
Stakeholders and Interests :

Preconditions:
1. User is known and his identity has been authenticated.
Post-conditions:

Main flow :
1. Portal will take care of every profile in the system.
2. No user will be allowed to use our system without a valid ID

-4-
 3. Every profile must authenticate using system procedure.
4. This would ensure the security of our system

2. Use Case Diagram

-5-