Srs Hotel Management System
Hotel Automation Software [ Software Requirements Specification ]
Version <1.0>
Table of Contents
1. Introduction 3 1.1 Purpose 3 1.2 Scope 3 1.3 Definitions, Acronyms and Abbreviations 3 1.4 References 3 1.5 Overview 4 2. Overall Description 4 2.1 Product Perspective 4 2.2 Product Functions 4 2.3 User Characteristics 5 3. Specific Requirements 5 3.1 External Interface 5 3.1.1. User Interface 5 3.1.2. Software Interface 5 3.1.3. Hardware Interface 5 3.1.4. Communication Interface 6 3.2 Functional Requirement 6 3.3 Purchased Components 7
Introduction The following subsections of the Software Requirements Specifications (SRS) document provide an overview of the entire SRS.
Purpose
The Software Requirements Specification (SRS) will provide a detailed description of the requirements for the Hotel Automation Software (HAS). This SRS will allow for a complete understanding of what is to be expected of the HAS to be constructed. 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. This SRS will provide the foundation for the project. From this SRS, the HAS can be designed, constructed, and finally tested. This SRS will be used by the software engineers constructing the HAS and the hotel end users. The software engineers will use the SRS to fully understand the expectations of this HAS to construct the appropriate software. 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. 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.
Scope
The software product to be produced is a Hotel Automation Software which will automate the major hotel
Version <1.0>
Table of Contents
1. Introduction 3 1.1 Purpose 3 1.2 Scope 3 1.3 Definitions, Acronyms and Abbreviations 3 1.4 References 3 1.5 Overview 4 2. Overall Description 4 2.1 Product Perspective 4 2.2 Product Functions 4 2.3 User Characteristics 5 3. Specific Requirements 5 3.1 External Interface 5 3.1.1. User Interface 5 3.1.2. Software Interface 5 3.1.3. Hardware Interface 5 3.1.4. Communication Interface 6 3.2 Functional Requirement 6 3.3 Purchased Components 7
Introduction The following subsections of the Software Requirements Specifications (SRS) document provide an overview of the entire SRS.
Purpose
The Software Requirements Specification (SRS) will provide a detailed description of the requirements for the Hotel Automation Software (HAS). This SRS will allow for a complete understanding of what is to be expected of the HAS to be constructed. 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. This SRS will provide the foundation for the project. From this SRS, the HAS can be designed, constructed, and finally tested. This SRS will be used by the software engineers constructing the HAS and the hotel end users. The software engineers will use the SRS to fully understand the expectations of this HAS to construct the appropriate software. 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. 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.
Scope
The software product to be produced is a Hotel Automation Software which will automate the major hotel
References: [2] The principal source of textbook material is “Fundamentals of Software Engineering” by Rajib Mall (PHI 2009).