1 . Team members :

_ Nguyễn Minh Hải .

_ Lê Anh Nam.

_ Nguyễn Xuân Trường.

_ Trần Công Thắng.

_ Đoàn Văn Hiếu.

2. Project:

Hotel management system

3. System analysis:

3 .1 System-as- is study: Vietnam hotels mostly use notebook to save information. This leads to many problems:

_ Info is not safe and easy to lose.

_ Having many info make it ’s hard to organize.

_ Hard to manage guest and ca lculate their bi l ls .

_ Hard to manage staffs and payment.

_ Writing is very time-consuming.

3.2 System-to-be objectives: Hotel Management System is a software which helps to solve al l of the above problems:

_ Saving time, money, very easy to use.

_ Safe and secure system.

_ Support multiple accounts.

_ Support guest to reserve the room through internet .

4. Stakeholder identify:

4 .1 . Stakeholder:

_ Owner of hotel .

_ Receptionist .

_ Manager.

_ Onl ine guest.

HOTEL MANAGEMENT SYSTEM

4 .2 Use case diagram:

5. Context diagram:

6. Use cases l ist:

Owner Set room ratesView reports

Manage staff Add staff membersDelete staff membersUpdate staff infoBackup data

Manage User Add UserDelete UserUpdate User detai l

Receptionist Search avai lable roomManage reservation Make reservation

Add servicesEdit reservationCancel reservation

Manage guest Add guestUpdate guest deta i lIssue bi l l

Manager Manage room Add roomDelete roomUpdate room detai lsView staff detai ls

Manage inventory Add itemDelete i temEdit i tem detai l

Make report

Onl ine guest Check avai lable roomsMake reservationCancel reservation

7. Interface design:

(Not done yet stil l updating)

Log In screen for different user:

Owner menu:

Manager menu:

Receptionist menu:

Website booking request form:

Add guest:

Make reservation:

View and edit reservation:

Search and edit staff:

Issue bi l l :

8. Non-functional requirement:

8 .1 Performance requirement:

_Performance requirements define acceptable response times for system functional ity . The load time for user interface screens shal l take no longer than two seconds. I t makes fast access to system functions. The log in information shal l be ver ified within five seconds causes. Returning query results within five seconds makes search function more accurate.

8.2 Safety requirement:

_There are several users in the system, each account wi l l be protected by a User Log In screen that requires a Username and Password.

_The backup option ensure the system database secur ity . System can be restor ing in case of emergency.

8.3 Securi ty requirement:

_ Customer Serv ice Representatives and Managers and owner wi l l be able to log in to the Hotel Management System. Customer Service Representatives wi l l have access to the Reservation/Booking and subsystems. Managers wi l l have access to the Management subsystem as wel l as the Reservation/Booking subsystems. Owner has the maximum pr ivi lege to al l subsystems. Access to the var ious subsystems wi l l be protected by a user log in screen that requires a user name and password.

8.4 Software qual i ty attr ibutes:

• Avai labi l i ty : - The system shal l be avai lable during normal hote l operating hours

• Correctness: - extent to which program satisfies specifications, fulfil l s user’s miss ion objectives

• Efficiency: - How much less number of resources and time are required to achieve a particular task through the system.

• Flex ibi l i ty: - Abi l i ty to add new features to the system and handle them conveniently .

• Integr ity : - How the system would insecure the information in the system and how it avoids the data losses. Referential integrity in database tables and interfaces

• Mainta inabi l i ty: - How easy is to keep the system as i t is and correct defects with making changes.

• Portabi l i ty : - The Hotel Management System shal l run in any Microsoft Windows environment

• Rel iabi l i ty : - Speci fy the factors required to establ ish the required re l iabi l i ty of the software system at time of del ivery. Mean time between fa i lures and mean time to recovery

• Reusabi l i ty : - What is the abi l i ty to use the avai lable components of the system in other systems as wel l .

• Testabi l i ty : - Effort needed to test to ensure performs as intended

• Usabi l i ty : - How easi ly a person can be taken the benefits of the system and the user fr iendl iness.

• Robustness: – Strength of the system to handle system functions accurate ly and mainta in the database without facing to unexpected fa i lures

• Mainta inabi l i ty: – What des ign, coding standards must be adhered to exc lusions created