IS-VNU

Project Document
[Hotel Supply Chain]

<Group 8>
<Nguyễn Tất Bảo Ngọc-Leader-17071391>
<Phạm Hà Nam- 18071532 >
Group Members <Bùi Mạnh Tùng-18071540 >
<Trịnh Thanh Hằng-18071521>

Supervisor Bùi Văn Phát

Ext Supervisor
Capstone Project
code

Hanoi, 26/05/2021
 Table of Contents

Acknowledgement.................................................................................................................................4
Definition and Acronyms........................................................................................................................4
I. Project Introduction............................................................................................................................5
1. Overview........................................................................................................................................5
2. Product Background.......................................................................................................................5
3. Existing Systems.............................................................................................................................5
4. Business Opportunity.....................................................................................................................5
5. Software Product Vision.................................................................................................................5
6. Project Scope & Limitations...........................................................................................................5
II. Project Management Plan..................................................................................................................6
1. Overview........................................................................................................................................6
2. Management Approach.................................................................................................................6
3. Master Schedule............................................................................................................................6
4. Project Organization......................................................................................................................6
5. Project Communication..................................................................................................................6
6. Configuration Management...........................................................................................................6
III. Software Requirement Specification.................................................................................................7
1. Overall Description.........................................................................................................................7
2. User Requirements........................................................................................................................7
3. Functional Requirements...............................................................................................................7
4. Non-Functional Requirements.......................................................................................................7
5. Other Requirements......................................................................................................................7
IV. Software Design Description.............................................................................................................8
1. Overall Description.........................................................................................................................8
2. System Architecture Design...........................................................................................................8
3. System Detailed Design..................................................................................................................8
4. Class Specification..........................................................................................................................8
5. Data & Database Design.................................................................................................................8
V. Software Testing Documentation......................................................................................................9
1. Overall Description.........................................................................................................................9
2. Test Plan.........................................................................................................................................9
3. Test Cases.......................................................................................................................................9
 4. Test Reports...................................................................................................................................9
VI. Release Package & User Guides......................................................................................................10
1. Deliverable Package.....................................................................................................................10
2. Installation Guides.......................................................................................................................10
3. User Manual.................................................................................................................................10
VII. Appendix........................................................................................................................................10
1. Glossary [Optional].......................................................................................................................10
2. References [Optional]..................................................................................................................10
3. Others [Optional].........................................................................................................................10

1. Status Report
# Work Item
 1  Functions
 2  Buttons, Form and Layout
 3  Databases
2. Team Involvements
# Task
 1  Front-end, back-end
 2  Front-end, back-end
 3  Front-end, back-end
4 Layout, Login/logout
3. Issues/Suggestions
# Issue
 1  Functions
 2  Buttons, Form and Layout
 3  Databases
Acknowledgement
Project Report
Status Notes (Work Item in Details)
 functions such as payment, refund
Pending confirm room availability or out of room
 create navigation buttons
buttons that link the product to the right
functions
create the background
In Progress standard form
Completed  Databases
Member Notes (Task Details, etc.)
 edit create buttons
Nguyễn Tất Bảo Ngọc creating the app rendering
 edit create buttons
Phạm Hà Nam creating the app rendering
 edit create buttons
Bùi Mạnh Tùng creating the app rendering
Trịnh Thanh Hằng Create and edit authorize, area
Status Notes (Solution, Suggestion, etc.)
Pending  complexity while handling functions
 not really suitable for the project and the
In Progress functions in each project
 need to add more or less appropriate
Completed things in the databases
 Definition and Acronyms
Acronym Definition

HSSM Hotel supply chain system

BK Booking

RB Room Booking

DT Details

USP User support policy

GUI Graphical User Interface

UC Use Case

API Application Program Interface

ERD Entity Relational Diagram

 I. Project Introduction
1. Overview
1.1 Project Information
Project Information
• Project name: << Hotel supply chain>>
• Project code: <<ASP.NET-C#>>
• Group name: <<INS2159-GROUP 8>>
• Software type: <<Web Applications>>

1.2 Project Team

a. Supervisor
Full Name Email PhoneNo Title

Bùi Văn Phát

b. Team Members
Full Name Email Mobile Role

Nguyễn Tất Bảo Ngọc baongoc25111999@gmail.com 0943476891 Leader

Members and
Phạm Hà Nam Phamhanam1702@gmail.com 0868475996 coding
function web
Members and
Bùi Mạnh Tùng ucmpunk2173@gmail.com 0977226618 coding
functions web
Members and
Trịnh Thanh Hằng Thanhhangtr.2109@gmail.com 0944178096 coding
functions web

2. Product Background
The hotel supply chain management project is a management system used on the web, with
management, providing information in search and gathering for easier service applications for
customers in the technology age number.

System evaluation: Through actual survey, it can be seen that the management in many hotels
is also done quite manually. Therefore, the purpose of this topic is to minimize manual works
to ensure the accuracy and reliability of work. However, due to the nature of work, in this
system, there is still a need for human performance, namely the receptionist. This section
details manual tasks and tasks performed by the computer. Most of the functions of the
system discussed below are performed by computer, only a few of the tasks mentioned must
be performed manually.
Project request: This hotel management system is integrated of many different functions to
serve different aspects of the manager's work. For example, staff management, hotel
reservations and hotel accounting are being replaced by different functions in a software
system. Many system companies have placed multiple hotel management areas in their
software. Hence, this software is known as property management software since many
other features enter in the basic hotel management work.
User system:
Customer: They are the ones who directly use the application on the system to access
bookings and view organizational information of hotels.
Hotel owner: They are hotel users with different functions from normal users, they are hotel
receptionists.
3. Existing Systems
 Professional management: This is where the product must ensure all the
requirements such as: booking, reception, accounting, bars, spa, sport, human
resources, …

 Manage reservations: Today, booking has become different when reservations come
from a variety of sources. So today's hotels require features that can handle private
bookings or from online travel agencies, travel agencies, corporate sources and from
other the website they collaborate with is as easy and accurate as possible.

 Hotel management and operation: is to organize and manage all hotel activities
scientifically and effectively. The hotel manager will set the rules for the management
of different parts of the hotel from reception, guest rooms to dining, events, financial
reporting, recordings - budget expenditure related to general hotel operations ...

 Invoice and payment: this is a must-have function in the software. This function
helps customers pay by using many different methods such as: cash, credit cash,…

 Synthesize and report: this function making it easy for hotel owners to grasp the
situation and make decisions. timely right or effective advertising and communication
strategies.
  Hotel equipment system interaction: Depending on the scale and system of the
hotel facilities, there will be a system of equipment, such as: ID scanner, Door lock,
cash drawer, vending system, other payment gateways or other payment gateways.
Equipped finance and accounting software. In order for the hotel work to be operated
according to a system or process, the hotel management software needs to be well
integrated and linked with other hardware or software.

4. Business Opportunity
Through actual survey, it can be seen that the management in many hotels is also done
quite manually. Therefore, the purpose of this topic is to minimize manual works to ensure
the accuracy and reliability of work. However, due to the nature of work, in this system,
there is still a need for human performance, namely the receptionist. This section details
manual tasks and tasks performed by the computer. Most of the functions of the system
discussed below are performed by computer, only a few of the tasks mentioned must be
performed manually.
In this product, hotels can scale and manage customer and order information better than in
the past. Hotels will directly compete in the software business market. By not only directly
comparing hotel values, but here all aspects of a hotel will be presented for example: price,
quality. services, location, ... This software works in all hotels that cater to a large number of
customers and want to technologize the complete management process.
Of course, in a development trend like the current 4.0 technology era, each product has its
own usefulness and practicality. suppose in the case that the product 'hotel supply chain
management' does not exist, the database system will return to the way it was before, ...
The hotel will directly manage vouchers such as booking, booking, receiving parties, ... with a
set of outdated and complicated technology dependent on stakeholders, ...
In addition, the introduction of a series of hotel chain products on the web as well as a form
of business promotion in the industry, will be known by more people.
In case you are a user, when you travel you will have a hard time finding a suitable
accommodation such as service, price, convenient location, ....
5. Software Product Vision
Together towards the development of better life services, the project's products provide
utilities for customers when looking for a suitable hotel, reasonable price, service, ...
everything is okay. directly on the website. The system supports users to choose the most
convenient resort, in addition, it also helps you to reduce the time in registering complicated
orders or cumbersome procedures as before, all transactions will be recorded and Pay directly
on the hotel's website system
6. Project Scope & Limitations
The hotel supply chain management project is a web-based management system, with the
management and provision of information to search and collect for easier service
application for customers in the modern era digital technology.
Hotel Management System is a system for storing, updating and modifying customer
information and services quickly in order to create maximum convenience for system users
and customers.
This software aims to support the hotel management quickly, accurately and easily. It will be
very helpful for the admin on
The project is developed on a small scale because it has just been started, so it may only
appear in a few hotels across the country.
Developers and stakeholders are determined not to have any other product advertising in
the product system. This is for the purpose of eliminating problems related to spam
information, unauthorized access permission, or link to unhealthy inappropriate dark web
sites (system consolidation policy).
For proposals outside the scope of activities of the project, the developer will also consider
and consolidate in the future. If it is really important or necessary for the project, of course,
it is necessary for each product to improve the quality of users through modification and
update than the old version.
Along with each change, each component is needed to make it up such as budget policy,
human resources, specific schedule, ...
The budgetary policy will include policy to the extent authorized by the management team
and the inquiry panel, the costs incurred by adding or subtracting parts of the system
structure.
Human resources to meet the job requirements, in addition, always think of change and
appropriate creativity when making this new product.
Schedule: one schedule form for specific time from launch date to product announcement
presentation to stakeholders and industry groups
6.1 Major Features
Feature 1: Room sales, aggregate by room type consolidated by housing, aggregate by room
number, consolidate revenue from reception

Feature 2: Sales of delegations: Checkout The union has a checkout room, Debts owed to
groups with Checkout rooms (Outstanding), Unchecked room, All Union liabilities - Details
All Union liabilities – Details, Details by room type, Details by block arrivals, Details by
room

Feature 3: Minibar and accompanying services

Aggregate according to the type of service, Aggregated by Room Type, Aggregate according
to the number of rooms, Aggregate by commodity group, Aggregate by Item, Details by type
of service, Details by Room Type, Details by Room Number, Details by commodity group,
Item Details

Feature 4: Guest list

-Check in room list of the day

-Customer list by Name

-List of customers by Nationality

-Customer list according to Check in Date

-List of customers by room

-List of customers by delegation

-Happy Birthday Customer List

-Customer List Free of charge

-List of early check-in customers

-List of early checkout customers

-List of GOLD customers during the period

-List of customers who will Go for the day

-The list of customers that will arrive within the day

Feature 5: Other reports

-Collect money in shift

-Debts owed to guests who are staying

-Management Information Change rooms

-Room status map

In addition to the most basic features and extensions of the product, we also have some ideas
for other features that are not accessible in the product.

High-end features

Employee management and decentralization of each function

High scalability

Integrated management of many hotels in the system

Manage room bill

The room charge includes tax, deposit fee

Support bill split function, bill pooling

Integrating online booking function

Support online deposit payment

Integrate and check VIP membership

Integrate hotel promotions.

 II. Project Management Plan
1. Overview
1.1 WBS & Estimation
Est. Effort
Complexit
# WBS Item (man-
y
days)
1 Feature 1 29
1.1 Design layout of the website Simple 7
1.2 Database of the website Simple 2
1.3 Coding the server side Complex 20
1.4 Document 1-6 Complex 20
1.5 report complex 5
Total Estimated Effort (man-days) 54

1.2 Project Objectives

[Provide the overall project objective description and then the specific target metrics of your project
in term of time, cost, and quality

1.3 Project Risks

[List out the details on project risks in the table below]

2. Management Approach
[Describe the approach you would use the manage and implement your project]

2.1 Project Process

[Draw and describe the software development process model that the team would apply into the
project implementation]

2.2 Quality Management

[Provide the approach you would apply to improve the project quality, reach the project quality
objectives

2.3 Training Plan

[You need to plan the training activities in case any of your team member lack of knowledge/skills to
handle the project works]

3. Master Schedule
[Given the main project deliverables. Those can be internal and/or external deliverables]

4. Project Organization
[Provide the project organization, the role and responsibilities of each project team member]
5. Project Communication
[Provide the details of project communication plan, the to-be-used tools, the project interface, etc.]

6. Configuration Management
6.1 Tools & Infrastructures
[List out the tools & infrastructure that you would use in the software development and deployment]

6.2 Document Management

[Describe how you would manage project documents & their changes/versions]

6.3 Source Code Management

[Describe how you would manage project source codes & their changes/versions]
 III. Software Requirement Specification

1. Overall Description
1.1 Product Overview
The hotel management is a system that coordinates the provision of services to customers.
The goal of the project is to help customers choose a hotel among many hotels in the
country. The system will be able to handle many services to take care of all customers in a
quick manner. The system should be user appropriate, easy to use, provide easy recovery of
errors and have an overall end user high subjective satisfaction.
The Hotel Management System is a system for storing, updating and modifying customer
information and services quickly for the hotel system in a hotel chain.
This hotel management application is aimed at two main users, customers and users.
Customers here are those who want to find information about services, rooms, hotels that
match the criteria they give, ... The remaining object that the project targets are hotel chain
systems. with the need for data management, access and query information in the
management and use of data to facilitate management arrangement as well as revenue
summary and detailed reports for system statistics, ...
Assumptions

A few assumptions were made when conceiving the project:

 have all the resources needed to finish the project

 Team members are enough and have all the required skills
 All of the equipment, technology, … is in good condition
 The goods bought online will be delivered on time
 All members will be on time for the meeting
 There will be no quarrel and every discussion will go smoothly

Dependencies

Firstly, for this project to work. The layout is needed to shape the image of the software.
This can be done by searching through the web or creating by yourself. The layout must
be presented in a way that is easy to understand for the user.

Secondly, the code needed to finish the project needs to be completed and then
aggregated. In the process to complete the code, it is possible to run tests to find bugs,
errors and perfect the software.
1.2 Business Rules
[Provide common business rules that you must follow. The information can be provided in the table
format as the sample below]

2. User Requirements
[Provide specification of the user requirement: actor, use cases, use case diagram, use case
specification, etc. These contents are optional, it can be ignored if the functional requirements are
clear enough]

3. Functional Requirements
[Provide specification of software system: screen, functions, system data, diagrams, functional
specification, etc.]
3.1 System Functional Overview
3.2 <<Feature Name 1>>
a. <<Function Name 1>>
[A function can be a screen or a non-screen function (listed in the part 5.1 above). In this part, you
need to provide the details on the related function, focus on mentioning below information
 Function trigger: how this function is triggered (navigation path, a timing frequency, etc.
 Function description: actors/roles, purpose, interface, data processing, etc.

Screen layout: mockup prototype of the screen

4. Non-Functional Requirements
4.1 External Interfaces
[This section provides information to ensure that the system will communicate properly with users
and with external hardware or software elements.]

4.2 Quality Attributes

[List all the required system characteristics (quality attributes) specification]

5. Other Requirements
[List out other requirements, appendix information etc. in this part]
 IV. Software Design Description
[Provide final software design information follow the template as part II in the Report #4]

1. Overall Description
1.1 Assumptions

[Describe any items, based on which to design future system]

1.2 Design Constraints

[Describe any global limitations or rules that have a significant impact on the design of the system's
software (and describe the associated impact]
1.3 [Technology Suggestion]
[This section is optional. If this section isn’t set, remove it out of the document]

2. System Architecture Design

2.1 Overall Architecture
[Select suitable architecture style and describe the architectural diagram in the
relationship/connection to the external systems. The content of this section include the overall
diagram and the explanation for each of the diagram components]

2.2 System Architecture

[Select suitable architecture patterns for sub-systems. The content of this section include the overall
diagram and the explanation for each of the diagram components]

2.3 Package Diagram

[Provide the package diagram for each sub-system. The content of this section include the overall
package diagram(s) and the explanation for each package]

3. System Detailed Design

3.1 <Feature Name1>
[Provide the detailed design for the feature <Feature Name1>. It include Class Diagram, Class
Specifications, and Sequence Diagram(s)]

a. Class Diagram
[This part presents the class diagram for the relevant feature]

b. Sequence Diagram(s)
[Provide the sequence diagram(s) for the feature]

4. Class Specification
[Provide the description for each class, including Class Methods information]
5. Data & Database Design
5.1 Database Design
[Provide the tables relationship and table specifications]
5.2 Data File Design
[List out the data files and file formats which are used in the system]

V. Software Testing Documentation

1. Overall Description
1.1 Test Model
Our developers use the waterfall model: a model of the software development process in
which the development process looks like a flow, with phases being executed in strict order
and no rollbacks or phase jumps are: requirements analysis, design, implementation, testing,
integration, and maintenance.

1.2 Testing Levels

1. Unit/component testing
The most basic type of testing is unit, or component, testing.
Unit testing aims to verify each part of the software by isolating it and then perform
tests to demonstrate that each individual component is correct in terms of fulfilling
requirements and the desired functionality.
This type of testing is performed at the earliest stages of the development process,
and in many cases it is executed by the developers themselves before handing the
software over to the testing team.
The advantage of detecting any errors in the software early in the day is that by doing
so the team minimise software development risks, as well as time and money
wasted in having to go back and undo fundamental problems in the program once it
is nearly completed.
2. Integration testing
Integration testing aims to test different parts of the system in combination in order
to assess if they work correctly together. By testing the units in groups, any faults in
the way they interact together can be identified.
There are many ways to test how different components of the system function at
their interface; testers can adopt either a bottom-up or a top-down integration
method.
In bottom-up integration testing, testing builds on the results of unit testing by testing
higher-level combination of units (called modules) in successively more complex
scenarios.
It is recommended that testers start with this approach first, before applying the top-
down approach which tests higher-level modules first and studies simpler ones later.
 
3. System testing
The next level of testing is system testing. As the name implies, all the components
of the software are tested as a whole in order to ensure that the overall product
meets the requirements specified.
System testing is a very important step as the software is almost ready to ship and it
can be tested in an environment which is very close to that which the user will
experience once it is deployed.
System testing enables testers to ensure that the product meets business
requirements, as well as determine that it runs smoothly within its operating
environment. This type of testing is typically performed by a specialized testing
team.
 
4. Acceptance testing
Finally, acceptance testing is the level in the software testing process where a product
is given the green light or not. The aim of this type of testing is to evaluate whether
the system complies with the end-user requirements and if it is ready for
deployment.
The testing team will utilize a variety of methods, such as pre-written scenarios and
test cases to test the software and use the results obtained from these tools to find
ways in which the system can be improved.
The scope of acceptance testing ranges from simply finding spelling mistakes and
cosmetic errors, to uncovering bugs that could cause a major error in the application.
By performing acceptance tests, the testing team can find out how the product will
perform when it is installed on the user’s system. There are also various legal and
contractual reasons why acceptance testing has to be carried out.
1.3 Testing Types

Manual testing is the most hands-on type of testing and is employed by every team
at some point. Of course, in today’s fast-paced software development lifecycle,
manual testing is tough to scale.

Automated testing uses test scripts and specialized tools to automate the process
of software testing.

Continuous testing goes even further, applying the principles of automated testing

in a scaled, continuous manner to achieve the most reliable test coverage for an
enterprise. Keep reading to learn more about the differences between automated
testing vs. manual testing and how continuous testing fits in.

2. Test Plan
2.1 Test Stages

Stage of Test
Type of Test Integratio Acceptanc
Unit System
n e
<Function Test > X X X X
<User Interface test> X X
<Performance Tests
(Performance profiles of individual X X
components)>
 <Load, Stress, Volume test> X X

<Security test> X X

<Data integrity test> X X

2.2 Resources
a. Human Resources

Revisions History

Revision No. Date of Issue Author Description

1 13.05.2021 Nguyễn Tất Bảo Ngọc Functional testing

2 20.05.021 Phạm Hà Nam Usability testing

b. Environment
It mentions the minimum hardware requirements that will be used to test the Application.
Following software’s are required in addition to client-specific software.
Windows 10
Microsoft SQL server and MSSQL 2019
Visual Studio 2019-ASP.NET FRAMEWORK.

2.3 Test Milestones

Task Name Start Finish Effort Comments

Test Planning 20/04/2021 18/05/2021 X

Review Requirements documents 23/04/2021 21/05/2021 X

Create initial test estimates 24/04/2021 22/05/2021

Staff and train new test resources 01/05/2021 22/05/2021 X

First deploy to QA test environment 02/05/2021 22/05/2021

Functional testing – Iteration 1 05/05/2021 23/05/2021 X

 Iteration 2 deploy to QA test 06/05/2021 23/05/2021
environment

Functional testing – Iteration 2 10/05/2021 21/05/2021 X

System testing 15/05/2021 22/05/2021

Regression testing 17/05/2021 22/05/2021 X

Resolution of final defects and final 20/05/2021 23/05/2021

build testing

Deploy to Staging environment 20/05/2021 23/05/2021

Performance testing 20/05/2021 23/05/2021 X

Release to Production 20/05/2021 23/05/2021 X

2.4 Deliverables

Deliverable For Date / Milestone

Test Plan Project Manager; QA Director;

Test Team
Traceability Matrix Project Manager; QA Director

Test Results Project Manager

Test Status report QA Manager, QA Director

Metrics All team members

3. Test Cases

TEST CASE FUNCTION

№ Steps Expected results Test
results
1. Tool tips
Pre-steps:
1. Open Main
1.1 Steps: WEB page with room appears. Pass
1. Click Card with button ‘Detail
+ Booking ’in hotel menu
2. Move mouse on Room .
1.2 Steps: WEB page with many functions Pass
1. Click Room Menu; appears.
2. Select List
 3. Move mouse on Market
button.
2. Work with keyboard
Pre-steps:
1. Open Main
2. Open Market
2.1 Steps: Next (Bottom) row is highlighted. Pass
1. Select Exchange;
2. Click any symbol;
3. Press Tab.
2.2 Steps: Table displays all symbols of Pass
1. Click Exchange Panel; selected exchange.
2. Move mouse on any exchange;
3. Press Enter.
2.3 Steps: Selected column is hidden. Pass
1. Select Exchange;
2. Right-click any column header;
3. Move mouse on Hide column;
4. Press Enter.
2.4 Steps: All columns are present. Pass
1. Select Exchange;
2. Right-click any column header;
3. Move mouse on Show all
columns;
4. Press Enter.
2.5 Steps: Column chooser was opened. Pass
1. Select Exchange;
2. Right-click any column header;
3. Move mouse on Choose
column;
4. Press Enter.

4. Test Reports
which contains a summary of all test activities and final test results of a testing project:
Meet the requirements that have guided its design and development,
Respond correctly to all input types,
Perform its functions in an acceptable time,
Be able to use,
Can be installed and run in its intended environments
Achieve the common outcome desired by the stakeholders.
 VI. Release Package & User Guides
1. Deliverable Package
1.1 Source codes & documents
The section will list all source programs, scripts, documents with version number in this release.

No. Items Sub-Items Type Version

Code Package
1 SM SM Client Modify 2.3
2 FT Delayed Report New 2.2.1
Database
1 Tables Hotel_Management.sql New 2.2.0

Hotel_Management _BookingStatus.sql Re-Use 2.1

Hotel_Management _RoomBooking.sql Re-Use 2.1.0

2 Stored New
Procedures
Modify
Documents
1 Requirement Design and integrate new functions Modify 2.0.2
2 Deployment Modify access and partition permissions and Modify 2.0.1
other minor corrections
3 Submission Version (final) Modify 2.0

1.2 Known Issues, Limitations & Restrictions

All known (pending) issues:

With the current scale of operations, manual management faces many difficulties and
disadvantages, namely: If the above activities want to perform well, the departments must
screen and select information manually. Investing a large amount of time requires a lot of
participants and not high accuracy

The old system also causes difficulties in management statistics and the security

Safety of some information is not high

Some systems have not decentralized system users.

Limitations :
In addition to the basic extended features of the product, we also have some limitations that
are not yet integrated for access in the product.

Limitations in product functionality

High scalability

Integrated management of many hotels in the system

Manage room bill

Room rate includes tax, deposit fee

Support split bill, bill merge function

Integrated online booking room function

Support online deposit payment

Integrate and check VIP membership

Integrate hotel promotions.

Restrictions in the final deliverable package:

Executive management features

Indispensable feature for hotel owners themselves. All sales figures per day, week, month,
staff activity will be controlled by the hotel owner. This feature helps hotel owners have an
overview of the hotel operations in a certain period of time and have a reasonable plan in
the future.

Feature that allows integration with 3rd party

A good hotel management software needs to integrate and work effectively with countless
other hardware and software. A standard hotel today usually has PABX, Door Lock, ID
scanner, cash drawer, payment gateway and other financial accounting software. And it
would be beneficial if your PMS is compatible with the above devices.

2. Installation Guides
2.1 System Requirements
System requirements are quite simple. With 2 main functions:
Login to decentralize and use the system what users need is just a computer or a phone to
access the internet and use the application directly on the web. Currently, we have not
developed a system on software and integration using the specifically language for phone
software.
2.2 Setup Files
User: not need to installed any things of systems.
Hotel staff: software engineering staff will come to the hotel to set up a multi-faceted
integration process with data packages and processes.
2.3 Installation Instruction
Hotel staff:

Founder will provide open source link and different query system to make it easier to use.

User:

Users just need to visit the page source as below and search for the appropriate hotel information.

3. User Manual
3.1 Terms and definitions
Programs and projects use appropriate terminology that is not too difficult to understand,
close to daily life, towards the convenience of using the system for both users and hotel
staff.
Accompanying we will arrange a few symbols or labels to beautify the layout and be clear in
each product use function.
3.2 System requirements

For system request support we have included a feature that allows users to contribute
personal opinions with support to contribute to building the system.
For hotel staff, we also create direct contact with the technical department's support
switchboard to handle fault maintenance and upgrade their own system.
3.3 Application Usage
a. Overview
The hotel supply chain management project is a management system used on the web, with
management, providing information in search and gathering for easier service applications
for customers in the technology age number.
System evaluation: Through actual survey, it can be seen that the management in many
hotels is also done quite manually. Therefore, the purpose of this topic is to minimize
manual works to ensure the accuracy and reliability of work. However, due to the nature of
work, in this system, there is still a need for human performance, namely the receptionist.
This section details manual tasks and tasks performed by the computer. Most of the
functions of the system discussed below are performed by computer, only a few of the tasks
mentioned must be performed manually. All done on the computer
b. Feature 1
Descript the purpose of this feature:
Functional purpose: for users to conveniently view the cost of using the room and a number
of available utilities and services
List of functions used in this feature:
Room booking function
Room service details
Insert the user interface(s) of each function and provide step by step description of how to
use that function:
First step: After accessing the hotel you want to see the information will display a product
list of rooms in the hotel.

Second step: Users will continue to select the View button to view product details in any
room they want.
Third step: In this step, users will see detailed product information.

c. Feature 2
Descript the purpose of this feature: Display the function of accessing and filling in
information to register for a room directly on the web, register the hotel room that the user
chooses
Insert the user interface(s) of each function and provide step by step description of how to
use that function:
Here the user directly fills in personal information and confirms the product's information

3.4 Troubleshooting
Descript some common troubles while using application
A common case is that after a user fills in the access information but is not recorded to use
the room, it can be understood that for a number of reasons sometimes the web application
does not load in time with some network signal error, or sometimes when the user also does
not fill in this information properly with the pre-established user format, ...
In other cases, it could be at wifi or spyware, …
There are cases we don't know yet
Users can directly contact the hotel department or support policy right on the web for help.

VII. Appendix
1. Glossary

Definition and Acronyms

Acronym Definition

HSSM Hotel supply chain system

BK Booking

RB Room Booking

DT Details
 USP User support policy

GUI Graphical User Interface

UC Use Case

API Application Program Interface

ERD Entity Relational Diagram

2. References
https://www.slideshare.net/Bchm2/cc-khi-nim-c-bn-d-n-phn-mm
https://www.slideshare.net/damanh64/qun-tr-d-n-cng-ngh-thng-tin