1.1 References: Books
1.1 References: Books
1 References
Books:
[1] IanSommerville,Software Engineering 8th edition.Pearson education,2008.
[9]Louw,D,(2006, may 10).Description with UML for a Hotel Reservation System. Retrieved
from
http://www.liacs.nl/assets/Bachelorscripties/2006-08JanneLouw.pdf
Project Documentation section reveals the all the details about documents created by the
project team so far of this project. It includes project charter and project proposal.
Project charter: - This document provides the basic information about the team
members their responsible in developing functions, the background of the
client and the nature of the main problem identified
Project Proposal: - The proposal of the project consists with the problems that
are identified with the client, and the solutions that are going to implement
using the proposed system.
User manual provide to the client will give a clear idea in interacting with the system. It will
be written in a simple understandable language concealing the inner complexity of the
system. A hard copy of the user manual will be delivered to the client with the delivery of
system.
Some software used in implementing the system is with high cost and the client has agreed to
afford the amount of money needed to purchase them. It’s assumed that client won’t change
that decision on the next phases of the software development. Although we assume that client
is using windows 7 or windows 8. Otherwise if client use an open source operating system,
there is a need of changing the SRS accordingly.
1.6 Communications Interfaces
When a specific reservation reserved at the same time an e-mail notification will be sent to
both relevant staff member’s e-mail account and guest’s account. Guest will be notified in the
check-out date. To achieve that functionality, it requires having a stable internet connection.
Mostly a broadband connection with the client’s computer will provide the efficient
servOther Nonfunctional Requirements
1.2Performance Requirements
There are several user levels in hospitality management system, Access to the various
subsystems will be protected by a user log in screen that requires a user name and password.
This gives different views and accessible functions of user levels through the system.
Maintaining backups ensure the system database security. System can be restoring in any
case of emergency.
1.4Security Requirements
Customer Service Representatives and Managers and owner will be able to log in to the Hotel
Management System. Customer Service Representatives will have access to the
Reservation/Booking and subsystems. Managers will have access to the Management
subsystem as well as the Reservation/Booking subsystems. Owner has the maximum
privilege to all subsystems. Access to the various subsystems will be protected by a user log
in screen that requires a user name and password.
1.5Business Rules
Mariott Hospitality Management System will perform under three users which are Owner,
Manager and Receptionist. The system is designed in a way where responsibility and
privileges are decreased in the order of owner, manager and receptionist. The role of manager
is elected in the aim of making the owner’s hands free from regular interfering with the
system. So, most of the privileges that owner has are given to manager, except the ones are
critical and important. Some features like that are, taking backup, restoring of the system and
handling financial details, hotel income reports of the system. Receptionist is given with the
most frequently used features of the system which has less responsibility than the other two
users. Deleting of any information in the system is only allowed for the owner of the Resort
2. Other Requirements
When the system is completely developed and submitted to the client, few sessions will be
required to make the users of the system understand about the functionality of it and some
time to adapt to the system. After those sessions, it’s required that a member from the
development team should spend sometime in the system background for an agreed time
period. That time period will be used in identifying new bugs that could not be reached in the
earlier phases of the development process.
Client should have a valid e-mail account in order to receive reservation e-mail notifications.
Payment Management System
The system should allow customer to pay bill via online using credit
or debit card
Select Once the confirmation done, the Payment Gateway page will
be displayed as shown below. any of the Gateways Select the mode
of payment Net Banking / Debit Card / Credit card then click on
accept terms and conditions .
Add Payment
Steps to pay through online
1. Visit your merchant website.
2. Select Debit/Credit Card as payment option.
3. Enter the details like Debit Card No, Expiry Date, CVV printed on your Card.
4. Enter your 6 digit PIN or One time password.
5. Once the payment made successfully the following screen will appear
click on PAY
After the Pay Now the OTP will come to your mobile and complete the payment
2. Functional requirement for website
The site should be designed to allow any users to search database from hospitality
system database. The system should allow customer to view information of rooms and hotel
and allow customer to book the records in the database, accept the payment and provide
confirmation. Other function that could increase the usability of a website is:
1. Automatic email confirmation of the room booking.
2. Confirmation of payment details.
3. Provide list of room available and rates.