Hotel Reservation System Requirements

The provided content describes the functional and non-functional requirements of a hotel reservation system. The system should allow customers to view rooms available, packages, make reservations, cancel reservations, and view customer information. Admins can view or edit room and package information, approve or cancel reservations, and view or add staff and customer information. Non-functional requirements include consistency, flexibility, understandability, and ease of use.

HOTEL RESERVATION SYSTEM
STUDENT NAME:
11 November, 2016

Contents
FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS.........................................................2
USECASE DIAGRAM.........................................................................................................................2
USECASE DESCRIPTION...................................................................................................................3
USECASE-REQUIREMENT TABLE..................................................................................................5

FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS
1. Functional requirements
F1: Customer should be able to view rooms available
F2: Customer should be to view packages
F3: Customer should be able to make reservations
F4: Customer should be able to cancel reservations
F5: Admin should be able to view or edit rooms available and data
F6: Admin should be to view, add or edit packages info
F7: Admin should be able to view or approve reservations
F8: Admin should be able to view or cancel reservations
F9: Admin should be able to add, edit and view customer and staff info
2. Non-functional requirements
NF1: Consistency
NF2: Flexibility
NF3: Understandability
NF4: Easy to use
USECASE DIAGRAM

USECASE DESCRIPTION
USECASE ID: 1
NAME: ROOMS
DESCRIPTION: VIEW ROOMS AVAIBALE INFO
BASIC FLOW:
1. THE ADMIN CAN VIEW, EDIT OR ADD THE ROOM INFO BY ITS UNIQUE ID
2. THE CUSTOMER CAN VIEW ROOM INFO AND CHARGES ETC.
ALTERNATIVE FLOW: NONE
USECASE ID: 2
NAME: PACKAGES
DESCRIPTION: VIEW, ADD OR EDIT PACKAGE
BASIC FLOW:
1. THE ADMIN CAN VIEW, EDIT OR ADD THE PACKAGE INFO BY ITS UNIQUE ID
2. THE CUSTOMER CAN VIEW PACKAGE INFO AND CHARGES ETC.

ALTERNATIVE FLOW: NONE
USECASE ID: 3
NAME: RESERVATION
DESCRIPTION: MAKE RESERVATION, VIEW RESERVATION, APPROVE RESERVATION
BASIC FLOW:
1. THE ADMIN CAN VIEW OR APPROVE RESERVATIONS
2. THE CUSTOMER CAN MAKE OR VIEW RESERVATIONS
ALTERNATIVE FLOW: NONE
USECASE ID: 4
NAME: CANCEL RESERVATIONS
DESCRIPTION: PROCESS TO CANCEL RESERVATIONS OR VIEW RESERVATIONS
BASIC FLOW:
1. THE ADMIN CAN VIEW CANCELLED RESERVATIONS
2. THE CUSTOMER CAN CANCEL RESERVATIONS.
ALTERNATIVE FLOW: NONE
USECASE ID: 5
NAME: STAFF INFO
DESCRIPTION: VIEW INFORMATION ABOUT STAFF
BASIC FLOW:
1. THE ADMIN CAN VIEW OR EDIT THE INFORMATION ABOUT STAFF USING UNIQUE ID
2. THE ADMIN CAN ADD INFO ABOUT THE STAFF
ALTERNATIVE FLOW: NONE
USECASE ID: 6
NAME: CUSTOMER INFO
DESCRIPTION: VIEW INFORMATION ABOUT CUSTOMER
BASIC FLOW:
1. THE ADMIN CAN VIEW OR EDIT THE INFORMATION ABOUT CUSTOMER USING UNIQUE ID

2. THE ADMIN CAN ADD INFO ABOUT THE CUSTOMER
ALTERNATIVE FLOW: NONE
USECASE-REQUIREMENT TABLE
USECASE ROOMS PACKAGES RESERVATIO
N
CANCEL
RESERVATIO
N
CUSTOME
R
DETAILS
STAFF
DETAILS
REQUIRE-
MENT
F1 X
F2 X
F3 X
F4 X
F5 X
F6 X
F7 X
F8 X
F9 X X
NF1 X X X X X X
NF2 X X X X X X
NF3 X X X X X X
NF4 X X X X X X