Hotel Management System
SWE 626 Team 2
Hotel Management System
Software Requirements Specification
Document
Prepared by
Team 1
Version: (1.1) Date: (02/11/2002)
Table of Contents
1 Introduction 3
1.1 Purpose 3
1.2 Scope 3
1.3 Definitions, Acronyms, and Abbreviations. 4
1.4 Overview 4
2 The Overall Description 4
2.1 Product Perspective 4
2.1.2 Software Interfaces 4
2.2 Product Functions 4
2.3 User Characteristics 5
2.4 Apportioning of Requirements 5
2.5 Assumptions and Dependencies 5
3 Specific Requirements 6
3.1 External Interfaces 6
3.1.1 User Interfaces 6
3.1.2 Software Interfaces 6
3.1.3 Hardware Interfaces 6
3.1.4 Communication Interfaces 7
3.2 Functional Requirements 7
3.3 Nonfunctional Requirements 9
3.3.1 Performance Requirements 9
3.3.2 Logical Database Requirements 9
3.3.3 Design Constraints 10
3.3.4 Standards Compliance 10
3.3.5 Reliability 10
3.3.6 Availability 10
3.3.7 Security 10
3.3.8 Maintainability 10
3.3.9 Portability 10
4 Change Management Process 11
5 Document Approvals 11
5.1 Team One Approval 11
5.2 Team Two Approval 11
6 Supporting Information 11
1 Introduction
The following subsections of the Software Requirements Specifications (SRS) document provide an overview of the entire SRS.
1.1 Purpose
The Software Requirements Specification (SRS) will provide a detailed description of the requirements for the Hotel Management System (HMS). This SRS will allow for a complete understanding of what is to be expected of the HMS to be constructed. The clear understanding of the HMS 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 HMS can be designed, constructed, and finally tested.
This SRS will be used by the software engineers constructing the
Hotel Management System
Software Requirements Specification
Document
Prepared by
Team 1
Version: (1.1) Date: (02/11/2002)
Table of Contents
1 Introduction 3
1.1 Purpose 3
1.2 Scope 3
1.3 Definitions, Acronyms, and Abbreviations. 4
1.4 Overview 4
2 The Overall Description 4
2.1 Product Perspective 4
2.1.2 Software Interfaces 4
2.2 Product Functions 4
2.3 User Characteristics 5
2.4 Apportioning of Requirements 5
2.5 Assumptions and Dependencies 5
3 Specific Requirements 6
3.1 External Interfaces 6
3.1.1 User Interfaces 6
3.1.2 Software Interfaces 6
3.1.3 Hardware Interfaces 6
3.1.4 Communication Interfaces 7
3.2 Functional Requirements 7
3.3 Nonfunctional Requirements 9
3.3.1 Performance Requirements 9
3.3.2 Logical Database Requirements 9
3.3.3 Design Constraints 10
3.3.4 Standards Compliance 10
3.3.5 Reliability 10
3.3.6 Availability 10
3.3.7 Security 10
3.3.8 Maintainability 10
3.3.9 Portability 10
4 Change Management Process 11
5 Document Approvals 11
5.1 Team One Approval 11
5.2 Team Two Approval 11
6 Supporting Information 11
1 Introduction
The following subsections of the Software Requirements Specifications (SRS) document provide an overview of the entire SRS.
1.1 Purpose
The Software Requirements Specification (SRS) will provide a detailed description of the requirements for the Hotel Management System (HMS). This SRS will allow for a complete understanding of what is to be expected of the HMS to be constructed. The clear understanding of the HMS 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 HMS can be designed, constructed, and finally tested.
This SRS will be used by the software engineers constructing the