software requirements specfication

1. Software Requirements
Specification
HOTEL MANAGEMENT SYSTEM
FOLLOWING INCREMENTAL DEVELOPMENT MODEL
1

2. Submitted To:
Mr. Tanvir Ahmed
Lecturer
Department of CSE
Dhaka International University
Submitted By:
Name Roll
Md.Reza-Ul-Islam Nishan 26
2

3. Overview
Introduction
Motivation
Functions
User Definition
System Requirements
Functional Requirements
Non-Functional Requirements
Our Challenges
Design and Implementation Constraints
3

4. Introduction
The motivation behind this Software is to depict the
Hotel Management System . This record contains the
practical, behavioral and non-practical necessities of
the Project and it additionally contains the rules for
framework specialists and system engineers and
designers to start working the project.
4

5. Motivation
 Our Hotel Management system is different from ordinary pen-paper
note down system. We just want to come out from the old systems to
include with online accessing system and under strong management
protocol. The concept of easy to booking any where of the world, is
more precise to develop the system. Maintain the room directory &
availability by computer and use a simple database system was our
main target. In here we also update the employee management with
out system to save the owner valuable time and reduce the operation
cost.
5

6. Functions
Administrator :
 Responsibility and power of admin
 Capability of admin
 Booking conformation
 Offer & discount
Operating System:
 The Hotel Management System is a website and shall operate in all famous browsers, for a model we are taking
Microsoft Internet Explorer ,Google Chrome, and Mozilla Firefox.
Dependencies:
 Our Website needs the following third party products.
 Microsoft SQL server to store the database.
 PHP to develop the Site.
6

7. User Definition
User
Internal user External user
Admin Customer
System Manager Others Organization
Booking Officer
7

8. Internal User
Admin:
 Able to change any settings
 Admin give the approval to any Registration process
 Add or delete any reservation
 Have authority to make any sudden change
 Can able to access the developing option
 Admin can cheek the all staff and current directory any time
System Manager:
 Can see the simulation part of main system
 Able to change any settings with the admin permission
Booking officer:
 Booking officer cant able to make any change, he just maintain the process properly.
8

9. External User
Customer:
 Customer's have no access the internal system.
 They can just visit the website
 Customer's can send a review to update the system if need
Others Organization:
 Can visit the guest site
 Can send a review
9

10. User Characteristics
Internal User:
 Internal user have to well trained to use the system
 All have to well known about the whole system
 Have to maintain a chai communication
 Concern about the security option, to keep it more secure
External User:
 A minimum level to understand the registration and terms-policy is must
 No miss use and unwanted using is not allowed
10

11. System Requirements
Hardware
 Only the recommended configuration (basic requirements of a computer system ) no other specific hardware
is required to run the software.
Software
 Browser to load and view the web pages
 Operating System
11

12. Functional Requirements
Outlook:
 Hotel name , Menu and Search bar.
 Book Now- Customer can choice date, category, price, payment method.
 Event, Business space, Advertise.
 Current offer, News, About, Address.
 Login / Signup option- Existing user can login directly. But new user need to signup.
 Review, Question, Info.
Admin Panel:
 Todays Request- Room booking, New signup, Review.
 Room- Available room, Cheek out info.
 Payment- Total transaction, Todays balance.
 Settings.
12

13. Non-Functional Requirements
This function is our responsibility, our developer will figure out this like-
 System backup
 Routine cheek of the system
 Error detection
 Storage management
 Performance measurement
 Safety measurement
 Security management
 Version update
13

14. Our Challenges
As we are try to follow Incremental Development Model. Which can also define as “Quick Serve”.
Our Challenges are be like-
 Deliver the product with basic requirements
 Care about the data secure process
 Continues monitoring to the development process
 Maintain the communication with clients and keep them pleasure about the project
 Update the system as fast can possible
 Ensure the best support team to fix any kind of error
 Ensure the best quality for the final version
14

15. Design and Implementation Constraints
Our following Model
15

16. Design and Implementation Constraints 16

17. 17