View
27
Download
4
Category
Tags:
Preview:
DESCRIPTION
nothing
Citation preview
Hotel Management System
System Requirements Specification
Version: SRS 2.0
Prepared by
Team # 26
Ruken GÜNEŞ
Bahar TEKE
Özlem HAYRAT
Ömer ÖZTÜRK
2012
XYZ PROJECT
Preface
This document is Software Requirement Specification for our project named as Hotel
Management System. In this document, requirements will be documented clearly.
Atılım University
COMPE/SE/ISE 491-492
2/30
Team # 5 (Team ABC)
System Requirements Specification
Version: X
XYZ PROJECT
List of Table
TABLE 1. REZERVATION.................................................................................................................... 18
TABLE 2. USER AUTHENTICATION...................................................................................................19
TABLE 3.MANAGE ROOM .................................................................................................................. 21
TABLE 4. SEND MESSAGE................................................................................................................. 22
TABLE 5. CONTACT SUPPLIER.........................................................................................................23
Atılım University
COMPE/SE/ISE 491-492
3/30
Team # 5 (Team ABC)
System Requirements Specification
Version: X
XYZ PROJECT
Table of Contents
PREFACE ............................................................................................................................2
List of Figures........................................................................................................................3
List of Tables..........................................................................................................................3
Table of Contents...................................................................................................................4
1. Introduction..................................................................................................................6
1.1. Purpose......................................................................................................................6
1.2. Scope.........................................................................................................................6
1.3. Definitions, Acronyms & Abbreviations..................................................................7
1.4. References.................................................................................................................8
1.5. Overview...................................................................................................................9
2. Overall Description....................................................................................................10
2.1. Product Perspective.................................................................................................10
2.1.1. System Interfaces.............................................................................................10
2.1.2. User Interfaces............................................................................................10-11
2.1.3. Hardware Interfaces.........................................................................................11
2.1.4. Software Interfaces...........................................................................................11
2.1.5. Communication Interfaces...............................................................................12
2.1.6. Memory............................................................................................................12
2.2. Product Functions...................................................................................................13
2.3. User Characteristics................................................................................................16
2.4. Constraints..............................................................................................................16
2.5. Assumptions and Dependencies.............................................................................17
3. Specific Requirements...............................................................................................17
3.1. External Interfaces..................................................................................................17
3.2. Functional Requirements........................................................................................18
3.3. Reservation……………………………………………………………………18
3.4. Performance Requirements.....................................................................................24
3.5. Logical Database Requirements.............................................................................24
3.6. Design Constraints..................................................................................................25
3.6. Software System Attributes....................................................................................25
Atılım University
COMPE/SE/ISE 491-492
4/30
Team # 5 (Team ABC)
System Requirements Specification
Version: X
XYZ PROJECT
4. Appendices............................................................................................................27-37
Atılım University
COMPE/SE/ISE 491-492
5/30
Team # 5 (Team ABC)
System Requirements Specification
Version: X
XYZ PROJECT
1. Introduction
1.1. Purpose
The purpose of this document is reflecting all the requirements, constraints and design
activities. This document contains the requirements which are supposed to submitted to our
supervisor on time. Our project will be depend on these requirements.
1.2. Scope
The scope of our project is designing a web environment to provide a safe and user
friendly system for hotel management. In this environment, there will be different types of
user and those are: hotel administirator, accounter and client. For all those user types, there
will be different interfaces.
Our project will cover these properties:
- A room reservation system for client (authorized user).
- An information system for hotel administrator.
- A log-in and sign-up interface for visitor (unauthorized user).
- Search information
- Manage room and employee
- Announcement
For every type of users, there will be a different interface and properties which are
metioned above.
Atılım University
COMPE/SE/ISE 491-492
6/30
Team # 5 (Team ABC)
System Requirements Specification
Version: X
XYZ PROJECT
1.3
DEFINATIONS
COCOMO
Constructive Cost Model
DB Database
FP Function Points
GUI Graphic User Interface
HTML Hypertext Markup Language
HW Hardware
IDE Integrated Development Environment
IE Internet Explorer
IEEE Institute of Electrical and Electronics Engineers
I/O Input / Output
IP Initial Plan
Java EE Java Enterprise Edition
Java ME Java Micro Edition
KLOC 1000 Lines of Code
KU Knowledge Unit
LOC Line Of Code
MIDP 2.0 Mobile Information Device Profile
MS Microsoft
PS Problem Statement
RAM: Random Access Memory
SDD Software Design Description
SPS Student Portal System
SPMP Software Project Management Plan
SQL Structured Query Language
SRS Software Requirements Specification
SW Software
Atılım University
COMPE/SE/ISE 491-492
7/30
Team # 5 (Team ABC)
System Requirements Specification
Version: X
XYZ PROJECT
1.4. References
IEEE Std 1058-1998, IEEE Standard for Software Project Management Plans
Pressman, Roger S., Software Engineering, 4th edition, McGraw-Hill, 1997
Fairley, R. E., Work breakdown Structure, Software Engineering Project
Management, IEEE CS Press, 1997
Atılım University
COMPE/SE/ISE 491-492
8/30
Team # 5 (Team ABC)
System Requirements Specification
Version: X
XYZ PROJECT
1.5. Overview
In section 2, an overall description for SRS will be given from product perspective,
functional requirements, constraints, user types and assumptions. In product perspective,
user interfaces will be mentioned. Since there is no hardware interface in our project,
hardware interface is not included in our SRS document. In function requirements
subchapter, functions, accessing of those functions personally and pre and post conditions
will be mentioned. Also, user types, constraints and assumptions will be mentioned.
In section 3, specific requirements will be considered in detailed. Major functions, how
they work and who will access them will be described.
Atılım University
COMPE/SE/ISE 491-492
9/30
Team # 5 (Team ABC)
System Requirements Specification
Version: X
XYZ PROJECT
2. Overall Description
In this section of SRS, the general factors that affect the product and its requirements will
be described.
2.1 Product Perspective
2.1.1 System Interfaces
Our project will consist of two main parts which are a database system for holding
information and user interface for accessing those information.
2.1.2 User Interfaces
Since there are 5 types of users, there are 5 types of user interface and those are;
- Administration interface
- Staff Interface
- Authorized (Customer) user interface
- Unauthorized (Guest)user interface
These interfaces will be variated according to user’s requirements. However they will have
some common properties such as:
- A customizable window theme (colors, font types, etc.)
- Menus
- Windows layouts
There will be a registration system for every type of user. In registration step, user will
define their type(administrator, accounter or client) and after registration they will reach
different interfaces.
Atılım University
COMPE/SE/ISE 491-492
10/30
Team # 5 (Team ABC)
System Requirements Specification
Version: X
XYZ PROJECT
The interfaces will contain checkboxes, text areas, and combo boxes to prevent user
entering wrong inputs. Checkboxes and combo boxes will be designed for every possible
user inputs without constratining the user. Also, system will try to minimize errors but if an
error occurs, user will be informated with a window.
The interfaces for each user types are below:
- Administrator Interface: When administrator logged in to system, they will reach
this interface. It allows administrators to add or delete rooms, send e-mail or
messages to other type of users (except from unauthorized users), contact to
supplier companies (food, room materials etc.), and reach to customers’
information.
- Staff Interface: Staff can manage announcement and restaurant function.
- Authorized(Customer) User Interface: When a user log-in to the system, they
can see the prices and status of the rooms, and can make reservation.
- Unauthorized(Guest) User Interface: An unauthorized user can sign-up or log in
to the system.
- Administrator Interface: Admin can manage rezervation, employee, user
authentication in the system.
2.1.3 Hardware Interfaces
Not applicaple in our project.
2.1.4 Software Interfaces
Since our project is a web application, a modern web browser can be operated by the
application. Although our project is platform independent, an up-to-date operation system
is recommended.
Communication Interfaces
Data transmission between server and client is achieved by using TCP/IP (Transmission
Atılım University
COMPE/SE/ISE 491-492
11/30
Team # 5 (Team ABC)
System Requirements Specification
Version: X
XYZ PROJECT
Control Protocol/ Internet Protocol). Moreover, HTTP (Hyper Text Transfer Protocol) will
be used.
2.1.5 Memory
Since an up-to-date web browser requires a modern operating system, memory requirement
will be higher than the application’s need. At least 512 MB RAM is recommended for user
side and on the database server side, 4 GB RAM is required. On the user side, minimum 1
GB free disk space and on the database server side, minimum 1 TB hard disk is required.
Minimum System Requirements for Personal Computers:
- 1 GHz 32 bit Intel, AMD or equivalent CPU.
- 512 MB RAM
- Minimum 1 GB free disk space
- An up-to-date OS is recommended for browser support (Windows XP or higher)
Minimum System Requirements for Database Server
- 2 GHz Intel Xenon or equivalent CPU
- 4 GB RAM
- 1 TB Hard disk space
Since today it is possible to reach a web site with a mobile phone, internet connection and
a supported web browser (Opera Mini, etc.) is required for mobile phones.
Atılım University
COMPE/SE/ISE 491-492
12/30
Team # 5 (Team ABC)
System Requirements Specification
Version: X
XYZ PROJECT
2.2. Product Functions
General functions that Hotel Management System project will perform are given in this
part.
2.2.1. Users Functions
2.2.1.1 User Authentication
- Login
- Determine Authorization Level
- Change Password
- Lost Password
- Registration
2.2.2. Authorized User Functions
2.2.2.1 Reservation Function: By this function, an authorized user (customer)
can book a room that fits to their needs and budget. Customer can see the status
and prices of the rooms. Customer can modify reservation.
2.2.3. Administration Functions
2.2.3.1 Add/Delete/Modify Room: An administrator can add or delete a
room by this function. Also administrator can change the price of the rooms.
The only constraint of this function is, if a room is reserved, it cannot be
deleted.
2.2.3.2 Changing Room Status: Administrator can change a room’s status
as “RESERVED”, “AVAILABLE” or “NOT AVAILABLE” manually.
Atılım University
COMPE/SE/ISE 491-492
13/30
Team # 5 (Team ABC)
System Requirements Specification
Version: X
XYZ PROJECT
However, changing room’s status to “RESERVED” operation will be done
automatically. When customer’s payment is reach to the hotel’s bank account,
an e-mail will be sent to the administrator to confirm the reservation and the
chosen room’s status will be changed as “RESERVED”.
2.2.3.3 Sending Message: An administrator can send and receive message to
ad staff by using “MESSAGE” panel.
2.2.3.4 Contact To Supplier Companies: Administrator can send and
receive e–mail to supplier companies by using “CONTACT” panel.
2.2.3.5 Customer and Staff Information: By this function,
administrator can reach customers’ and staff’s information that they entered
when they signed up to the system.
2.2.3.6 Search : Admin can search room, employee and customer information
2.2.4 Staff Functions
2.2.4.1 Send-Receive Message: Staff can send and receive message
to/from administrator by this function. It can be performed in “MESSAGE” panel.
2.2.4.2 Announcement: Staff can add, delete and modify announcement.
2.2.4.3 Restaurant management: Staff can manage information related
with restaurant.
2.3 User Characteristics
The users of Hotel Management System is customers who want to book a hotel room, hotel
staff, accounters and administrators. All of the users are assumed to be manage those
operations and have those materials;
Atılım University
COMPE/SE/ISE 491-492
14/30
Team # 5 (Team ABC)
System Requirements Specification
Version: X
XYZ PROJECT
- Having a personal computer. (Database server is not needed by the user side)
- An internet connection.
- Ability to access a web page using a modern internet browser.
- Ability to perform sign-up and log-in operations.
- Being familiar to a web site environment.
- Ability to online paying system. (For customers)
- Being familiar to an çevrimiçi management system. (For administrators, staff and
accounters)
2.4 Constraints
The constraints of our project are given below;
- System Requirement Constraints: Personal computers and database
sunucu have to satisfy the minimum system requirements which are given in
Section 2.1.6.
- Reliability and Security Constraints: Our team members will work
hard for security issues. However if there is a security problem on database side, it
will be handled as soon as possible.
Atılım University
COMPE/SE/ISE 491-492
15/30
Team # 5 (Team ABC)
System Requirements Specification
Version: X
XYZ PROJECT
2.5 Assumptions and Dependencies
Assumptions and dependencies are listed below;
- The system interfaces are assumed to be work properly.
- It is assumed that minimum system requirements are satisfy
- The user characteristics are assumed to be satisfied.
3 Specific Requirements
3.1 External Interfaces
3.1.1 User Interface
The application will have customizable menus (colors, font types, etc.) and for
different user types, there will be different interfaces. The symbolic tables are
given in appendix section.
3.1.2 Hardware Interfaces
All the data will be kept on our database server so our project will work on this
database.
3.1.3 Sofware Interfaces
Hotel management system will use an operating system, web browser, database
management system and a web server supporting the language.
On the server side of SPS, OpenSolaris 10 shall be used. “OpenSolaris is a free
Atılım University
COMPE/SE/ISE 491-492
16/30
Team # 5 (Team ABC)
System Requirements Specification
Version: X
XYZ PROJECT
unix operating system providing innovative technologies like dTrace, ZFS and
IPS for the enterprise or the dorm room. By using this O/S at server side, SPS
shall have all the power of unix.”
On the user side, any up-to-date web browser can be used. As scripting and
programming languages, ASP.NET and C# will be used.
3.1.4 Communication Interfaces
Data transmission between server and client is achieved by using TCP/IP (Transmission
Control Protocol/ Internet Protocol). Moreover, HTTP (Hyper Text Transfer Protocol) will
be used.
3.2 Functional Requirement
3.3
Table 1. Reservation
Use Case Name: Reservation
Priority High
Trigger
Precondition User must be signed in
Basic Path 1. User log in to system
2. Choose reservation menu
3. Choose a suitable room
4. Click book button
Atılım University
COMPE/SE/ISE 491-492
17/30
Team # 5 (Team ABC)
System Requirements Specification
Version: X
XYZ PROJECT
5. Make payment
6. A notification is sent to administrator if payment is done
correctly.
7. Administrator gives permission to user.
Alternate Path
Postcondition Reservation is end and System saved a reservation
successfully.
Exception Path 1. User log in to system
2. Choose reservation menu
3. Choose a suitable room
4. Click book button
5. Make payment
If payment is not done correctly, user gets an error report.
Other
Reference:
Table 2, User Authentication
Use Case Name: User Authentication
Priority High
Trigger
Precondition User begins the registration system.
Basic Path 1. Clicks on sign-up button
Atılım University
COMPE/SE/ISE 491-492
18/30
Team # 5 (Team ABC)
System Requirements Specification
Version: X
XYZ PROJECT
2. Enters their information
3. Confirms with their information
Alternate Path
Post condition User account is saved by the system.
Exception Path 1. User enters the web site
2. Clicks on sign-up button
3. Enters their information
4. Confirms with their information
5. If en error occurs, user gets an error report
Other
Reference:
Table 3. Manage Room
Use Case Name: Manage Room
Priority High
Trigger
Precondition User has to be logged in to system and has administrator
authority.
Basic Path 1. Admistrator logs in to the system.
2. Clicks on room menu
3. Chooses if he/she wanted add room, delete room
or modify room.
Atılım University
COMPE/SE/ISE 491-492
19/30
Team # 5 (Team ABC)
System Requirements Specification
Version: X
XYZ PROJECT
4. Clicks on save button.
Alternate Path
Post condition Change of room is saved.
Exception Path 1. Admistrator logs in to the system.
2. Clicks on room menu
3. Chooses if he/she wanted add room, delete room
or modify room.
4. Clicks on save button.
5. If an error occurs in those processes,
administrator gets an error report.
Other
Reference:
Table 5, Send Message
Use Case Name: Send Message
Priority High
Trigger
Precondition User has to be logged in to system and has administrator or
staff on the message menu.
Basic Path 1. User clicks on message menu
2. Clicks on message
Atılım University
COMPE/SE/ISE 491-492
20/30
Team # 5 (Team ABC)
System Requirements Specification
Version: X
XYZ PROJECT
3. Clicks on Send message
4. Fills the header and body spaces
5. Clicks on send.
Alternate Path
Post condition Message is send.
Exception Path 1. User clicks on message menu
2. Clicks on message
3. Clicks on Send message
4. Fills the header and body spaces
5. Clicks on send.
6. If an error occurs, user gets an error report.
Other
Reference:
Table 6, Contact Supplier
Use Case Name: Contact Supplier
Priority Low
Trigger
Precondition User has to be logged in to system and has administrator
authority on the supplier menu.
Basic Path 1. User clicks on the supplier menu.
Atılım University
COMPE/SE/ISE 491-492
21/30
Team # 5 (Team ABC)
System Requirements Specification
Version: X
XYZ PROJECT
2.Choose the company name
3. Send an e-mail or reach the address and phone information.
Alternate Path
Post condition End
Exception Path 1. User clicks on the supplier menu.
2. Choose the company name
3. Send an e-mail or reach the address and
phone information.
4. If an error occurs, user gets an error
message.
Other
Reference:
3.4 Performance Requirements
Hotel Management System is a web application, so the connection speed has an active role
for performance. Although in user side, number of online users is not important, on server
side it is a critical factor. To prevent this our team will choose a high-end database server
which has the hardware given in Section 2.1.6.
3.5 Logical Database Requirements
ER diagram for database entities, attributes and relations is given in APPENDIX section.
3.6 Design Constraints
Atılım University
COMPE/SE/ISE 491-492
22/30
Team # 5 (Team ABC)
System Requirements Specification
Version: X
XYZ PROJECT
For Hotel Management System project, the design constraints are given below;
Hotel Management System is a web application, so it requires an internet
connection.
All the users must be logged in to use their different functions and interfaces.
All the users must use a modern web browser with an up-to date operating system.
(Details are in Section 2.1.6.)
The survey planned will create a basis for better understanding of needs of users, in
addition survey will be taken into consideration at design state.
3.7 Software System Attributes
3.7.1 Reliability
Hotel Management System will be designed for work on every environment, as
long as required hardware and software is provided. During the test process,
any possible hardware and software combinations will be tested.
3.7.2 Availibilty
Apart from backing up data process, Hotel Management System will be
available any time as long as required hardware and software is provided.
3.7.3 Security
Our team members will work hard on security issues. For critical operations
such as signing up process, ready-made algorithms will be used. Also all
possible precautions will be taken for hacker attacks such as SQL injection or
Cross Site Scripting.
3.7.4 Maintainability
Hotel Management System will be maintainable as long as there are no HW
problems. Also databases should be updated.
Atılım University
COMPE/SE/ISE 491-492
23/30
Team # 5 (Team ABC)
System Requirements Specification
Version: X
XYZ PROJECT
4. Appendices
Appendix 1 – ER Diagram
Appendix 2 – Use-Case Diagrams
Atılım University
COMPE/SE/ISE 491-492
24/30
Team # 5 (Team ABC)
System Requirements Specification
Version: X
XYZ PROJECT
4.2.1.Use Case Diagram for Contact Supplier Company
4.2.2 Use Case Diagram for Manage Room
Atılım University
COMPE/SE/ISE 491-492
25/30
Team # 5 (Team ABC)
System Requirements Specification
Version: X
XYZ PROJECT
4.2.3 Use Case Diagram for Message Function
4.2.4 Use Case Diagram for Reservation Function
Atılım University
COMPE/SE/ISE 491-492
26/30
Team # 5 (Team ABC)
System Requirements Specification
Version: X
XYZ PROJECT
4.2.5 Use Case Diagram for Modifying Room Status
4.2.7 Use Case Diagram for User Authentication
Atılım University
COMPE/SE/ISE 491-492
27/30
Team # 5 (Team ABC)
System Requirements Specification
Version: X
XYZ PROJECT
Appendix 3 – Interfaces
4.3.1 Reservation Interface for Authorized Users
BANNER
ROOM FINDER: Low Price High Price FIND
ROOM 1 ROOM 2 ROOM 3
IMAGE IMAGE IMAGE
STATUS: AVAILABLE STATUS: RESERVED STATUS: N/A
PROPERTIES: ... PROPERTIES: ... PROPERTIES: ...
PRICE: 300$ PRICE: 300$ PRICE: -
BOOK
Atılım University
COMPE/SE/ISE 491-492
28/30
Team # 5 (Team ABC)
System Requirements Specification
Version: X
XYZ PROJECT
4.3.2 Unauthorized User Interface
BANNER
HOME CONTACT ABOUT US SIGN UP LOG-IN
ADVERTISEMENTS
Atılım University
COMPE/SE/ISE 491-492
29/30
Team # 5 (Team ABC)
System Requirements Specification
Version: X
XYZ PROJECT
4.3.3 Admin Interface
BANNER
ROOMS MESSAGES SUPPLIER CUSTOMERS LOG-OUT
ADVERTISEMENT CREATOR
RESERVATIONS
Atılım University
COMPE/SE/ISE 491-492
30/30
Team # 5 (Team ABC)
System Requirements Specification
Version: X
Recommended