Question
A software requirements specification (SRS) document should avoid discussing which one of the following?
Official answer and solution
- Official answer
- C
- From
- Official GATE 2015 answer key
Solution
Recall the fundamental distinction between requirement specification and design/implementation in software engineering.
The Software Requirements Specification (SRS) documents what the system must do, not how it is designed or implemented.
An SRS typically specifies:
- Functional and non-functional requirements
- External interfaces (user interface characteristics, hardware/software interfaces)
- System constraints and performance parameters
An SRS should explicitly avoid design specifications (such as choice of algorithms, internal data structures, module decomposition, and database schema design), as premature design constraints unnecessarily restrict the system designers.
C
Assuming non-functional requirements or user interface constraints should be omitted from an SRS.
The answer is the one in the official GATE answer key. The solution is this site's own explanation.
Source
- Paper
- GATE 2015 Computer Science and Information Technology (CS) Session 2
- Question
- 14 of 65, printed as CS Q.4
- Section
- Computer Science and Information Technology
This question is from a part of the syllabus that is no longer in GATE CS. It is kept because it was in the paper.
Report an error in this question
GATE questions are the work of the organising institutes. This site is independent and is not affiliated with them.