All subjects · Information Technology · WIT13 2 hour written exam on data, enabling technologies and systems development

The waterfall method

Edexcel IAL Information Technology · WIT13 2 hour written exam on data, enabling technologies and systems development

The waterfall method develops a system in a fixed sequence of phases, each finished and signed off before the next begins. You need its concept, features, phases and the activities in each phase (spec 15.2).

Practise this in the app: instant marking and a fix for every mistake. Free, no email needed to start.

Practise this lesson

Concept and features

The waterfall method is a linear, sequential approach: like water flowing down steps, each phase flows into the next.

Features:

Phases and activities

PhaseActivities
Requirements / analysisInvestigate the current system (interviews, questionnaires, observation, document analysis); identify problems and user needs; feasibility study; produce a requirements specification agreed and signed by the client
DesignDesign data structures (normalised tables, data dictionary), inputs and outputs, user interface, processes and algorithms, security, hardware and network; plan testing
ImplementationWrite the code, build the database and interface according to the design; unit test individual modules
Testing / debuggingIntegration and system testing against the requirements; test plans with normal, boundary and erroneous data; fix bugs; user acceptance testing by the client
InstallationInstall hardware and software; convert and migrate data; choose a changeover method; train users; hand over user and technical documentation
MaintenanceCorrective, adaptive and perfective maintenance after the system is in use; review against the original requirements

Advantages and disadvantages

Advantages: simple to understand and manage; clear milestones and deliverables make progress easy to track; thorough documentation helps maintenance and new staff; costs and timescales can be estimated early; suits projects with stable, well-understood requirements, fixed contracts, or strict regulation and safety requirements.

Disadvantages: inflexible: changes to requirements are hard and expensive after sign-off; users see the product late, so misunderstandings are found late, when they cost most to fix; testing comes late, so serious errors may be found near the deadline; long time before any working software is delivered; risky for large, complex or innovative projects.

Worked example

A government agency must build a tax calculation system to a fixed legal specification by a fixed date. Explain why waterfall might suit it.

  1. The requirements are set by law and unlikely to change, so fixing them at the start is realistic.
  2. Each phase is signed off and documented, which gives the audit trail a government body needs.
  3. Clear milestones help track progress against the fixed deadline and budget.

Answer: Stable requirements, documentation and control make waterfall a good fit

Key idea: Waterfall: linear phases, each completed and signed off: requirements/analysis, design, implementation, testing/debugging, installation, maintenance. Good for stable requirements and documentation; poor at handling change; users see the system late.

Check yourself

  1. Which phase comes immediately after design in the waterfall method?
    • Requirements
    • Testing
    • Installation
    • Implementation
    Show answer

    Implementation. Design, then implementation (coding).

  2. In which waterfall phase are interviews and questionnaires used to investigate users' needs?
    • Implementation
    • Requirements / analysis
    • Installation
    • Maintenance
    Show answer

    Requirements / analysis. Fact-finding happens at the start.

  3. Data migration, user training and choosing a changeover method happen in which phase?
    • Design
    • Requirements
    • Testing
    • Installation
    Show answer

    Installation. Getting the system into use.

  4. What is the main disadvantage of the waterfall method?
    • Changing requirements after sign-off is difficult and costly
    • It produces no documentation
    • There are no clear milestones
    • It cannot be used for databases
    Show answer

    Changing requirements after sign-off is difficult and costly. Inflexibility.

  5. Which project is most suited to the waterfall method?
    • A start-up app whose features will change after user feedback
    • A game whose design will evolve each month
    • A system with clear, stable requirements and strict regulatory documentation
    • A website whose client cannot describe what they want
    Show answer

    A system with clear, stable requirements and strict regulatory documentation. Stable requirements suit waterfall.

  6. What is user acceptance testing?
    • The client tests the system to confirm it meets their requirements before accepting it
    • Developers test a single function
    • The system is tested only with erroneous data
    • Testing the network cables
    Show answer

    The client tests the system to confirm it meets their requirements before accepting it. Final sign-off by the client.

  7. Explain why errors found late in a waterfall project are expensive to fix.
    Show answer

    Because each phase builds on the previous one, an error in the requirements or design means the later design, code and tests must all be redone, which costs time and money near the deadline.. Phases build on each other, so rework, so cost.

Practise with instant feedback

Sources

Last updated 8 November 2026. Spotted a mistake? Tell us.