This action might not be possible to undo. Are you sure you want to continue?
1.2 Product Functions 2.3.1 External Interface 3.1. Hardware Interface 18.104.22.168 Purchased Components 3 3 3 3 3 4 4 4 4 5 5 5 5 5 5 6 6 7 2. Software Interface 3. Acronyms and Abbreviations 1. .4 References 1.5 Overview Overall Description 2.1 Purpose 1.2 Functional Requirement 3. Introduction 1. 22.214.171.124 User Characteristics Specific Requirements 3. Communication Interface 3.2 Scope 1.Table of Contents 1.3 Definitions. User Interface 3.2.1 Product Perspective 2.
The managers have access to the other systems as well.  The principal source of textbook material is “Fundamentals of Software Engineering” by Rajib Mall (PHI 2009). 1. From this SRS. The first subsystem is a Reservation System to keep track of reservations and room availability. The end users are the booking clerks. . 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. catering service representative and hotel managers. 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. Introduction The following subsections of the Software Requirements Specifications (SRS) document provide an overview of the entire SRS. The first two have access to the Reservation and catering System respectively. 1. constructed. This SRS will allow for a complete understanding of what is to be expected of the HAS to be constructed. the HAS can be designed. The General Management System will be restricted to management users apart.1 Purpose The Software Requirements Specification (SRS) will provide a detailed description of the requirements for the Hotel Automation Software (HAS).1. and finally tested. 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.2 Scope The software product to be produced is a Hotel Automation Software which will automate the major hotel operations. The software engineers will use the SRS to fully understand the expectations of this HAS to construct the appropriate software. The third subsystem is a Management System which caters for General Management Services and allows modification of subsystem information.4 References  The applicable IEEE standards are published in “IEEE Standards Collection. There are three end users for the HAS. 1. This SRS will be used by the software engineers constructing the HAS and the hotel end users.3 Definitions.” 2001 edition. These three subsystems’ functionality will be described in detail in section 2-Overall Description. 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. The second subsystem is the Catering System that charges the current room. This SRS will provide the foundation for the project.
2 Product Functions Login Allows users with different profiles to login to the system and perform their desired functions. The Overall Description This section describes the general factors that affect the product and its requirements. 2. The HAS will be placed on PC’s throughout the hotel. 2. 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. which are defined in section 3. and makes them easier to understand. menu items and prices. It is totally self contained. The first is The Overall Description and the second is the Specific Requirements. user profiles Registration of frequent customers 2. Instead it provides a background for those requirements.1 Product Perspective The HAS is an independent stand–alone system. 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. The Overall Description will describe the requirements of the HAS from a general high level perspective.3 User Characteristics . 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. This section does not state specific requirements. deletion and modification of information on rooms and rates.5 Overview The SRS is organized into two main sections.1. The Specific Requirements section will describe in detail the requirements of the system.
3. credit card number. automatic cancellation date. is sufficient to enable designers to design a system to satisfy those requirements. use cases. The Frequent customer database will include all customer personal like name.2 Software Interfaces The system shall interface with an Oracle11g database. that when combined with the system context diagram. frequent customer. Specific Requirements This section contains all the software requirements at a level of detail.3 Hardware Interfaces The system shall run on a Microsoft Windows based system. and delete meal items and prices Frequent customers Register Frequent customers/update details 3.1 External Interfaces The Hotel Management System will use the standard input/output devices for a personal computer. The meal menu database will contain details of various food items available and corresponding rates. contact number etc along with a identification number. phone number. Tariffs. Modify room stay Checkout Checkout customer.1.There are essentially three profiles of users for the HAS: The booking clerk who will use it for reservation of customer related functions. 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. generate bill Payment Accept payment for room and food Catering Add meals consumed. whether or not the room is guaranteed. actual check in date and time. The room database will include the room numbers and if they are vacant or occupied. assigned room. customers details.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. and testers to test that the system satisfies those requirements. These databases include hotel rooms. revise room tariffs Administer Meals Create. address.1 User Interfaces The User Interface Screens are described in table 1. default room rate(may be changed). generate meal charges Administer Rooms Query Room occupancy statistics. expected check out date and time. 3. amount owed by customer. modify. expected check in date and time. and abbreviated customer feedback. . This includes the following: Keyboard Mouse Monitor Printer 3. last name. confirmation number. 3. The customers details database will contain all the information of the customer such as first name. These can be modified by the end users. number of occupants. meal menu. Check-in Check-in customer (with or without a reservation).1. and use case descriptions.
2.2 R. duration of stay. Output: Allotted Room no. Processing: Allocate a room no. the reservation will be automatically cancelled if payment is not made before checkin time+1 hour. Check Availability Input: Type of room Processing: Query room database and return available rooms Output: Room nos. R.5 Constraint: In case of advance booking. Next Function: R. Processing: Calculate total amount due from customer and update in customer database.3.3. refer to the use cases.2.2 Check Tariff Input: Type of room Processing: Query room database and return queried rooms’ tariff Output: Current applicable tariff Next Function: R. This includes (a) Room Tariff (b) Catering Charges (c) Taxes.3.1. If rooms are not available apology message will be displayed. and Management. booking of rooms. Next Function: R. Login. if password is valid and username profile = Catering Service Representative R.4.1 Login Input: User name and password Processing: Password Validation Output: Window corresponding to Next function is opened if password is valid.2. R. 3.3 R. Update room occupancy status as vacant.. and update room occupancy status as occupied for the duration of stay. Checkout Input: Token No. Checkin Input: Customer details. if password is invalid R.1. Next Function: R.2. Reservation. for customer and update in customer database. checkin date and time.2.2. type of room. R.2 Functional Requirements Functional requirements define the fundamental actions that system must perform. . and Token no.4.1.2. checkin/checkout of customers. if password is valid and username profile = Manager R. Reservation Description This function would cater for all day to day booking related requirements like to querying about availability of rooms. The functional requirements for the system are divided into four main categories. For further details. if available.4 Communication Interfaces The system shall be a standalone product that does not require any communication interfaces. Allot Unique TOKEN No. if password is valid and username profile = Booking Clerk R. approx.2.2. Food. If password is invalid error message is displayed and user is asked to re-enter the password/user name.
5. duration (from date-to date. Add/Delete/Modify food item/rates Input: Item Description.: (b)Room type: (c) All: ∑ ∑ Specified duration: (a) For month.4./Room type/All. Output: Generate payment receipt and display pending dues.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. duration = to date – from date. R.2. Up/Down.1. This function can be invoked only if logged in as manager profile.3.4. Processing: Update catering details to customer record with date and time and update catering charges to customer dues. rate.4.4. R. . Next Function: R. payment mode.2. Output: Acknowledgement. Management This function allows the manager to carry out General Management Services. duration = 30 days (b)For from date-to date. Payment Input: Token No.3 Revise Room Tariff Input: Room No. The database software (Oracle 11g) will be purchased and necessary licensing documents will be provided.% Processing: Update room tariff in room database Output: Display updated tariffs. 3. Output: Identity Number. R.5 R. amount. token no.. Query Room Occupancy Input: Room No. Register Frequent customers Input: Customer details Processing: Add customer to Frequent customer database. Output: Average occupancy rate in days R. Processing: Update customer dues in customer data base. R./Room type/All. Processing: Add/Delete/Modify food item/rates in food database Output: Display updated menu. month) Processing: Calculate the occupancy rate as follows: (a) Room No. R.4.2. Catering Input: Quantity and type of food.4.Output: Bill indicating total amount due from customer.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue listening from where you left off, or restart the preview.