Index

1. Synopsis 2. SRS
1. Introduction 1.1 Purpose 1.2 Scope 1.3 Definitions, Acronyms, and Abbreviations 1.4 References 1.5 Overview

3 4-13

2. The Overall Description 2.1 Product Perspective 2.1.1 System Interfaces 2.1.3 Interfaces 2.1.3 Hardware Interfaces 2.1.4Software Interfaces 2.1.5 Communications Interfaces 2.1.6 Memory Constraints 2.1.7 Operations 2.1.8 Site Adaptation Requirements 2.2 Product Functions 2.3 User Characteristics 2.4 Constraints 2.5 Assumptions and Dependencies 2.6 Apportioning of Requirements

3. Specific Requirements 3.1 External interfaces

1|Page

3.2 Functions 3.3 Performance Requirements 3.4 Logical Database Requirements 3.5 Design Constraints 3.5.1 Standards Compliance 3.6 Software System Attributes 3.6.1 Reliability 3.6.2 Availability 3.6.3 Security 3.6.4 Maintainability 3.6.5 Portability 3.7 Organizing the Specific Requirements 3.7.1 System Mode 3.7.2 User Class 3.7.3 Objects 3.7.4 Feature 3.7.5 Stimulus 3.7.6 Response 3.7.7 Functional Hierarchy 3.8 Additional Comments

4. Change Management Process 5. Document Approvals 6. Supporting Information

3. Design 3.1 Data base design E R Diagram 3.2 DFD 3.2 Flow chart

13-20

4.Biblography
2|Page

21

1. Synopsis
1.1 objectives
To give better cervices to the customers. Online room searching and booking facilities. Employee details checking facilities. To search a particular guest in hotel.

1.2 Functions
The major functions, which the Hotel Management System will perform are: Registering new user by collecting user information. Log-in for subscription to enter into the system. This permits the user to access their user details and book the rooms according to specified procedure. The facilities include Review the Room information by user-id and password. View the information Book the room on the availability procedure.

1.3 REFERENCES:
Internet Explorer. Google Existing Documents of Hospital management
3|Page

2.SRS 1. Introduction
Main aim of hotel is to provide the customers information related to the room availability tariff and the other facilities.

1.1 Purpose
The main aim of HOTEL MANAGEMENT SYSTEM is it gives the customer view of the hotel. The customer needs in hotel, enquiry about rooms, reservation process, vacating process, cancelling the reservation, and the restaurant for food items.

1.2 Scope
1 The system aims to provide secure login to each customer. 2 To Reserve the room customer needs to fill required information. 3 After reserving the room each customer will be given a Customer_ID for reference. 4 Guest search facility is provided. Some benefits and goals of this software are as follows No Paper Work Required Time Efficient Cost Efficient Automatic data validation User friendly environment

4|Page

 Data security and reliability Fast data insertion & retrieval Easy performance check

1.3 Definitions, Acronyms, and Abbreviations.

Customer-id:-An Identification Provided to the user For Opening the Package including User name and password SRS-Software Requirement Specification

1.4 References
1. Care2x.org(www.care2x.org/billing_generic/srscare.htm# 2.1%20User%20Characteristics) 2. http://www.anandsystems.com/hotel_software/hospitali ty_front_desk_software.htm
3. WWW.TGMC.COM

1.5 Overview
The Hotel Management is an independent of the manual system. It is for an online registration process, which should be capable of monitoring the details of booking the rooms and registering by the user. 2. The Overall Description Hotel Management System is an ideal software solution that can be used at hotels, , inns, resorts, lodges, and hostel. Hotel Management System is a comprehensive software suite consisting of integrated modules for various aspects of hotel management. The software is often referred to as Property Management System in the Hotel industry. This system includes all the features required in a Hotel Management Software, Hotel Reservation Software, Hotel Reception
5|Page

Software (Front Office), Accounting, Hotel Point of Sales (Restaurant, Bar, Room Service, House Keeping or any other outlet), Inventory Management System and Hotel accounting software. Our hotel management software is developed for Microsoft Windows operating system using latest software developing techniques. It emphasizes the highest level of individual guest services through our comprehensive features seamlessly integrating rooms, dining with information contained in reservations till back office general ledger.

2.1 Product Perspective

The Hotel management software is fully independent product. Our product is not a part of any other system.

2.1.1 System Interfaces

Not applicable

2.1.2 User Interfaces

We have user interfaces. Users will be categorized as;

Administrator Interfaces Staff Interfaces

Interfaces for Administrator

List of interfaces are listed as bellow

Account View

In this view user will add, remove new staff in the system. In administrator view, administrator will confirm newly added department. Administrator will be able to access all information about hotel staff, customers and managed them.
6|Page

2.1.3 Hardware Interfaces

No specific hardware is required.

2.1.4 Software Interfaces

No software interface.

2.1.5 Communications Interfaces

Client on internet will be using HTTP protocol. Client on intranet will be using TCP/IP protocol.

2.1.6 Memory Constraints

The software shall be able to operate on a system with 128Mb of memory.

2.1.7 Operations
Online user registration using user name and password. To check the availability of room and customer. Informations for hotel staff. Hotel manager to check account details . Backup to software and customer details .

2.1.8 Site Adaptation Requirements

Not applicable

2.2 Product Functions

Registration screen: Used to register the user Availability and status: Checking the availability rooms for users.
7|Page

Guest search: Searching for a particular guest. Report generation: Manager point of view.

2.3 User Characteristics

Every user should be comfortable of working with the computer. User must have knowledge of English too.

2.4 Constraints
GUI is in English only. Every user has to register. Login ID and Password used for user Authentication. An advance of 500Rs/- is required to book a room.

2.5 Assumptions and Dependencies

1 .We are assuming that This System is developed for windows Operating system only. 2. This system is fully independent. Not applicable

2.6 Apportioning of Requirements.

3. Specific Requirements

3.1 External Interfaces

Not applicable

3.2 Functions
The major functions, which the Hotel Management System will perform are: Registering new user by collecting user information. Log-in for subscription to enter into the system.
8|Page

 This permits the user to access their user details and book the rooms according to specified procedure. The facilities include Review the Room information by user-id and password. View the information. Book the room on the availability procedure.

3.3 Performance Requirements

Hotel management should be provided with some system where the customers details can be maintained and can store as a database.This system should be reliable and can be easily transfer from one system to another when required.

3.4 Logical Database Requirements

User Database The user database shall be stored in a text file; passwords stored shall be encrypted. The user database will be called upon when a user logs on. The information will only be able to be changed by an Administrator user. There will be two types of user stored: Administrator and receptionist. Each type will have corresponding entries including the full name of the user, the user name of the user, the password of the user, and the access level of the user. Customer Database The customer database shall be stored in an encrypted text file. It will store the records of the customer. The database shall be fully accessible by an administrator user and partial accessible by a receptionist user.
9|Page

3.5 Design Constraints

Not applicable

3.5.1 Standards Compliance

Not applicable

3.6 Software System Attributes

The interface designed for the system is designed for the use of the front desk receptionist only.

3.6.1 Reliability
-Stable encryption scheme Stable database access scheme Stable core system

3.6.2 Availability
System can be available 365 days .Because system can be an automated process, so it can stay open for 24 hours a day.

3.6.3 Security
Administrator will give the privilege to the user according to their need. Only registered users have the permissions to go through the site for internal details. User name Password is used to authenticate the user.

10 | P a g e

3.6.4 Maintainability
This software is in the form of small sub-systems so it is to maintain sub-system independently.

3.6.5 Portability
This software is only applicable to windows.

3.7 Organizing the Specific Requirements

Not applicable

3.7.1 System Mode

Not applicable

3.7.2 User Class

Not applicable

3.7.3 Objects
Not applicable

3.7.4 Feature
Not applicable

3.7.5 Stimulus

Not applicable

3.7.6 Response Not applicable

11 | P a g e

3.7.7 Functional Hierarchy

Fig 1: functional heierarchy

3.8 Additional Comments

Not applicable

4. Change Management Process

Not applicable
12 | P a g e

5.Document Approvals
Not applicable

6. Supporting Information
Not applicable

3.Design 3.1 Data base Design ER Diagram

WORKS FOR M 1

Employee EID ENAME DID Salary Designation ADDRESS

DEPARTMENT DID DNAME MGRNO

1 1

MANAGES M

N M CONSUMES N SERVES FOR

CUSTOMER FOOD ITEM NO ITEM NAME PRICE QUANTITY CID CNAME ROOM NO ADDRESS

1 N

OCCUPY

CONTAINS

ROOM RNO RTYPE AVAILABILITY

BILL CID CHECK-IN CHECK-OUT BNO TOTAL AMT

CONTAINS

Fig 2:ER diagram 13 | P a g e

3.2 DFD
Customer info Employee info

date

STAFF

HOTEL MANAGEMENT SYSTEM

report

Room infio

Customer info

Staff infro

Fig 3:level 0

14 | P a g e

DFD FOR GENERATING BILL

DATABASE

STAFF

READ ROOM NO

CHECK FOR CHECK OUT OF CUSTOMER

CLOSE DATABASE

COMPUTE BILL

CASH CUSTOMER

Fig 4:bill

15 | P a g e

DFD FOR CHECK OUT OF THE CUSTOMER

CUSTOMER SCAN THE CUSTOMER ROOM NO

DATABASE

GET DETAILS OF CUSTOMER

GENERATE BILL

UPDATE

Fig 5:check out

16 | P a g e

Display DETAILS OF AVAILABLE ROOMS customer

DATABASE

SELECT ROOM TYPE

Assigning a room

Fig 6:check in

17 | P a g e

DFD FOR FOOD ORDER

CUSTOMER

READ MENU

SELECT ITEM

PLACE ORDER

Fig 7: food order

18 | P a g e

GENERATING NEW ROOM no CUSTOMER

Display form

FILE
process

Update table

Get details

Customer document

update

Open room

fig 8:new room

19 | P a g e

3.3 flow chart

START

CUSTOMER

NO YES

REQUEST

BOOKING

NO CHECK-IN

ROOM

CHECKOUT

BILL

END

Fig 9:flow chart

20 | P a g e

4. BIBILOGRAPHY 1. Ian Sommerville Software engineering 8th edition Pearsons education publication 2007. 2. www.wikipedia.com

21 | P a g e