Requirement Engineering MCQs Archives

51. The SRS is said to be consistent if and only if____________________?

A. its structure and style are such that any changes to the requirements can be made easily while retaining the style and structure

B. every requirement stated therein is one that the software shall meet

C. every requirement stated therein is verifiable

D. no subset of individual requirements described in it conflict with each other

✅ The correct answer is option D.
Explanation: Real world object may conflict with each other for example one requirement says that all lights should be red while the other states that all lights should green

52. Considering the example of issue/return of a book, cataloging etc. in a library management.What type of management requirement is being depicted here ?

A. Enduring

B. Volatile

C. Both Enduring & Volatile

D. All of the mentioned

✅ The correct answer is option A.
Explanation: For library management system issue/return of a book, cataloging etc. are core activities and are stable for any system.

53. How many feasibility studies is conducted in Requirement Analysis ?

A. Two

B. Three

C. Four

D. None of the mentioned

✅ The correct answer is option B.
Explanation: Economic feasibility (cost/benefit analysis), Technical feasibility (hardware/software/people, etc.) and Legal feasibility studies are done in Requirement Analysis.

54. Why is Requirements Elicitation a difficult task ?

A. Problem of scope

B. Problem of understanding

C. Problem of volatility

D. All of the mentioned

✅ The correct answer is option D.
Explanation: Users specify unnecessary technical detail that may confuse, rather than clarify overall system objectives.Also, the customers/users are not completely sure of what is needed, have a poor understanding of the capabilities and limitations of their computing environment and they do not understand that the requirements change over time

55. Consider the following Statement: “The output of a program shall be given within 10 secs of event X 10% of the time.”What characteristic of SRS is being depicted here ?

A. Consistent

B. Verifiable

C. Non-verifiable

D. Correct

✅ The correct answer is option B.
Explanation: An SRS is verifiable, if and only if, every requirement stated therein is verifiable.Here the given condition can be verified during testing phase

56. To ensure that a given root definition is rigorous and comprehensive, The Lancaster team proposed several criteria that are summarized in the mnemonic CATWOE in Soft Systems Methodology (SSM).Which of the following alphabet is representing an entirely different meaning to SSM ?

A. C – Customer

B. A – Actor

C. T – Transformation

D. E – ER Model

✅ The correct answer is option D.
Explanation: ‘E’ in CATWOE stands for Environmental constraints.

57. Arrange the given sequence to form a SRS Prototype outline as per IEEE SRS Standard?

i. General description

ii. Introduction

iii. Index

iv. Appendices

✅ The correct answer is option i.
A. iii, i, ii,v, iv

58. What is the major drawback of CORE ?

A. Requirements are comprehensive

B. NFRs are not given enough importance

C. Role of analyst is passive

D. All of the mentioned

✅ The correct answer is option C.
Explanation: In CORE the requirement specification are put together by all users, customers and analysts, so a passive analyst will not get the requirements properly.

59. What are the types of requirement in Quality Function Deployment (QFD) ?

A. Known, Unknown, Undreamed

B. User, Developer

C. Functional, Non-Functional

D. Normal, Expected, Exciting

✅ The correct answer is option D.
Explanation: According to QFD, Normal, Expected and Exciting requirements maximizes customer satisfaction from the Software Engineering Process.

60. Requirements analysis is critical to the success of a development project ?

A. True

B. False

C. Depends upon the size of project

D. None of the mentioned

✅ The correct answer is option A.
Explanation: Requirements must be actionable, measurable, testable, related to identified business needs or opportunities, and defined to a level of detail sufficient for system design.