Unable to open this exercise
The four stages in this syllabus are analysis, design, coding and testing. They describe different activities, not four kinds of programming language.
Worked example: booking places
During analysis, find what the users need: how many places are available, what data must be entered, and what confirmation is required. Identify inputs, required outputs and constraints.
During design, plan the algorithm, data structures and tests. A flowchart or pseudocode can describe the steps before language-specific code is written.
During coding, implement that design using a suitable language and clear identifiers. During testing, compare actual results with expected results using normal, boundary and abnormal data. A program that runs without syntax errors can still calculate the wrong answer.
If testing reveals a misunderstood requirement, revisit analysis or design: development need not be a one-way line. Maintaining a released program is useful wider context, but is not a fifth required stage in this syllabus's four-stage model.
Independent practice
For a program that calculates delivery charges, describe one concrete activity in each stage. Include an expected test result so “testing” means more than seeing whether the program starts.
AI Socratic Tutor
Need guidance? Ask a question or use the hint below.
AI Socratic Tutor is an All-Access Benefit
Unlock step-by-step Socratic hints, algorithm trace table walkthroughs, and error diagnostics for every Cambridge exercise.
You're chatting with an AI tutor, not a person. AI can make mistakes, so double-check its answers.
Concept Check: Four stages
Concept Check: Four stages
- How many PDLC stages are specified here? [Space 1]
- Which stage establishes user requirements? [Space 2]
- Which stage compares outputs with expected results? [Space 3]
Interactive exercises for Module 2 and beyond require an active plan.