ITPEC IP April 2024 Question 52

Dividing development into stages and performing each later stage in order from the outputs of the previous ones — the waterfall model runs the phases one after another, like water falling down steps.

Requirements definition, design, programming, testing and installation are done in that order. Each phase ends with reviewed deliverables (documents, programs) that become the input of the next phase, and going back to an earlier phase is not planned for. Progress is easy to manage, which suits large projects, but the requirements are fixed early, so a mistake found in testing means costly rework of earlier phases.

Answer (c)

Why not others:

• •(a) — going back and forth between design and programming by trial and error is the round-trip style of object-oriented development, an iterative approach, the opposite of waterfall's one-way flow
• •(b) — repeating the development process for each subsystem while responding to users' requests is the spiral model
• •(d) — building a prototype early and settling requirements and specifications from users' comments is the prototyping model

Key rule: Waterfall flows one way, phase by phase, on fixed deliverables; the spiral, iterative and prototyping models build repetition and user feedback into the plan.

Software Development Management Techniques · AI-written, may contain errors