Computational Thinking · Cambridge syllabus 7.1, 7.2, 7.3 · Lesson 4 of 4
The Program Development Life Cycle
The program development life cycle has four stages: analysis, design, coding and testing. Analysis identifies the problem and its requirements, using abstraction and decomposition. Design plans the solution with decomposition, structure diagrams, flowcharts and pseudocode. Coding writes the program, testing each part as it is written (iterative testing). Testing runs the finished program with test data to check it meets the requirements.
By the end, you can
- Identify the stages of the program development life cycle: analysis, design, coding and testing.
- Describe the tasks carried out at the analysis stage.
- Describe the tasks carried out at the design stage.
- Describe the tasks carried out at the coding stage, including iterative testing.
- Describe the tasks carried out at the testing stage, using test data.
The four stages
The program development life cycle (PDLC) is the series of stages a program goes through as it is made. The syllabus limits it to four stages: analysis, design, coding and testing.
Analysis is about understanding the problem. The problem is identified and its requirements are written down: what the program must do, what it will input and output, and who will use it. Abstraction removes the details that do not matter, and decomposition breaks the problem into its parts.
Design is about planning the solution before any code is written. The problem is decomposed further, and the solution is shown with structure diagrams, flowcharts and pseudocode, so that it can be checked before time is spent on code.
Coding is writing the program code from the design. It includes iterative testing: each part is tested as soon as it is written, errors are fixed, and it is tested again, so that problems are found while the code is fresh. Testing is the final stage: the whole program is run with planned test data, normal, abnormal, extreme and boundary, to check that it works and meets the requirements found in analysis.
For a school library system: analysis finds that the librarian needs to record loans and returns and list overdue books; design draws a structure diagram with parts for loans, returns and reports, and writes pseudocode for each; coding writes and tests each part; testing runs the finished system with loans that are on time, overdue and invalid. If testing finds a problem, the team goes back to an earlier stage, which is why it is called a cycle.
Worth remembering
- Four stages: analysis, design, coding and testing.
- Analysis: identify the problem and requirements, with abstraction and decomposition.
- Design: structure diagrams, flowcharts and pseudocode.
- Coding with iterative testing, then testing the whole program with test data.
Worked example
For a school library loan system: analysis lists what the librarian needs, such as loans, returns and overdue books; design draws a structure diagram and writes pseudocode for each part; coding writes and tests each module; testing tries normal, abnormal, extreme and boundary data.
Practice
Warm-up · not marked
Check your understanding
Answer in your own words, then compare with the worked answer. Nothing here is saved or scored.
Worked answer
Design.
Check your method, units and explanation against it.
Marked practice
Set 1 of 4 · easiest first · Checked as you go, with the worked answer. Sign in or create a free account to save your progress.