Match each software lifecycle model in List – I to its description in List –…
2016
Match each software lifecycle model in List – I to its description in List – II :
\(\begin{array}{clcl} \text{} & \textbf{List-I} && \textbf{List-II} \\ \text{I.} & \text{Code-and-Fix} & \text{a.} & \text{Assess risks at each step; do most critical} \\ &&& \text{action first} \\ \text{II.} & \text{Evolutionary} & \text{b.} & \text{Build an initial small requirement specifications,} \\ &&&\text{code it, then “evolve” the specifications and code} \\ &\text{Prototyping}&& \text{as needed} \\ \text{III.} & \text{Spiral} & \text{c.} & \text{Build initial requirement specification for several}\\ &&& \text{releases, then design-and-code in sequence} \\ \text{IV.} & \text{Stagged delivery} & \text{d.} & \text{ Standard phases (requirements, design, code, test)} \\&&&\text{in order} \\ \text{V.} & \text{Waterfall} & \text{e.} & \text{Write some code,debug it, repeat(i.e. ad-hoc)} \\ \end{array}\)
Codes :
- A.
I-e, II-b, III-a, IV-c, V-d
- B.
I-e,II-c, III-a IV-b, V-d
- C.
I-d, II-a, III-b, IV-c, V-e
- D.
I-c, II-e, III-a, IV-b, V-d
Attempted by 270 students.
Show answer & explanation
Correct answer: A
Correct matching:
Code-and-Fix: Write some code, debug it, repeat (ad-hoc).
Evolutionary: Build an initial small requirement specification, code it, then evolve the specifications and code as needed.
Spiral: Assess risks at each step; do the most critical actions first (risk-driven iterative development).
Stagged delivery: Build initial requirement specifications for several releases, then design and code each release in sequence.
Waterfall: Follow standard phases (requirements, design, code, test) in order (linear development).
Explanation: These mappings match each model’s characteristic approach—ad-hoc iteration for Code-and-Fix, incremental evolution for Evolutionary, risk-driven iteration for Spiral, planned multiple releases for Stagged delivery, and linear phase sequencing for Waterfall.