What are common examiner traps in Software Requirements Specification?

Confusing 'Goals of Implementation' (valid contextual objective in SRS) with 'Algorithms for Software Implementation' (invalid design detail). Failing to separate requirements engineering artifacts from low-level design artifacts.

Software Requirements Specification

1 Qs · 2011 · 1 marks · 0.1 marks/paperStandard yield

Take topic test

In GATE Software Engineering, the Software Requirements Specification (SRS) topic tests conceptual understanding of requirement engineering principles. The focus is on the contents… Guide

Type

GATE CSE 2011Q10MCQ1 markEasyWhich one of the following is NOT desired in a good Software Requirement Specifications (SRS) document?

Topic guide

What does GATE test in Software Requirements Specification?

In GATE Software Engineering, the Software Requirements Specification (SRS) topic tests conceptual understanding of requirement engineering principles. The focus is on the contents, scope, and characteristics of an SRS document, specifically emphasizing that an SRS defines 'what' the system should do rather than 'how' it is implemented.

Core concepts

Distinction between 'what' (specification) vs 'how' (design/implementation)
Functional and Non-Functional Requirements
Goals of Implementation and System Constraints
Design Independence of SRS Documents
Undesirable contents in SRS (e.g., algorithms, internal data structures, hardware-specific code logic)

Recurring question patterns

Contents and Characteristics of SRS
rare · MCQ · 1 marks · 2011
Questions evaluate whether a candidate can distinguish between what belongs in an SRS document (functional/non-functional requirements, constraints, goals) versus implementation/design details (algorithms, data structures, coding specifics).

Examiner traps in Software Requirements Specification

Confusing 'Goals of Implementation' (valid contextual objective in SRS) with 'Algorithms for Software Implementation' (invalid design detail).
Failing to separate requirements engineering artifacts from low-level design artifacts.

How questions are asked

Identifying NOT/incorrect characteristics or contents of an SRS document

Paper trends

Software Engineering (including SRS) has been sparsely asked or removed/deprioritized in recent GATE CS syllabi, appearing as direct conceptual 1-mark MCQs when included.
2011

Difficulty notes

Easy: Direct recall or identification of what belongs or does not belong in an SRS document. Medium/Hard (if framed): Identifying subtle edge cases in non-functional constraints vs architectural decisions or IEEE 830 quality attributes (e.g., unambiguous, verifiable, modifiable, traceable).