← IGCSE Computer Science Paper 2

Matching a task to its PDLC stage

The four PDLC stages in order; each task belongs to one: analysis lists requirements, design draws flowcharts, coding writes code, testing runs test data.

Part of: IGCSE Computer Science 0478 — 7a Program Development Life Cycle — Module 18

Understanding Matching a task to its PDLC stage in IGCSE Computer Science Paper 2

What it does: Drawing a flowchart is design, because it plans the solution before any code is written. Listing requirements is analysis because it works out what the program must do, not how it will do it. Writing the code and fixing mistakes as you go is coding because the program is being built. Iterative testing while coding still belongs to this stage.

Common mistakes: Writing the code is the coding stage. Testing is when the finished program is run with test data. It should be: Write the code -> Coding. Boundary data is a type of test data, and running the program with test data is the testing stage. It should be: Use boundary data -> Testing.

Class: _____________________  ·  Name: _____________________  ·  Date: _________

Free printable worksheet with full answer key — or add this module to a class and your students practise it interactively.

🖨 Print worksheet + answer key Add Matching a task to its PDLC stage to a class →

This module's key terms are also in a printable crossword (Modules 17–26) and word search (Modules 1–26).

Take this worksheet further — free with Cloodit

Each concept is reinforced from every angle — learned, then applied, then tested.

Learning
Duo
A developer draws a flowchart showing how the program will work. Which stage is this?
CodingDesign
Matches
Drawing a flowchart is part of the analysis stage
↓
Flowcharts are drawn in the design stage, not analysis. Analysis is for listing requirements.
Applying
Meanings
Term
analysis, design, coding, testing
Meaning
The four PDLC stages in order; each task belongs to one: analysis lists requirements, design draws flowcharts, coding writes code, testing runs test data.
Practice
// Listing requirements is analysis because it states what the program must do
Testing
Gaps
Finding out what users need is
Check Answer
Spots
2Draw flowchart -> Design
3Write the code -> Testing

Cloodit turns curriculum-aligned coding content into journeys students work through one biome at a time.

The 'Lion' badge — Inheritance King, one of Cloodit's 106 collectible badges
Students earn collectable badges

Over 100 of them, across seven natural biomes.

Study Buddy
Students build a real study resource

Turns their work into revision material ready for Flash Cards and Exam study.

Diamond Dash — one of Cloodit's live, competitive Sprint games
Students lock in with Sprints

Live, competitive practice for the start of the lesson or a teacher-led lesson finisher.

A Cloodit certificate of achievement, ready to personalise and print
Custom printable certificates

Honour your top performers, or encourage a student who's trying hard — ready to print in seconds.

Add to class →

Quick Questions

1. A developer draws a flowchart showing how the program will work. Which stage is this?
A. Design ✓
B. Coding
Drawing flowcharts, hierarchy charts and writing pseudocode are design tasks because they plan the solution before any program code is written.
2. A developer lists what the program must do, including its inputs, processes and outputs. Which stage is this?
A. Analysis ✓
B. Design
Listing requirements is analysis because it works out what the program must do, not how it will do it.
3. A developer writes the program in a programming language and fixes errors as they go. Which stage is this?
A. Testing
B. Coding ✓
Writing the code and fixing mistakes as you go is coding because the program is being built. Iterative testing while coding still belongs to this stage.
4. A developer runs the finished program with normal, abnormal and extreme test data. Which stage is this?
A. Testing ✓
B. Coding
Running the finished program with test data is testing because it checks the program meets the requirements.
5. Which task belongs to the analysis stage?
A. Drawing a flowchart of the algorithm
B. Writing down the requirements of the program ✓
Writing requirements is analysis because it says what the program must do. A flowchart shows how it will do it, so it is design.

Match the Pairs

Listing what the program must do → Analysis stage: the task of finding and listing the requirements of the program
Running the program with test data → Testing stage: the task of checking the program works using normal, abnormal, extreme and boundary data
Design stage: planning how the program will work, for example by drawing a flowchart → Draw a flowchart of the algorithm
Coding stage: writing the program and fixing errors as you go with iterative testing → Write the program and fix errors as you go
Drawing a flowchart is part of the analysis stage → Flowcharts are drawn in the design stage, not analysis. Analysis is for listing requirements.
Running test data is part of the coding stage → Running the program with test data is the testing stage. Coding is for writing the program.

Key Term

analysis, design, coding, testing
The four PDLC stages in order; each task belongs to one: analysis lists requirements, design draws flowcharts, coding writes code, testing runs test data.

Fill in the Blanks

1. Finding out what users need is analysis
Hint: Type the PDLC stage where the problem is studied and requirements are found.
2. Writing and fixing code is the coding stage
Hint: Type the PDLC stage where the program is written and fixed as you go.
3. Running test data is the testing stage
Hint: Type the PDLC stage where the finished program is run with test data.
4. Drawing a flowchart is the design stage
Hint: Type the PDLC stage where the solution is planned with flowcharts.
5. Listing requirements is analysis because we must understand the problem first
Hint: Type the PDLC stage where a requirements list is written, before anything is designed.

Spot the Error

Question 1
A List requirements -> Analysis
B Draw flowchart -> Design
C Write the code -> Testing
D Run test data -> Testing
Line C — Writing the code is the coding stage. Testing is when the finished program is run with test data. It should be: Write the code -> Coding.
Question 2
A Find the outputs -> Analysis
B Draw hierarchy chart -> Design
C Fix bugs as you go -> Coding
D Use boundary data -> Coding
Line D — Boundary data is a type of test data, and running the program with test data is the testing stage. It should be: Use boundary data -> Testing.
Question 3
A Write pseudocode -> Coding
B Code the program -> Coding
C Run test data -> Testing
Line A — Pseudocode is a design method. It plans the algorithm before any real code is written. It should be: Write pseudocode -> Design.
Question 4
A Task: list requirements
B Stage: Analysis
C Because it plans the layout
Line C — The reason does not match the task. Listing requirements is analysis because it says what the program needs to do. Planning the layout belongs to design.
Question 5
A Task: run test data
B Stage: Coding
C Because it checks it works
Line B — Running a program with test data to check it works is the testing stage, not coding. It should be: Stage: Testing.

Student with a class code? Join your class →