What should not be included in an SRS regarding the design of software?
Understand the Problem
The question is asking about what aspects should be excluded from a Software Requirements Specification (SRS) document, particularly in relation to software design. It focuses on understanding the responsibilities and content that are relevant or irrelevant to an SRS.
Answer
Design specifications
Design specifications should not be included in the SRS (Software Requirements Specification). These are intended for the SDD (Software Design Description).
Answer for screen readers
Design specifications should not be included in the SRS (Software Requirements Specification). These are intended for the SDD (Software Design Description).
More Information
A Software Requirements Specification (SRS) document focuses on the 'what' aspect by defining the software's behavior and requirements, while design specifications detail the 'how' by specifying its implementation approach. Including design details in the SRS can lead to confusion between what the software is supposed to do and how it will be constructed.
Tips
A common mistake is mixing requirements with design in the SRS, which can complicate understanding and implementation. It's essential to clearly separate what the software needs to do (SRS) from how it will be done (SDD).
Sources
- Is design specification discussed in SRS document? - stackoverflow.com
AI-generated content may contain errors. Please verify critical information
