Detection of Guilty Agents
Hotel Management System
Software Requirements Specification
Document
Table of Contents
1 Introduction 4
1.1 Purpose 4
1.2 Scope 4
1.3 Definitions, Acronyms, and Abbreviations. 5
1.4 Overview 5
2 The Overall Description 5
2.1 Product Perspective 5 2.1.1 Hardware Interfaces 5 2.1.2 Software Interfaces 5
2.2 Product Functions 5
2.3 User Characteristics 6
2.4 Apportioning of Requirements. 6
2.5 Assumptions and Dependencies 6
3 Specific Requirements 7
3.1 External Interfaces 7 3.1.1 User Interfaces 7 3.1.2 Software Interfaces 7 3.1.3 Hardware Interfaces 7 3.1.4 Communication Interfaces 8
3.2 Functional Requirements 8
3.3 Nonfunctional Requirements 100 3.3.1 Performance Requirements 100 3.3.2 Logical Database Requirements 100 3.3.3 Design Constraints 111 3.3.4 Standards Compliance 111 3.3.5 Reliability 111 3.3.6 Availability 111 3.3.7 Security 111 3.3.8 Maintainability 11 3.3.9 Portability 111
4 Change Management Process 122
5 Document Approvals 122
5.1 Approval 122
6 Supporting Information 122
Introduction
The following subsections of the Software Requirements Specifications (SRS) document provide an overview of the entire SRS.
1 Purpose
The Software Requirements Specification (SRS) will provide a detailed description of the requirements for the Hotel Management System (HMS).
This SRS will be used by the software engineers constructing the HMS and the hotel end users. The software engineers will use the SRS to fully understand the expectations of this HMS 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
Software Requirements Specification
Document
Table of Contents
1 Introduction 4
1.1 Purpose 4
1.2 Scope 4
1.3 Definitions, Acronyms, and Abbreviations. 5
1.4 Overview 5
2 The Overall Description 5
2.1 Product Perspective 5 2.1.1 Hardware Interfaces 5 2.1.2 Software Interfaces 5
2.2 Product Functions 5
2.3 User Characteristics 6
2.4 Apportioning of Requirements. 6
2.5 Assumptions and Dependencies 6
3 Specific Requirements 7
3.1 External Interfaces 7 3.1.1 User Interfaces 7 3.1.2 Software Interfaces 7 3.1.3 Hardware Interfaces 7 3.1.4 Communication Interfaces 8
3.2 Functional Requirements 8
3.3 Nonfunctional Requirements 100 3.3.1 Performance Requirements 100 3.3.2 Logical Database Requirements 100 3.3.3 Design Constraints 111 3.3.4 Standards Compliance 111 3.3.5 Reliability 111 3.3.6 Availability 111 3.3.7 Security 111 3.3.8 Maintainability 11 3.3.9 Portability 111
4 Change Management Process 122
5 Document Approvals 122
5.1 Approval 122
6 Supporting Information 122
Introduction
The following subsections of the Software Requirements Specifications (SRS) document provide an overview of the entire SRS.
1 Purpose
The Software Requirements Specification (SRS) will provide a detailed description of the requirements for the Hotel Management System (HMS).
This SRS will be used by the software engineers constructing the HMS and the hotel end users. The software engineers will use the SRS to fully understand the expectations of this HMS 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