Requirements Engineering Questions and Answers

Q: Which one of the following is NOT desired in a good Software Requirement Specifications (SRS) document ?

The item not desired in an SRS is the Algorithm for Software Implementation.A Software Requirements Specification states what the system must do, its functional and non-functional requirements and the goals it must meet, not how it will be built. Algorithms belong to design and implementation.Functional requirements, non-functional requirements and the goals of implementation are all expected contents of a good SRS.

Q: A software requirements specification (SRS) document should avoid discussing which one of the following ?

An SRS should avoid discussing the Design specification.The SRS states what the software must do and the constraints on it. How the system will be structured and built is decided later, in the design document; putting design into the SRS ties the developers to choices before the requirements are settled.User interface requirements, non-functional requirements and interfaces with third-party software are all legitimate SRS content, because they describe what the system must provide or work with.

Q: Which document captures all the system requirements from stakeholders ?

The document is the SRS (Software Requirements Specification).The SRS records the complete set of functional and non-functional requirements gathered from the stakeholders: what the system must do, its interfaces, performance and constraints. It is the agreed basis for design, testing and acceptance.A test plan describes how the system will be tested, a user manual explains how to operate the finished system, and a design document describes how the requirements will be met. Each is built from the SRS rather than replacing it.

Q: A requirement is ambiguous and leads to inconsistent implementation. Which quality attribute is violated ?

The key's answer is Verifiability.A requirement is verifiable when there is a finite, cost-effective way to check that the software meets it. IEEE 830 notes that an ambiguous requirement is not verifiable: if it can be read in more than one way, there is no single criterion to test against, which is how different developers come to implement it differently.Traceability is the ability to link a requirement to its source and to design and tests. Completeness means nothing required is missing. Validation is an activity, checking that the requirements meet the customer's needs, not a quality attribute of a single requirement.

Q: Which of the following is not a tool for data collection ?

The one that is not a data collection tool is Program flowcharts.Systems analysts gather facts about an existing system through fact-finding techniques: interviews, questionnaires, on-site observation and review of records. Each of these collects information from users or the work itself.A program flowchart is a design and documentation tool that shows the logic of a program. It is produced from the facts once they are gathered, not used to collect them.

Q: Which of the following term is best defined by the statement : "Derive traceability information to maximize information hiding in the design." ?

The statement defines the risk of Requirements changes.In Sommerville's table of software risks and strategies, the strategy for requirements changes is to derive traceability information to assess the impact of a change, and to maximise information hiding in the design so that a change stays inside one module.Underestimated development time is handled by buying in components and using program generators, and organisational restructuring by keeping management informed of the project's importance, so neither fits.

11.

Which one of the following is NOT desired in a good Software Requirement Specifications (SRS) document ?

A.Functional Requirements
B.Non-Functional Requirements
C.Goals of Implementation
D.Algorithm for Software Implementation

Exam Year(s)

Tripura Public Service Commission - 2025,

Answer: D

The item not desired in an SRS is the Algorithm for Software Implementation.

A Software Requirements Specification states what the system must do, its functional and non-functional requirements and the goals it must meet, not how it will be built. Algorithms belong to design and implementation.

Functional requirements, non-functional requirements and the goals of implementation are all expected contents of a good SRS.

Discuss in Forum

12.

A software requirements specification (SRS) document should avoid discussing which one of the following ?

A.User interface issues
B.Non-functional requirements
C.Design specification
D.Interfaces with third party software

Exam Year(s)

Tripura Public Service Commission - 2025,

Answer: C

An SRS should avoid discussing the Design specification.

The SRS states what the software must do and the constraints on it. How the system will be structured and built is decided later, in the design document; putting design into the SRS ties the developers to choices before the requirements are settled.

User interface requirements, non-functional requirements and interfaces with third-party software are all legitimate SRS content, because they describe what the system must provide or work with.

Discuss in Forum

13.

Which document captures all the system requirements from stakeholders ?

A.SRS (Software Requirements Specification)
B.Test plan
C.User manual
D.Design document

Exam Year(s)

Tripura Public Service Commission - 2026,

Answer: A

The document is the SRS (Software Requirements Specification).

The SRS records the complete set of functional and non-functional requirements gathered from the stakeholders: what the system must do, its interfaces, performance and constraints. It is the agreed basis for design, testing and acceptance.

A test plan describes how the system will be tested, a user manual explains how to operate the finished system, and a design document describes how the requirements will be met. Each is built from the SRS rather than replacing it.

Discuss in Forum

14.

A requirement is ambiguous and leads to inconsistent implementation. Which quality attribute is violated ?

A.Verifiability
B.Traceability
C.Completeness
D.Validation

Exam Year(s)

Tripura Public Service Commission - 2026,

Answer: A

The key's answer is Verifiability.

A requirement is verifiable when there is a finite, cost-effective way to check that the software meets it. IEEE 830 notes that an ambiguous requirement is not verifiable: if it can be read in more than one way, there is no single criterion to test against, which is how different developers come to implement it differently.

Traceability is the ability to link a requirement to its source and to design and tests. Completeness means nothing required is missing. Validation is an activity, checking that the requirements meet the customer's needs, not a quality attribute of a single requirement.

Discuss in Forum

15.

Which of the following is not a tool for data collection ?

A.On-site observations
B.Program flowcharts
C.Interview
D.Questionnaires

Exam Year(s)

Tripura Public Service Commission - 2026,

Answer: B

The one that is not a data collection tool is Program flowcharts.

Systems analysts gather facts about an existing system through fact-finding techniques: interviews, questionnaires, on-site observation and review of records. Each of these collects information from users or the work itself.

A program flowchart is a design and documentation tool that shows the logic of a program. It is produced from the facts once they are gathered, not used to collect them.

Discuss in Forum

16.

Which of the following term is best defined by the statement : "Derive traceability information to maximize information hiding in the design." ?

A.Underestimated development time
B.Organizational restructuring
C.Requirements changes
D.None of the mentioned above

Exam Year(s)

Tripura Public Service Commission - 2019,

Answer: C

The statement defines the risk of Requirements changes.

In Sommerville's table of software risks and strategies, the strategy for requirements changes is to derive traceability information to assess the impact of a change, and to maximise information hiding in the design so that a change stays inside one module.

Underestimated development time is handled by buying in components and using program generators, and organisational restructuring by keeping management informed of the project's importance, so neither fits.

Discuss in Forum

17.

Which one of the following is not a step of requirement engineering ?

A.Requirement elicitation
B.Requirement analysis
C.Requirement design
D.Requirement documentation

Exam Year(s)

UGC NET - 2013,

Answer: C

'Requirement design' is not a step of requirement engineering. The process consists of elicitation (gathering needs), analysis (resolving conflicts and checking feasibility), specification or documentation, and validation.

Design belongs to the later software design phase, where the structure of the solution is decided from the requirements. Elicitation, analysis and documentation are all genuine requirement engineering steps, so they cannot be the answer to this 'which is not' question.

Discuss in Forum

18.

Consider the following characteristics :

(i) Correct and unambiguous
(ii) Complete and consistent
(iii) Ranked for importance and/or stability and verifiable
(iv) Modifiable and Traceable Which of the following is true for a good SRS ?

A.(i), (ii) and (iii)
B.(i), (iii) and (iv)
C.(ii), (iii) and (iv)
D.(i), (ii), (iii) and (iv)

Exam Year(s)

UGC NET - 2013,

Answer: D

A good software requirements specification has all the characteristics listed: it is correct and unambiguous, complete and consistent, ranked for importance and stability and verifiable, and modifiable and traceable. This is option D.

Each of options A, B and C leaves out one pair of the qualities, but the standard list for a good SRS contains all of them, so none of the partial lists is complete. The properties are taken from the standard on recommended practice for software requirements specifications, which lists them as the marks of a good SRS.

Discuss in Forum

Loading…

Topics

Other Subjects

Tags: Requirements Engineering Questions and Answers || Requirements Engineering MCQ Questions and Answers || Requirements Engineering GK Questions and Answers || Requirements Engineering GK MCQ Questions || Requirements Engineering Multiple Choice Questions and Answers || Requirements Engineering GK || GK on Requirements Engineering || Software Engineering Questions and Answers || Software Engineering MCQ Questions and Answers || Software Engineering GK Questions and Answers || GK on Software Engineering

Requirements Engineering Questions and Answers

Topics

Other Subjects

About Us

Stay informed about all important Dates & Notifications