DA NANG UNIVERSITY

VIETNAM – KOREA UNIVERSITY OF INFORMATION AND

COMMUNICATION TECHNOLOGY
~~~~~~*~~~~~~

BIG PROJECT
SYSTEM ANALYSIS AND DESIGN

TOPIC:
HOTEL MANAGER

Students perform : Nguyễn Thị Thanh Hiền - 21IT072

Nguyễn Thị Kim Phụng - 21IT101
Lê Thị Ngọc Ly - 21IT090
Lê Thị Kim Tuyền - 21IT660
Instructor : ThS. Lê Viết Trương

Da Nang, December 2022

 Systems analysis and design i

TABLE OF CONTENTS

CHAPTER 1 - STATUS SURVEY AND PROJECT ESTABLISHMENT.............1

1.1 Survey the current situation and assess the status.............................................1
1.1.1 About the unit............................................................................................1
1.1.2 Business Process........................................................................................1
1.1.3 Assess the status........................................................................................6
1.2 Project setting...................................................................................................6
1.3 System requirements........................................................................................7
CHAPTER 2 - MODELING REQUIREMENTS......................................................9
2.1 Identify the actors..............................................................................................9
2.2 Use case.............................................................................................................9
2.2.1 List Use Cases.............................................................................................9
2.2.2 Specification of Use Cases............................................................................9
2.3 Use case diagram.............................................................................................11
CHAPTER 3 - STRUCTURAL MODELING.........................................................14
3.1 Define classes..................................................................................................14
3.2 Defining relationships between classes............................................................17
3.3 Analysis class diagram.....................................................................................18
CHAPTER 4 – DYNAMIC BEHAVIOR MODELING.........................................19
4.1 Activity chart...................................................................................................19
4.1.1 System Boot Sequence Diagram.................................................................19
4.1.2 Sequence Diagram Sign In..........................................................................19
4.1.3 Sequence diagram Close system.................................................................20
4.1.4 Check-in sequence diagram........................................................................20
4.1.5 Check out the sequence diagram.................................................................20
4.2 State chart........................................................................................................21
4.2.1 Room status chart.......................................................................................21
4.2.2 Room equipment status chart......................................................................21
4.2.3 Employee Status Graph...............................................................................22
4.2.4 Customer Status Chart................................................................................22
4.2.5 Service State Chart......................................................................................22

Computer Science
 Systems analysis and design ii

4.3 Activity Diagram.............................................................................................23

4.3.1 Activity Diagram Login..............................................................................23
4.3.2 Activity Diagram Check-in.........................................................................23
4.3.3 Activity Diagram Check out.......................................................................24
CHAPTER 5 - DETAILS THE DESIGN CLASS CHART....................................25
CHAPTER 6 - ARCHITECTURAL MODELING.................................................26
6.1 Package diagram..............................................................................................26
6.2 Component Diagram........................................................................................26
6.3 Development Diagram.....................................................................................27
CONCLUSION AND DEVELOPMENT.................................................................28
REFERENCES..........................................................................................................29

Computer Science
 Systems analysis and design iii

LIST OF IMAGES, GRAPHICS

Figure 1.1.1.1 - Check-in process..................................................................................1
Figure 1.1.1.2 - Check-out process................................................................................2
Figure 1.1.1.3 - Business process Importing goods, classifying....................................3
Figure 1.1.1.4 - Export business process........................................................................4
Figure 1.1.1.5 - Business process Inventory liquidation - expiration.............................5
Figure 1.1.1.6 - Statistical and reporting business process.............................................6
Figure 2.3.1 - Hotel Management System Use Case Diagram ....................................11
Figure 2.3.2 - User Administration Use Case Diagram................................................12
Figure 2.3.3 - Employee Management Use Case Diagram..........................................12
Figure 2.3.4 - Use Case Diagram Search....................................................................13
Figure 2.3.5 - Drug Update Package Use Case Diagram.............................................13
Figure 3.3 - Analysis class diagram.............................................................................18
Figure 4.1.1 - System Boot Sequence Diagram...........................................................19
Figure 4.1.2 - Sequence Diagram Sign In....................................................................19
Figure 4.1.3 - Sequence diagram Close system............................................................20
Figure 4.1.4 - Check-in sequence diagram...................................................................20
Figure 4.1.5 - Check out the sequence diagram...........................................................20
Figure 4.2.1 - Room status chart..................................................................................21
Figure 4.2.2 - Room equipment status chart................................................................21
Figure 4.2.3 - Employee Status Graph.........................................................................22
Figure 4.2.4 - Customer Status Chart...........................................................................22
Figure 4.2.5 - Service State Chart................................................................................22
Figure 4.3.1 - Activity Diagram Login.......................................................................23
Figure 4.3.2 - Activity Diagram Check-in...................................................................23
Figure 4.3.3 - Activity Diagram Check-out.................................................................24
Figure 5 - Class Diagram Detail Level........................................................................25
Figure 6.1 - Package diagram......................................................................................26
Figure 6.2 - Component Diagram................................................................................26
Figure 6.3 - Development Diagram.............................................................................27

Computer Science
 Systems analysis and design iv

PREAMBLE
Along with the development of the economic situation in Vietnam in particular
and the world in general, when people have better living conditions and have more
time, rest, entertainment, and tourism become an important part. of the world. of
essential needs. Therefore, tourism has become a popular activity in social life and is
one of the fastest-growing world economies today.
Tourism not only brings economic benefits, and contributes significantly to the
national budget, but also acts as a bridge and opens up opportunities for exchange with
the outside world, bringing many cultural benefits. - Politics, economy, etc. Tourism
development will facilitate mutual understanding between peoples and cultures, and
build peace, friendship, and common progress of mankind in the world. gender.
Vietnam is a country with many favorable conditions for tourism to develop
rapidly, in which natural and human factors are diverse and unique, attracting domestic
and foreign tourists. Particularly Da Nang, with many natural advantages given by
nature such as a tropical monsoon climate, little volatility, diverse terrain, and many
beautiful beaches, .... This place is known as the city most livable in Vietnam. Da
Nang city is a major tourist center of Vietnam with many famous scenic spots, favored
by nature in terms of geographical location, landscape, climate, history, and humanity.
Along with the rapid development of tourism, the accommodation service
business is also developing constantly, the hotel is the most popular type to serve the
diverse needs of visitors. This is a profitable business. Annually, the revenue from the
hotel business accounts for a large proportion of the total revenue of the tourism
industry.
With the increasingly crowded hotel "market", many new hotels and resorts
have sprung up in Da Nang, leading to difficulties in competition among hotels in the
city. Managing a hotel is not easy with the increasing number of domestic and foreign
tourists. That's why I created hotel management software to remove difficulties in
hotel management.

Computer Science
 Systems analysis and design 1

CHAPTER 1 - STATUS SURVEY AND PROJECT

ESTABLISHMENT
1.1 Survey the current situation and assess the status
1.1.1 Business Process
1.1.1.1 Check-in process

Figure 1.1.1.1 - Check-in process

After receiving the customer, the receptionist will communicate with the
customer to collect information about the customer such as personal information,
booking information, accommodation needs, number of people... from there.
suggestions and check-in procedures for visitors.

Computer Science
 Systems analysis and design 2

1.1.1.2 Check-out process

Figure 1.1.1.2 - Check-out process

After receiving the check-out request, the receptionist will ask the housekeeping
department to check the room status, and service statistics, then make an invoice and
receive payment from the customer.

Computer Science
 Systems analysis and design 3

1.1.1.3 Business process Importing goods, classifying

Figure 1.1.1.3 - Business process Importing goods, classifying

After purchasing goods from the supplier, the accountant will check, classify and
arrange them in the warehouse.

Computer Science
 Systems analysis and design 4

1.1.1.4 Export business process

Figure 1.1.1.4 – Export business process

The accountant receives the list of goods to be exported from the housekeeping
department, checks and hands them over to the housekeeping department, obtains
confirmation, and stores release information.

Computer Science
 Systems analysis and design 5

1.1.1.5 Business process Inventory liquidation – expiration

Figure 1.1.1.5 - Business process Inventory liquidation - expiration

Periodically, the accountant will check the status of goods in the warehouse to
make a list of expired and unsold goods to prepare for liquidation.

Computer Science
 Systems analysis and design 6

1.1.1.6 Statistical and reporting business processes

Figure 1.1.1.6 - Statistical and reporting business process

Periodically or from time to time, the Manager will ask staff to make statistics
and report on the operation of the hotel. Staff responsible for making statistics.

1.1.2 Assess the status

Through the group survey, we found:
Some small hotels have just been established and come into operation in a short
time. The number of employees is not much, but there are many difficulties because
the tenants are quite crowded, and the work done is easy to cause chaos.
Therefore, our team decided to choose to analyze the topic and design a hotel
management software to serve the management at the hotel, providing security
services and high efficiency.
1.2 Project setting
 To manage the hotel easily, efficiently, and quickly.
 Management software for hotels is the integration of many different
functions to serve different aspects of the administrator's work such as
staff management, hotel booking, accounting, and collection - spending in
the hotel, ... helps the administrator to have the most overview of the
business situation of the hotel.

Computer Science
Systems analysis and design 7

 Currently, hotel management software is designed with a user-friendly

interface, you can operate it quickly on your phone, tablet, or laptop... No
need to be too knowledgeable about the job. information technology, you
can completely use the software easily in only 30 minutes.
 Manage business operations remotely
 All information about the hotel, staff members, or tourists is stored
entirely on the software system. You don't need to rummage through
paperwork to find customer information or have to go room by room to
see if the housekeeping department is working properly. All the
information you need is stored by the hotel management software, you can
import and export data anytime, anywhere.
 Hotel management software makes your calculations accurate to each
number, allowing you to capture the clearest and most comprehensive
view of the hotel's business performance as well as the progress of work.
of employee.
 The system will save you time and effort. Not only large and high-class
hotels but today, even small and medium hotels can use mini hotel
management software to manage hotel operations, saving money quickly
and accurately. corpse.

1.3 System requirements

 Require Functional:
 Search
 Reliability
 Security
 Environmentnt
 Capacity
 Ability to extension
 Resilience
 Maintainability
 Management ability
 Business Principle
 Non-functional requirement:
 Availability
 Usability
 Interactive ability

Computer Science
Systems analysis and design 8

 Business Principle
 Legal and regulator requirements
 Permissions secsion
 Data history

Computer Science
Systems analysis and design 9

CHAPTER 2 - MODELING REQUIREMENTS

2.1 Identify the actors
 System Administrator: Is the highest administrator of the system.
 Manager: The person who manages and regulates the operation of the
hotel
 Receptionist: The person in charge of the front desk receives customer
requests.
 Housekeeping staff: The person who does the checking and living of the
room.
 Customers (including Travelers and Suppliers): are business partners with
the hotel.

2.2 Use case

2.2.1 List Use Cases.
 Open system/ Close system.
 Login/ Logout
 User administration.
 Employee management.
 Transactions (including booking, check-in, and checkout).
 Payment.
 Issue invoice.
 Register to stay.
 Manage documents.
 Room manager.
 Room service.
2.2.2 Specification of Use Cases
 Use case: System startup
 Actor: System Administrator
 Description: The system administrator is responsible for starting
the system before using its functions of the system.
 Use case: Close system
 Actor: System Administrator
 Description: The system administrator is responsible for closing the
system at the end of the session.

Computer Science
Systems analysis and design 10

 Reference to All system functions.

 Use case: Login
 Agents: Admin, N*Receptionist, N*Housekeeping, N*Accounting.
 Description: Agents need to log into the system before using
system functions.
 Use case: User administration (NSD).
 Actor: Admin
 Description: When there is a request to add users, delete users or
edit user information, the Admin is responsible for performing
these functions.
 Use case: Employee management.
 Actor: Manager.
 Description: Help management grasp the personnel situation, give
detailed statistics, Manage employee list, work shift, leave, daily
report
 Use case: Transaction.
 Actors: Receptionist, visitors.
 Description: display the interface to support the search of rooms
according to customer requirements when checking in, retrieving
and saving customer information, and booking information.
Automatically calculate payment invoices...
o Check In
o Check out
o Reservations
o Payments
 Use case: Manage documents.
 Actors: Accountant, Room Attendant, Tourist, Supplier
 Describe :
o Import goods
o Export goods
o Issue Invoice
 Use case: Room management.
 Actor: Management.
 Description: Statistics of guests, customer details, and the status of
all current rooms of the hotel.

Computer Science
Systems analysis and design 11

 Use case: Room service.

 Actors: Room staff, Receptionist, visitors.
 Description: Room staff collect information on room status
(consumables, room scheduling, room equipment status) and input
it into the system through which the receptionist captures the room
situation, the reception receives Service requests from customers
and inputs into the system, through which room staff recognize
requests and promptly implement them.
 Use case: Report.
 Agent: N*Receptionist,N*Housekeeping, N*Accountant, Manager.
 Description: employees based on the current situation carry out the
reporting requirements of management including periodic and non-
periodic reports…

2.3 Use case diagram

Figure 2.3.1 - Hotel Management System Use Case Diagram.

Computer Science
Systems analysis and design 12

Figure 2.3.2 - User Administration Use Case Diagram.

Figure 2.3.3 - Employee Management Use Case Diagram.

Computer Science
Systems analysis and design 13

Figure 2.3.4 - Use Case Diagram Search.

Figure 2.3.5 - Drug Update Package Use Case Diagram

Computer Science
 Systems analysis and design 14

CHAPTER 3 - STRUCTURAL MODELING

3.1 Define classes
After the actual survey and documents, it is possible to identify the classes of the
Hotel Reservation Management system as follows:
 Customer: description of customer information
 Id_Cus
 Name: Full name
 Iden_num: Identity card number
 Sex: Male/Female
 Phone_Num: Phone number
 Type Cus: Customer classification
 Id_Typ_Cus: Id type
 Name_Typ_Cus: Name of type
 Des_Typ_Cus: Description
 Staff: description of employee information
 Id_Sta
 Name: Full name
 Phon_num: Phone number
 Depart_Sta: Types of staff parts
 Id_Fun_Sta: Id department
 Name_Fun_Sta: Name of department
 Des_Fun_Sta: Description

 Account: is used to log in to the system

 Username: Username to log in system
 Password: Password to log in system
 Role: Customers or staff will have the ability to access different
parts of the system, such as customers who cannot manage
customers,
 Room:
 Id_Room: Id of room
 Status: The availability or booking status of the room
 The price of the room will depend on the time price, so it will be
separated into Pri_Room table
 Typ_Room:
 Id_Typ_Room: Id type

Computer Science
Systems analysis and design 15

 Name_Typ_Room: Name of type

 Des_Typ_Room: Description
 Pri_Room
 Id_Pri_Room: Id
 Day_Beg: Day begin
 Day_En: Day end
 Pri: Price
 Equip_Room: Room equipment information
 Id_Eq_Room: Id
 Quan_Eq_Room: The quantity of the product that is used in the
room
 Status: Status of equipment in the room Condition of equipment in
the room
 Equip: Equipment information
 Id_Eq: Id of equipment
 Quan_Eq: The quantity of the equipment
 Status: Status
 Type_Equipe:
 Id_Typ_Eq: Id
 Name_Typ_Eq: Name of type

 Food_Room: Food/Drink in Room

 Id_ Food_ Room: Id
 Quan: The quantity
 Status: Status of food in the room
 Equip: Food
 Id_Food: Id
 Quan_eq: The quantity of equipment
 Status: Status
 Goods: Good include equipment, food, drink,..
 Id_Goods: Id
 Quan: The quantity of
 Status: Status
 Supplier: Supplier information
 Id_ Supplier: Id of Supplier
 Name: Name of Supplier
 Address: Address of supplier
 Contact_Num: Contact number
 Service: In addition to customers wishing to book, there are also
additional service needs such as spa, breakfast, and buffet, …

Computer Science
Systems analysis and design 16

 Id_Ser: Id service
 Name_Ser: Name service
 Pri_Ser: Price of service
 Type_Ser:
 Id_Typ_Ser: Id
 Name_Typ_Ser: Name
 Booking: Customer booking information
 Id_Book: Id of booking
 Day_Book: Date the customer registers
 Day_In: Date of entry
 Day_Out: Date of check-out (estimated)
 Quan_Peo: Number of people in the room
 Deposit: The amount deposited
 Note

 Bill: Information about the bill

 Id_Bill: Id
 Day_Bill: Bill Date
 Price_Bill: Total price

 Bill_Detail_Room: Details of room information in the bill

 Id_Bill: Id of bill detail room
 Quan_Room: Numbers of rooms
 ToPri_Ro: Room price

 Bill_Detail_Ser: Details of service information in the bill

 Id_Bi_DeSer: Id of bill detail service
 Quan_Ser: Numbers of service
 ToPri_Ser: Price service

3.2 Defining relationships between classes

 Customer - Type_Cus: * - 1
 Staff - Fun_Sta: * - 1
 Customer/Staff - Account: 1 - 1
 Account - Act: * - 1
 Room - Type_Room: * - 1
 Room - Pri_Room: 1 - *
 Room - Equip_Room: 1 - * (because 1 room has many equipments)
 Equip_Room - Equip : * - 1 (because 1 device line is used in many rooms)

Computer Science
Systems analysis and design 17

 Room - Food_Room: 1 - * (because 1 room has many food)

 Food_Room - Food : * - 1 (because 1 food line is used in many rooms)
 Equip/Food - Goods: *-1 (because goods include equipments, foods,
drinks)
 Service - Type_Service: * - 1
 Booking - Customer/Staff: * - 1
 Bill - Customer/Staff: * - 1
 Bill - Bill_Detail_Room/Bill_Detail_Ser: 1 - *
3.3 Analysis class diagram

Figure 3.3 - Analysis class diagram

Computer Science
Systems analysis and design 18

CHAPTER 4 – DYNAMIC BEHAVIOR MODELING

4.1 Activity chart
4.1.1 System Boot Sequence Diagram.

Figure 4.1.1 - System Boot Sequence Diagram.

4.1.2 Sequence Diagram Sign In

Figure 4.1.2 - Sequence Diagram Sign In.

Computer Science
Systems analysis and design 19

4.1.3 Sequence diagram Close system.

Figure 4.1.3 - Sequence diagram Close system.

4.1.4 Check-in sequence diagram.

Figure 4.1.4 - Check-in sequence diagram.

4.1.5 Check out the sequence diagram.

Figure 4.1.5 - Check out the sequence diagram.

Computer Science
Systems analysis and design 20

4.2 State chart

4.2.1 Room status chart

Figure 4.2.1 - Room status chart

4.2.2 Room equipment status chart

Figure 4.2.2 - Room equipment status chart

Computer Science
Systems analysis and design 21

4.2.3 Employee Status Graph

Figure 4.2.3 - Employee Status Graph

4.2.4 Customer Status Chart

Figure 4.2.4 - Customer Status Chart

4.2.5 Service State Chart

Figure 4.2.5 - Service State Chart

Computer Science
Systems analysis and design 22

4.3 Activity Diagram

4.3.1 Activity Diagram Login
Staff Login into the system:

Figure 4.3.1 - Activity Diagram Login

4.3.2 Activity Diagram Check-in
Receptionist check for the customer:

Figure 4.3.2 - Activity Diagram Check-in

Computer Science
Systems analysis and design 23

4.3.3 Activity Diagram Check out

Figure 4.3.3 - Activity Diagram Check-out

Computer Science
Systems analysis and design 24

CHAPTER 5 – CLASS DIAGRAM DETAIL LEVEL

Figure 5 – Class Diagram Detail Level

Computer Science
Systems analysis and design 25

CHAPTER 6 - ARCHITECTURAL MODELING

6.1 Package diagram

Figure 6.1 - Package diagram

6.2 Component Diagram

Figure 6.2 - Component Diagram

Computer Science
Systems analysis and design 26

6.3 Development Diagram

Figure 6.3 - Development Diagram

Computer Science
Systems analysis and design 27

CONCLUSION AND DEVELOPMENT

 CONCLUSION: The hotel management system is not a big topic, but it has the
common characteristics of information management systems in general, and it
has many advantages in practice. A high job, not only requires more meticulous
surveys and assessments but also requires a deeper level of mastery of hotel
operations. However, due to its limitations and conditions, Due to objective
circumstances, I cannot design a complete and comprehensive program.
 DEVELOPMENT: Can develop applications on a wide area network, then
will meet the needs of most customers in this day and age.

Computer Science
Systems analysis and design 28

REFERENCES

Computer Science