All Free Software Engineering MCQs with Answers

Every Software Engineering question in the bank, across all chapters, each with the correct answer and a written explanation. Free and unlimited, with no account needed.

1,731 questions · page 8 of 87

  • A. RTM
  • B. DOORS
  • C. Rational Suite
  • D. RDD 100

Explanation: RTM usually means Requirements Traceability Matrix, a document or tracking artifact rather than a requirements-management workbench tool.

Correct answer: Rational Suite
  • A. Automatic Link Detection
  • B. Documentation Support
  • C. Graphical Representation
  • D. Automatic Link Creation and Change

Explanation: Automatic Link Detection identifies relationships between artifacts by examining names, history, information-retrieval results, or model…

Correct answer: Automatic Link Detection
  • A. True
  • B. False

Explanation: Requirements management continues throughout the project because requirements must be traced, reviewed, and updated as approved changes…

Correct answer: False
  • A. Poor change management
  • B. Poor requirements management
  • C. Poor quality control
  • D. All of the mentioned

Explanation: Poor requirements management allows unclear, incomplete, conflicting, or changing requirements to propagate through the project, causing…

Correct answer: Poor requirements management
  • A. Two
  • B. Three
  • C. Four
  • D. Five

Explanation: FODA is commonly described through three main steps: context analysis, domain modeling, and architecture modeling.

Correct answer: Three
  • A. Iterative in nature
  • B. Redundancies are removed
  • C. It is simple and an easier method to use
  • D. Consistency problems are addressed in CORE

Explanation: CORE uses structured requirements representation and analysis to expose and address consistency problems.

Correct answer: Consistency problems are addressed in CORE
  • A. Requirements are comprehensive
  • B. NFRs are not given enough importance
  • C. Role of analyst is passive
  • D. All of the mentioned

Explanation: A recognized drawback of CORE is that the analyst has a relatively passive role, with much of the requirements contribution expected from…

Correct answer: Role of analyst is passive
  • A. True
  • B. False

Explanation: A narrative essay is difficult to analyze, trace, validate, and maintain because requirements are embedded in unstructured prose.

Correct answer: False
  • A. Problem of scope
  • B. Problem of understanding
  • C. Problem of volatility
  • D. All of the mentioned

Explanation: Elicitation is difficult because the scope may be unclear, stakeholders may understand the need differently, and requirements can change…

Correct answer: All of the mentioned
  • A. True
  • B. False

Explanation: Elicitation is cyclic because requirements are repeatedly gathered, analysed, clarified, validated, and refined as stakeholders and…

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