Free Requirements Engineering MCQs with Answers

125 Requirements Engineering MCQs from Software Engineering, each with the correct answer and a written explanation of why it is correct. Free and unlimited, with no account needed.

Last updated

125 questions · page 5 of 7

  • A. Consistent
  • B. Non-verifiable
  • C. Correct
  • D. Ambiguous

Explanation: An EOF character is not sufficiently defined here, so different implementations or readers may interpret the requirement differently and…

Correct answer: Non-verifiable
  • A. Cost
  • B. Design Constraints
  • C. Staffing
  • D. Delivery Schedule

Explanation: Design constraints belong in an SRS because they restrict the acceptable implementation, such as required technologies, standards…

Correct answer: Design Constraints
  • A. Consistent
  • B. Non-Verifiable
  • C. Correct
  • D. Ambiguous

Explanation: “Good human interface” has no measurable acceptance criterion because good can mean different things to different stakeholders.

Correct answer: Non-Verifiable
  • A. Consistent
  • B. Verifiable
  • C. Non-verifiable
  • D. Correct

Explanation: The requirement gives measurable limits for response time and frequency, so testing can determine whether it is satisfied.

Correct answer: Verifiable
  • A. black-box
  • B. white-box
  • C. grey-box
  • D. none of the mentioned

Explanation: An SRS describes externally observable behaviour without specifying internal implementation details, so it is treated as a black-box…

Correct answer: black-box
  • 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

Explanation: An SRS is consistent when its requirements do not contradict one another.

Correct answer: no subset of individual requirements described in it conflict with each other
  • A. Verifiable
  • B. Ambiguous
  • C. Complete
  • D. Traceable

Explanation: A good SRS must state requirements clearly enough to be verified, completely, and with traceability to their sources and downstream work.

Correct answer: Ambiguous
  • A. Primary
  • B. Secondary
  • C. Ternary
  • D. Both Primary and Secondary

Explanation: In OOSE use-case modelling, actors are commonly classified as primary actors, who initiate or directly benefit from a use case, and…

Correct answer: Both Primary and Secondary
  • A. Known, Unknown, Undreamed
  • B. User, Developer
  • C. Functional, Non-Functional
  • D. Normal, Expected, Exciting

Explanation: QFD commonly classifies customer requirements as normal, expected, and exciting: normal requirements are explicitly requested, expected…

Correct answer: Normal, Expected, Exciting
  • A. Identifying Stakeholder
  • B. Listing out Requirements
  • C. Requirements Gathering
  • D. All of the mentioned

Explanation: Stakeholders are identified first because they possess, use, influence, or are affected by the requirements.

Correct answer: Identifying Stakeholder
  • A. Object Oriented Design (by Booch)
  • B. Use Cases (by Jacobson)
  • C. Fusion (by Coleman)
  • D. Object Modeling Technique (by Rumbaugh)

Explanation: Jacobson introduced use cases as a way to capture user-system interactions and provide a functional view of the system during elicitation…

Correct answer: Use Cases (by Jacobson)
  • A. Availability
  • B. Testability
  • C. Usability
  • D. Flexibility

Explanation: Testability is a developer-oriented requirement because it specifies how easily the software can be checked against its requirements.

Correct answer: Testability
  • A. It is a degree to which software running on one platform can easily be converted to run on another platform
  • B. It cannot be enhanced by using languages, OS' and tools that are universally available and standardized
  • C. The ability of the system to behave consistently in a user-acceptable manner when operating within the environment for which the system was intended
  • D. None of the mentioned

Explanation: Portability measures how easily software can be moved from one platform or environment to another, including differences in operating…

Correct answer: It is a degree to which software running on one platform can easily be converted to run on another platform
  • A. Maintainability
  • B. Portability
  • C. Robustness
  • D. None of the mentioned

Explanation: Maintainability, portability, and robustness describe quality attributes or constraints on the system, so they are non-functional…

Correct answer: None of the mentioned
  • A. Functional
  • B. Non-Functional
  • C. Known Requirement
  • D. None of the mentioned

Explanation: Detecting an intrusion and alerting a security company specifies an observable service the system must perform, so it is functional.

Correct answer: Functional
  • A. True
  • B. False

Explanation: Functional requirements describe the services and externally observable behavior the system must provide.

Correct answer: True
  • A. Two
  • B. Three
  • C. Four
  • D. Five

Explanation: The referenced requirements-engineering classification presents five classification schemes for non-functional requirements.

Correct answer: Five
  • A. Usability, Reliability, Security, Flexibility
  • B. Availability, Reliability, Maintainability, Security
  • C. Availability, Reliability, Security, Safety
  • D. Security, Safety, Testability, Usability

Explanation: The four dependability dimensions listed here are availability, reliability, security, and safety.

Correct answer: Availability, Reliability, Security, Safety
  • A. Three
  • B. Four
  • C. Five
  • D. Six

Explanation: The referenced process divides requirements analysis into five phases, commonly including inception, elicitation, elaboration…

Correct answer: Five
  • A. True
  • B. False
  • C. Depends upon the size of project
  • D. None of the mentioned

Explanation: Requirements analysis exposes misunderstandings, missing needs, and conflicting expectations before design and implementation begin.

Correct answer: True