[ Project ]
Software Requirements Specification
June 27, 2001
[ Organization Name ]
[ Paste Your Organization’s Logo Here ]
|Version |Primary Author(s) |Description of Version |Date Completed | |Draft Type and |Full Name |Information about the revision. This table does not need to be |00/00/00 | |Number | |filled in whenever a document is touched, only when the version| | | | |is being upgraded. | | | | |CxPattern_RevisionHistory provides details on CxOne’s | | | | |recommended way to handle document revisions. | |
The paragraphs written in the “Comment” style are for the benefit of the person writing the document and should be removed before the document is finalized.
This template can be used to create Software Requirements Specifications that conform to IEEE Standard 830-1993.
An SRS is a tool for capturing requirements on a project; it is the epitome of “plain language requirements”. Although an SRS is designed to stand on its own, most projects will employ additional tools for capturing requirements. An SRS may be ancillary or unnecessary on many projects, but a partial or lightweight one may be quite useful even if other techniques are being used to capture the bulk of the requirements.
Consider using an SRS when:
• Modeling techniques need to be augmented
• Plain language is the best mechanism for capturing system behavior
• Requirements must be traceable
• Required by regulations
See CxGuide_CxOneArtifact for details on how to utilize the advanced features of CxOne artifact templates.
1.3 Definitions, Acronyms, and Abbreviations
2 Overall Description
2.1 Product Perspective
2.1.1 System Interfaces
2.1.2 User Interfaces
2.1.3 Hardware Interfaces
2.1.4 Software Interfaces
2.1.5 Communications Interfaces
2.1.6 Memory Constraints
2.1.8 Site Adaptation Requirements
2.2 Product Functions
2.3 User Characteristics
2.5 Assumptions and Dependencies
2.6 Apportioning of Requirements
3 Specific Requirements
3.1 External Interface Requirements
3.1.1 User Interfaces
3.1.2 Hardware Interfaces
3.1.3 Software Interfaces
3.1.4 Communications Interfaces
3.2 Software Product Features
3.2.1 Feature 1
Associated Functional Requirements
3.3 Performance Requirements
3.4 Design Constraints
3.5 Software System Attributes
3.6 Logical Database Requirements
3.7 Other Requirements
This section should provide an overview of the entire document.
Describe the purpose of this specification and its intended audience.
Identify the software product(s) to be produced by name. Explain what the products will and will not do. Describe how the software will be used, and identify relevant benefits, objectives, and goals.
3 Definitions, Acronyms, and Abbreviations
Define all terms, acronyms, and abbreviations used in this document.
List all the documents and other materials referenced in this document. This section is like the bibliography in a published book.
Describe the content and organization of the rest of this document.
Please join StudyMode to read the full document