Software-Engineering
August 25, 2024Types-of-Models
August 25, 2024Types-of-Models
| Question 5 |
Match each software lifecycle model in List – I to its description in List – II:
| I-e, II-b, III-a, IV-c, V-d | |
| I-e, II-c, III-a, IV-b, V-d | |
| I-d, II-a, III-b, IV-c, V-e | |
| I-c, II-e, III-a, IV-b, V-d |
Question 5 Explanation:
Code and Fix → Write some code, debug it, repeat(i.e. ad-hoc)
Evolutionary prototype → Build an initial small requirement specifications, code it, then “evolve” the specifications and code as needed.
Spiral → Assess risks at each step; do most critical action first.
Staged Delivery→ Build initial requirement specification for several releases, then design-and-code in sequence
Waterfall → Standard phases(requirements,design,code,test) in order.
Evolutionary prototype → Build an initial small requirement specifications, code it, then “evolve” the specifications and code as needed.
Spiral → Assess risks at each step; do most critical action first.
Staged Delivery→ Build initial requirement specification for several releases, then design-and-code in sequence
Waterfall → Standard phases(requirements,design,code,test) in order.
Correct Answer: A
Question 5 Explanation:
Code and Fix → Write some code, debug it, repeat(i.e. ad-hoc)
Evolutionary prototype → Build an initial small requirement specifications, code it, then “evolve” the specifications and code as needed.
Spiral → Assess risks at each step; do most critical action first.
Staged Delivery→ Build initial requirement specification for several releases, then design-and-code in sequence
Waterfall → Standard phases(requirements,design,code,test) in order.
Evolutionary prototype → Build an initial small requirement specifications, code it, then “evolve” the specifications and code as needed.
Spiral → Assess risks at each step; do most critical action first.
Staged Delivery→ Build initial requirement specification for several releases, then design-and-code in sequence
Waterfall → Standard phases(requirements,design,code,test) in order.