Match List I with List II. List I: Software Process Model A. Waterfall Model B. Evolutionary Model C.…

Question

Match List I with List II. List I: Software Process Model A. Waterfall Model B. Evolutionary Model C. Component-based Software Engineering D. Spiral Development List II: Description I. Software can be developed incrementally II. Requirement compromises are inevitable III. Explicit recognition of risk IV. Inflexible partitioning of the project into stages Choose the correct matching.

Accepted Answer

Correct answer: C — Concept A software process model classifies development approaches by their governing discipline: how they order activities, how they handle changing requirements, and how they treat risk. Four disciplines recur: strictly sequential phase-locking (no phase repeats or overlaps), incremental delivery in successive working versions, reuse-driven assembly from existing components (so requirements bend to fit what is available), and a dedicated risk-analysis step repeated every cycle. Application Model List II description it satisfies Why A. Waterfall Model IV. Inflexible partitioning of the project into stages Its phases (requirements, design, implementation, testing, maintenance) run once, in strict sequence, with no revisiting an earlier phase — the defining rigidity is fixed, non-negotiable staging. B. Evolutionary Model I. Software can be developed incrementally It delivers a working system in successive versions, each refined from feedback on the previous one — development proceeds in increments rather than one pass. C. Component-based Software Engineering II. Requirement compromises are inevitable The system is assembled around existing, reusable components, so the original requirements are adapted to fit what those components actually offer. D. Spiral Development III. Explicit recognition of risk Every loop of the spiral dedicates a distinct step to identifying and mitigating risk before committing to the next loop — risk analysis is built into the process itself, not an afterthought. Cross-check — contrasting the other combinations A ‐ II, B ‐ I, C ‐ III, D ‐ IV: this swaps the reuse-driven trait and the risk-driven trait between Component-based development and Spiral development, and it also treats the strictly sequential Waterfall approach as if adapting to ready-made components were its central concern — none of which matches how those three disciplines actually operate. A ‐ II, B ‐ III, C ‐ I, D ‐ IV: here every pairing is inconsistent — a fixed, phase-locked model is tied to component reuse, an incremental-delivery model is tied to risk analysis, a reuse-driven model is tied to incremental delivery, and an iterative, risk-driven model is tied to rigid staging. A ‐ IV, B ‐ I, C ‐ III, D ‐ II: the sequential and incremental rows are placed correctly, but the remaining two are exchanged — a dedicated, per-cycle risk-analysis step is not what defines reuse-driven component assembly, and adapting requirements to fit existing components is not what defines a risk-focused, iterative spiral. Result: the matching that is internally consistent with every model's actual governing discipline is A ‐ IV, B ‐ I, C ‐ II, D ‐ III.

Answer

A. A ‐ II, B ‐ I, C ‐ III, D ‐ IV

Answer

B. A ‐ II, B ‐ III, C ‐ I, D ‐ IV

Answer

C. A ‐ IV, B ‐ I, C ‐ II, D ‐ III

Answer

D. A ‐ IV, B ‐ I, C ‐ III, D ‐ II

Model	List II description it satisfies	Why
A. Waterfall Model	IV. Inflexible partitioning of the project into stages	Its phases (requirements, design, implementation, testing, maintenance) run once, in strict sequence, with no revisiting an earlier phase — the defining rigidity is fixed, non-negotiable staging.
B. Evolutionary Model	I. Software can be developed incrementally	It delivers a working system in successive versions, each refined from feedback on the previous one — development proceeds in increments rather than one pass.
C. Component-based Software Engineering	II. Requirement compromises are inevitable	The system is assembled around existing, reusable components, so the original requirements are adapted to fit what those components actually offer.
D. Spiral Development	III. Explicit recognition of risk	Every loop of the spiral dedicates a distinct step to identifying and mitigating risk before committing to the next loop — risk analysis is built into the process itself, not an afterthought.

Match List I with List II. List I: Software Process Model A. Waterfall Model…