Essay on Memorable Day in Life
Software Requirements Specification
Contents
1. Introduction. 2
1.1. Purpose. 2
1.2. Document Conventions. 3
1.3. Intended Audience and Reading Suggestions. 3
2. Overall Description. 4
2.1 Product Perspective. 4
2.2 Product Features. 5
2.3 User Classes and Characteristics. 6
2.4 Operating Environment. 6
2.5 Design and Implementation Constraints. 6
2.6 User Documentation. 6
2.7 Assumptions and Dependencies. 7
3. System Features. 8
3.1. Database – Storage. 8
3.2. Functional Requirements. 8
3.2.1 Interface Requirements. 8
3.2.1.1 User Interfaces. 9
4. Non Functional Requirements. 10
4.1. User Interfaces. 10
4.2. Hardware Interfaces. 10
4.3. Software Interfaces. 11
4.4. Communications Interfaces. 11
5. Other Nonfunctional Requirements. 11
5.1. Performance Requirements. 11
5.2. Safety Requirements. 11
5.3. Security Requirements. 12
5.4. Software Quality Attributes. 12
5.5 Hardware Constraints. 12
5.6 Software Constraints. 12
5.7 Design Constraints. 12
1. Introduction
1.1. Purpose
The main objective of this document is to illustrate the requirements of the project Library Management system. The document gives the detailed description of the both functional and non functional requirements proposed by the client. The document is developed after a number of consultations with the client and considering the complete requirement specifications of the given Project. The final product of the team will be meeting the requirements of this document.
1.2. Document Conventions The following are the list of conventions and acronyms used in this document and the project as well:
Administrator: A login id representing a user with user administration privileges to the software
User: A general login id assigned to most
Contents
1. Introduction. 2
1.1. Purpose. 2
1.2. Document Conventions. 3
1.3. Intended Audience and Reading Suggestions. 3
2. Overall Description. 4
2.1 Product Perspective. 4
2.2 Product Features. 5
2.3 User Classes and Characteristics. 6
2.4 Operating Environment. 6
2.5 Design and Implementation Constraints. 6
2.6 User Documentation. 6
2.7 Assumptions and Dependencies. 7
3. System Features. 8
3.1. Database – Storage. 8
3.2. Functional Requirements. 8
3.2.1 Interface Requirements. 8
3.2.1.1 User Interfaces. 9
4. Non Functional Requirements. 10
4.1. User Interfaces. 10
4.2. Hardware Interfaces. 10
4.3. Software Interfaces. 11
4.4. Communications Interfaces. 11
5. Other Nonfunctional Requirements. 11
5.1. Performance Requirements. 11
5.2. Safety Requirements. 11
5.3. Security Requirements. 12
5.4. Software Quality Attributes. 12
5.5 Hardware Constraints. 12
5.6 Software Constraints. 12
5.7 Design Constraints. 12
1. Introduction
1.1. Purpose
The main objective of this document is to illustrate the requirements of the project Library Management system. The document gives the detailed description of the both functional and non functional requirements proposed by the client. The document is developed after a number of consultations with the client and considering the complete requirement specifications of the given Project. The final product of the team will be meeting the requirements of this document.
1.2. Document Conventions The following are the list of conventions and acronyms used in this document and the project as well:
Administrator: A login id representing a user with user administration privileges to the software
User: A general login id assigned to most