Software requirements specification
Lua error in package.lua at line 80: module 'strict' not found. A software requirements specification (SRS) is a description of a software system to be developed. It lays out functional and non-functional requirements, and may include a set of use cases that describe user interactions that the software must provide.
Software requirements specification establishes the basis for an agreement between customers and contractors or suppliers (in market-driven projects, these roles may be played by the marketing and development divisions) on what the software product is to do as well as what it is not expected to do. Software requirements specification permits a rigorous assessment of requirements before design can begin and reduces later redesign. It should also provide a realistic basis for estimating product costs, risks, and schedules.[1]
The software requirements specification document enlists enough and necessary requirements that are required for the project development.[2] To derive the requirements we need to have clear and thorough understanding of the products to be developed or being developed. This is achieved and refined with detailed and continuous communications with the project team and customer till the completion of the software.
The SRS may be one of a contract deliverable Data Item Descriptions[3] or have other forms of organizationally-mandated content.
Contents
Structure
An example organization of an SRS is as follows:[4]
- Introduction
- Purpose
- Definitions
- System overview
- References
- Overall description
- Product perspective
- System Interfaces
- User Interfaces
- Hardware interfaces
- Software interfaces
- Communication Interfaces
- Memory Constraints
- Operations
- Site Adaptation Requirements
- Product functions
- User characteristics
- Constraints, assumptions and dependencies
- Product perspective
- Specific requirements
- External interface requirements
- Functional requirements
- Performance requirements
- Design constraints
- Standards Compliance
- Logical database requirement
- Software System attributes
- Reliability
- Availability
- Security
- Maintainability
- Portability
- Other requirements
Write specifications to be readable and reviewable
Lua error in package.lua at line 80: module 'strict' not found. Stakeholders should provide feedback. Therefore, technical writers and other contributors should write a specification in such a way that facilitates reading and review.
Some of the questions to ask about readability is:
- Does the specification describe, at a high-level, the scope of the work?
- Does the formatting help a reader easily navigate the specification?
- Does the formatting help a reader easily understand primary versus secondary use cases?
- Does the specification link to related features?
- Does the specification list questions that still must be addressed?
See also
- Concept of operations
- Requirements engineering
- Software Engineering Body of Knowledge (SWEBOK)
- Design specification
- Specification (technical standard)
- Formal specification
References
External links
- Lua error in package.lua at line 80: module 'strict' not found.
- Lua error in package.lua at line 80: module 'strict' not found.
- Lua error in package.lua at line 80: module 'strict' not found.
- Lua error in package.lua at line 80: module 'strict' not found.("This standard replaces IEEE 830-1998, IEEE 1233-1998, IEEE 1362-1998 - http://standards.ieee.org/findstds/standard/29148-2011.html")
- Lua error in package.lua at line 80: module 'strict' not found.
- Lua error in package.lua at line 80: module 'strict' not found.
- Lua error in package.lua at line 80: module 'strict' not found.
- Software Requirements Specification Writing Service
