|
|
NATIONAL
UNIVERSITY OF MANAGEMENT
|
|
|
FACULTY
of INFORMATION TECHNOLOGY
SUBJECT:
SYSTEMS ANALYSIS and DESIGN
|
|
|
||
|
|
|
Phnom Penh Hotel Booking
Management System
Analysis Document
Version 1.0
|
|
Authors
|
VANNAK SOMLOT, SENG VIREAK, KOB TEA, PHY
BUTHRY, CHAK PUTHIRITH, SOK SARAN, THON MAKARA, SOEU CHANTHORN, PHAN PHANITH,
SEN SEREYLEAP, NARA SOPHAL, KONG THA.
|
|
Date created
|
23rd of July 2016
|
|
Date modified
|
[10th of October 2015, if no
modification you don’t need to put]
|
|
Reader
|
EAV DARAPISAL
|
Table of Contents
1. Introduction
1.1. Objective
[What is the purpose of this document? What are the contents of this document? See
my first simple template about requirements document for your sample]
1.2. Project Description in brief
2. Analyses Use Case
2.1. Use Case List
[List of all use cases in the table below. Try to think
which use case should be come first in the list. In part 2.2 you are going to
study Use Case one by one from the list in this table.
For example in web mail system: login use case must be the
first, because we must log in, after that we can work with other use case]
|
Priority
|
Use Case name
|
Possible included Use Case
(Optional)
|
Responsible Person
|
|
1
|
Login
|
User Name, Password
|
Receptionist, Manager
|
|
2
|
Manage Staff
|
|
Manager(owner)
|
|
3
|
Manage Room
|
Status Room
|
Manager(Owner)
|
|
4
|
View Room
|
|
Receptionist
|
|
5
|
View Cost
|
Status Room
|
Receptionist
|
|
6
|
Fine
|
|
Stock keeper
|
|
7
|
Book Room
|
Check-in, Deposit
|
Customer,
|
|
8
|
Guest Delay staying
|
|
Customer
|
|
9
|
Check-out
|
|
Customer
|
|
10
|
Print Invoice
|
|
Receptionist
|
2.2. Use Case and Scenarios
2.2.1. Use case name
|
Scenarios
|
|
|
Use Case name:
|
Login
|
|
Description:
|
All user must be login (User name, Password)
|
|
Actor:
|
Receptionist,
Manager
|
|
Author:
|
|
|
Precondition:
|
Username and password
|
|
Post condition:
|
Application
launched
|
|
Successful completion:
|
-User open application
-System display login form
-User input user name and password
-User Click login button
-System query username and password
-Display main form
|
|
Alternative:
|
Invalid username and password
|
|
Scenarios
|
|
|
Use Case name:
|
Insert Room
|
|
Description:
|
Manager can Set new Room
|
|
Actor:
|
Manager
|
|
Author:
|
|
|
Precondition:
|
Bed, Room ID, Type of Room, Price
|
|
Post condition:
|
New Room Info
will be record to the system and then Show massage Successful
|
|
Successful completion:
|
- Manager Click on new Room
- System Displays room form
- Manager Fill up the form(Room ID, Bed, Type of Room,
Price)
- Manager Click on Save Button
-New Room Info will be recorded to database System
-System alerts the massage New Room is Successful Insert
|
|
Alternative:
|
-New Room Form Is not
completed
|
|
Scenarios
|
|
|
Use Case name:
|
Insert Staff
|
|
Description:
|
Manager have to insert all staff and when new staff
come in
|
|
Actor:
|
Receptionist,
Manager
|
|
Author:
|
Vannak Somlot
|
|
Precondition:
|
Non
|
|
Post condition:
|
Staff
profile will be inserted into database
system
|
|
Successful completion:
|
-Manager click on Staffs button
-System Show insert Staff form
-Manager fill Staff information into form
-Manager Click on Insert button or press Enter key
-Staff profile will be recorded into database system
-System alert the massage Staff profile recorded
Successful
|
|
Alternative:
|
Form has not completed
|
|
Scenarios
|
|
|
Use Case name:
|
Update Room
|
|
Description:
|
Manager updates room cost, Upgrades rooms (mattress,
Fridge, TV, Toothpaste…..)
|
|
Actor:
|
Manager
|
|
Author:
|
Seng Vireak
|
|
Precondition:
|
Room ID
|
|
Post condition:
|
System Displays
room information on the screen
|
|
Successful completion:
|
-
Manager clicks on find button
-
System shows an Input Box to find room
information
-
Manager inputs Room ID or Name and clicks Ok
or Press Enter key
-
System queries room information from the
Database
-
System displays room information on the screen
-
Manager does editing room information
-
Manager clicks on Room Update Button
-
Room information is updated to the Database
system
-
System shows a message” Record updated
successfully!”
-
Clear form
|
|
Alternative:
|
Record not updated!
|
|
Scenarios
|
|
|
Use Case name:
|
Booking
|
|
Description:
|
Customer can book room via hotel website
|
|
Actor:
|
Customer
|
|
Author:
|
Thon makara
|
|
Precondition:
|
Name, Phone number, Date ,Status room, Type of Room
|
|
Post condition:
|
Booking form will
be record to the system and then Show massage Successful
|
|
Successful completion:
|
-Customer open website
-Customer Click on Booking Button
-System display Booking form
-Customer fill up the form Booking(Name, Phone number,
ID card, Type of Room, Passport)
-Customer Click on button Confirm
-Booking form will be recorded to database System
-System alerts the massage Booking is Successful
|
|
Alternative:
|
The form is not completed
|
|
Scenarios
|
|
|
Use Case name:
|
View Cost
|
|
Description:
|
Manager, Receptionist can view Room Cost
|
|
Actor:
|
Receptionist,
Manager
|
|
Author:
|
Soeu chanthorn
|
|
Precondition:
|
Type of Room
|
|
Post condition:
|
Display Room Cost
From Database
|
|
Successful completion:
|
-Receptionist Click on Check Price Button
-System Displays Check Room form
-Receptionist Enter type of Room
-Receptionist click check price
-System Query price of room in Database
-System Display Room price Detail on screen
|
|
Alternative:
|
Cost of Room Was not Found
|
|
Scenarios
|
|
|
Use Case name:
|
Cancellation Booking
|
|
Description:
|
Guests and Receptionist can cancel booking.
|
|
Actor:
|
Guests,
Receptionist
|
|
Author:
|
Chak Puthirith
|
|
Precondition:
|
Reservation ID
|
|
Post condition:
|
Booking has been deleted from system.
|
|
Successful completion:
|
- Receptionist click button Cancellation
- System display cancellation form
- Receptionist Enter Booking ID
- Receptionist click search button
- System will query book information from database
- System display
Search booking information on screen
- Receptionist click button cancel
- System delete booking ID from system
- System display message cancel successful
|
|
Alternative:
|
-Reservation ID not found.
|
|
Scenarios
|
|
|
Use Case name:
|
Guest Delay
staying
|
|
Description:
|
The guest want to
continue staying in the hotel by asking the receptionist to calculate the
amount that needs to pay.
|
|
Actor:
|
Receptionist
|
|
Author:
|
Kob Tea
|
|
Precondition:
|
-
Room
number
-
Time
|
|
Post condition:
|
-
Guest
must to inform to receipt
-
Room
still Unavailable
|
|
Successful completion:
|
-
RECEPTIONIST
insert room number into the SYSTEM
-
SYSTEM
finds room info
-
SYSTEM
display room info on the screen
-
RECEPTIONIST
click on RoomDelay Button
-
Set
number of time
-
SYSTEM
calculates the price
-
SYSTEM
displays the amount on the screen
-
RECEPTIONIST
prints the invoice and gives to the guest
-
RECEPTIONIST
set the room continue to unavailable
-
SYSTEM
set room to unavailable
|
|
Alternative:
|
-
Form is
not completed
|
[Draw UML sequence
diagram]
[Draw a simple User
Interface for this Use Case or relationship of the interfaces that user needs
to go through to complete this Use Case] (Optional)
Ex:
|
Scenarios
|
|
|
Use Case name:
|
Check out
|
|
Description:
|
The guest
prepares to leave the hotel by asking the receptionist to calculate the
amount that needs to pay.
|
|
Actor:
|
Receptionist
|
|
Author:
|
Eav Darapisal
|
|
Precondition:
|
-
Room
number
|
|
Post condition:
|
-
Guest
gets the receipt
-
Room is
set to free
|
|
Successful
completion:
|
-
RECEPTIONIST
insert room number into the SYSTEM
-
SYSTEM
finds room info
-
SYSTEM
display room info on the screen
-
RECEPTIONIST
click on check out button
-
SYTEM
calculates the number of days stayed
-
SYSTEM
calculates the price
-
SYSTEM
displays the amount on the screen
-
RECEPTIONIST
prints the invoice and gives to the guest
-
RECEPTIONIST
set the room to free
-
SYSTEM
set room to free
|
|
Alternative:
|
-
Form is
not completed
|
|
UML sequence
diagram for "Check Out"
|
|
UML
collaboration diagram for "Check out" interface
|
[After finish one
Use Case, you need to study other Use Case and number it as 2.2.2 , 2.2.3,
…etc]
3. Planning
[Draw you planning here if there is any
change on your last planning]
4. Reference
[If you have reference please list all your
references here]
|
No
|
References
|
|
1
|
|
|
2
|
|
5. Glossary
[List all your abbreviations]
W3C World Wide Web Consortium
