You are on page 1of 7

Hotel Automation Software Software Requirements Specification

Version <1.0>

3 User Characteristics Specific Requirements 3.Table of Contents 1.3.1 Purpose 1.2 Functional Requirement 3.4. Hardware Interface 3. Communication Interface 3.1 Product Perspective Purchased Components 3 3 3 3 3 4 4 4 4 5 5 5 5 5 5 6 6 7 2.1. Introduction 1.1 External Interface 3.2 Scope 1.4 References 1. Software Interface 3.3 Definitions. Acronyms and Abbreviations 1.1.5 Overview Overall Description 2.1. User Interface 3. 3. .2 Product Functions 2.2.

Acronyms and Abbreviations SRS – Software Requirements Specification HAS – Hotel Management System Subjective satisfaction – The overall satisfaction of the system End users – The people who will be actually using the system 1. If it is not to their expectations the end users can specify how it is not to their liking and the software engineers will change the SRS to fit the end users’ needs. 1.” 2001 edition. . The hotel end users will be able to use this SRS as a “test” to see if the software engineers will be constructing the system to their expectations.1 Purpose The Software Requirements Specification (SRS) will provide a detailed description of the requirements for the Hotel Automation Software (HAS). From this SRS. constructed. This SRS will allow for a complete understanding of what is to be expected of the HAS to be constructed. The first subsystem is a Reservation System to keep track of reservations and room availability. The managers have access to the other systems as well. and finally tested. The software engineers will use the SRS to fully understand the expectations of this HAS to construct the appropriate software. This SRS will provide the foundation for the project. 1. Introduction The following subsections of the Software Requirements Specifications (SRS) document provide an overview of the entire SRS. catering service representative and hotel managers. The clear understanding of the HAS and its’ functionality will allow for the correct software to be developed for the end user and will be used for the development of the future stages of the project. The second subsystem is the Catering System that charges the current room.1. [2] The principal source of textbook material is “Fundamentals of Software Engineering” by Rajib Mall (PHI 2009). These three subsystems’ functionality will be described in detail in section 2-Overall Description. 1.3 Definitions. The General Management System will be restricted to management users apart. The end users are the booking clerks. There are three end users for the HAS.2 Scope The software product to be produced is a Hotel Automation Software which will automate the major hotel operations.4 References [1] The applicable IEEE standards are published in “IEEE Standards Collection. This SRS will be used by the software engineers constructing the HAS and the hotel end users. the HAS can be designed. The third subsystem is a Management System which caters for General Management Services and allows modification of subsystem information. The first two have access to the Reservation and catering System respectively.

which are defined in section 3.2 Product Functions Login  Allows users with different profiles to login to the system and perform their desired functions. deletion and modification of information on rooms and rates. 2.5 Overview The SRS is organized into two main sections. The Overall Description will describe the requirements of the HAS from a general high level perspective. The Overall Description This section describes the general factors that affect the product and its requirements. It is totally self contained.3 User Characteristics . menu items and prices. Reservation  Allows for typing in customer information  Has a default room rate that is adjustable  Includes a description field for the changed rate  When a customer checks in.1. The Specific Requirements section will describe in detail the requirements of the system. The HAS will be placed on PC’s throughout the hotel. Instead it provides a background for those requirements. and makes them easier to understand. adds an extra night to amount owed and provides a report  Records that room is vacant  Records payment  Allows for space to write customer’s feedback Catering  Tracks all meals purchased  Charges the current room as necessary General Management Services  Querying room occupancy statistics  Allows addition. The first is The Overall Description and the second is the Specific Requirements. 2. the room number will be changed to occupied in the database  Ability to modify a reservation  When no rooms are available and a customer would like to extend their reservation their information will be placed in a database and when there are rooms available the first customer on the list will have the room  When a customer checks out the amount owed is displayed  If the internal clock states that is a customer’s time to have checked out and customer has not checked out. user profiles  Registration of frequent customers 2. This section does not state specific requirements. 2.1 Product Perspective The HAS is an independent stand–alone system.

This includes the following:  Keyboard  Mouse  Monitor  Printer 3. revise room tariffs Administer Meals Create. Check-in Check-in customer (with or without a reservation). and testers to test that the system satisfies those requirements.2 Software Interfaces The system shall interface with an Oracle11g database. address. whether or not the room is guaranteed.1 External Interfaces The Hotel Management System will use the standard input/output devices for a personal computer. and use case descriptions. The room database will include the room numbers and if they are vacant or occupied. default room rate(may be changed). . phone number. The meal menu database will contain details of various food items available and corresponding rates. generate bill Payment Accept payment for room and food Catering Add meals consumed. contact number etc along with a identification number. Modify room stay Checkout Checkout customer. confirmation number. These databases include hotel rooms. customers details. Specific Requirements This section contains all the software requirements at a level of detail. expected check in date and time. Catering service representative who will use it to update meal records of customers and finally managers who will be administrators and will carry out various General Managerial Services like revision of room/meal rates etc. assigned room. actual check in date and time.There are essentially three profiles of users for the HAS: The booking clerk who will use it for reservation of customer related functions. 3. meal menu. modify. number of occupants. amount owed by customer. These can be modified by the end users. automatic cancellation date. frequent customer.1.1 User Interfaces The User Interface Screens are described in table 1. Table 1: Hotel Management User Interface Screens Screen Name Description Login Log into the system as a Booking Clerk or Catering Service Manager or Manager Enquiry Check room Availability. last name. credit card number. is sufficient to enable designers to design a system to satisfy those requirements. 3.1. Tariffs. The customers details database will contain all the information of the customer such as first name. expected check out date and time. and delete meal items and prices Frequent customers Register Frequent customers/update details 3. use cases. The Frequent customer database will include all customer personal like name. that when combined with the system context diagram.3 Hardware Interfaces The system shall run on a Microsoft Windows based system. generate meal charges Administer Rooms Query Room occupancy statistics. 3. and abbreviated customer feedback.1.

3. if password is valid and username profile = Booking Clerk R.4. the reservation will be automatically cancelled if payment is not made before checkin time+1 hour. checkin date and time. Output: Allotted Room no. Processing: Calculate total amount due from customer and update in customer database. approx. Login.1 Login Input: User name and password Processing: Password Validation Output: Window corresponding to Next function is opened if password is valid. Next Function: R. Next Function: R. Processing: Allocate a room no.2.1.2 Check Tariff Input: Type of room Processing: Query room database and return queried rooms’ tariff Output: Current applicable tariff Next Function: R. Checkout Input: Token No.4. .2.2 R. duration of stay.3. This includes (a) Room Tariff (b) Catering Charges (c) Taxes. Check Availability Input: Type of room Processing: Query room database and return available rooms Output: Room nos. If password is invalid error message is displayed and user is asked to re-enter the password/user name. Allot Unique TOKEN No. R. R. Reservation. checkin/checkout of customers.2. booking of rooms. if password is invalid R. Next Function: R.2. R. Checkin Input: Customer details.3. Update room occupancy status as vacant.2 Functional Requirements Functional requirements define the fundamental actions that system must perform.2.1. if password is valid and username profile = Manager R. type of room.2. Food. For further details. for customer and update in customer database. refer to the use cases. Reservation Description This function would cater for all day to day booking related requirements like to querying about availability of rooms. and Management.4 Communication Interfaces The system shall be a standalone product that does not require any communication interfaces. if available.3. and update room occupancy status as occupied for the duration of stay.2.3 R.1. If rooms are not available apology message will be displayed.2. if password is valid and username profile = Catering Service Representative R. and Token no..2.5 Constraint: In case of advance booking. The functional requirements for the system are divided into four main categories.

3. This function can be invoked only if logged in as manager profile./Room type/All. R.4.3 Purchased Components It is presumed that the PCs on which the software is targeted will be running on Windows Operating System hence the same will not be provided.2.2. Next Function: R. Output: Acknowledgement. Up/Down.: (b)Room type: (c) All: ∑ ∑ Specified duration: (a) For month. R. Output: Average occupancy rate in days R./Room type/All. Add/Delete/Modify food item/rates Input: Item Description. The database software (Oracle 11g) will be purchased and necessary licensing documents will be provided. Management This function allows the manager to carry out General Management Services. rate. R. payment mode. Processing: Update catering details to customer record with date and time and update catering charges to customer dues. duration = to date – from date. token no. month) Processing: Calculate the occupancy rate as follows: (a) Room No. Payment Input: Token No. Processing: Add/Delete/Modify food item/rates in food database Output: Display updated menu.3 Revise Room Tariff Input: Room No..1. Output: Generate payment receipt and display pending dues.4. Processing: Update customer dues in customer data base. .3.4. R.5 R. Catering Input: Quantity and type of food.5. Register Frequent customers Input: Customer details Processing: Add customer to Frequent customer database. Output: Identity Number. duration = 30 days (b)For from date-to date.Output: Bill indicating total amount due from customer. R.4. amount.4.% Processing: Update room tariff in room database Output: Display updated tariffs. Query Room Occupancy Input: Room No. duration (from date-to date.2.4.