What are the stages of the system development life cycle, and why is software developed as a repeating cycle?
Describe the stages of the system development life cycle, analysis, design, development, testing, installation and review, explain what happens at each, and explain why development is iterative.
A CCEA GCSE Digital Technology answer on the system development life cycle for the Programming route (Unit 4), covering the stages of analysis, design, development, testing, installation and review, what happens at each stage, and why development is an iterative cycle.
Reviewed by: AI editorial process; not yet individually human-reviewed
Have a quick question? Jump to the Q&A page
Jump to a section
What this dot point is asking
Software is not written all at once; it is developed through an organised sequence of stages. The Programming route (Unit 4, Digital Development Concepts) expects you to name and describe the stages of the system development life cycle, explain what happens at each, and explain why development is iterative, that is, a repeating cycle. This framework underpins the whole route and the practical unit, where you analyse, design, build, test and evaluate a program.
Why a life cycle is used
Developing software without a plan leads to errors, wasted effort and a product that does not meet the user's needs. The system development life cycle gives a structured, ordered approach so that the problem is understood first, the solution is planned before coding, and the result is tested and reviewed. Following the stages in order keeps the project under control and makes sure each step builds on the one before.
The stages of the life cycle
You must be able to name the stages in the correct order and describe what happens at each.
Each stage has a clear job. Analysis asks what the system must do, gathering and recording the requirements. Design turns those requirements into a plan, including how the program will be structured and how the interface will look, so that coding follows a blueprint. Development is the coding itself, building the planned solution. Testing checks the program is correct and meets the requirements, using carefully chosen test data, and any errors found are corrected. Installation puts the working system into real use, which may involve transferring existing data and training the users. Review evaluates the system once it is in use, judging it against the original requirements and finding what could be improved.
Why development is iterative
The life cycle is not a one-way street; it is a repeating cycle.
This matters because real systems are rarely perfect first time and because users' needs change. By looping back, the developer can fix problems found late and add improvements, keeping the system fit for purpose over time.
Applying the life cycle to a scenario
The exam often gives a development scenario and asks you to place actions in the right stage, so the skill is matching each activity to its stage.
Why this matters
The system development life cycle is the backbone of the Programming route. It frames how programs are created, is examined directly in Unit 4, and is exactly the process you follow in the Unit 5 practical, where you analyse a task, design a solution, develop and test it, and evaluate it. Knowing the stages, what each involves, and why the process repeats secures marks across both.
Exam-style practice questions
Practice questions written in the style of CCEA exam questions on this dot point, with worked answer explainers. The year tag is the paper they imitate, not the source.
CCEA-style (Unit 4)5 marksName and describe the stages of the system development life cycle in the correct order.Show worked answer →
The stages in order are analysis, design, development, testing, installation and review (1 mark for the correct order, plus marks for the descriptions).
Analysis: investigate and understand the problem and decide what the system must do (its requirements). Design: plan the solution, including the structure of the program and the user interface, before coding. Development: write the program code to build the planned solution. Testing: check the program works correctly and meets the requirements, using test data, and fix errors. Installation: put the finished system into use, including any data transfer and user training. Review: evaluate the system in use against the requirements and identify improvements. Up to 4 marks for clear descriptions of the stages, with the order mark on top.
CCEA-style (Unit 4)3 marksExplain why the system development life cycle is described as iterative rather than a single straight line.Show worked answer →
It is iterative because the stages are repeated rather than carried out only once (1 mark for the idea of repeating the cycle).
The review stage often reveals improvements or new requirements, which sends the developer back to analysis and design to make changes, so the cycle goes round again, each time refining the system (1 mark). Earlier stages can also be revisited if testing finds problems that need a design change, so development loops back rather than always moving forward (1 mark). A strong answer makes clear that iteration lets the system be improved over time and that problems found late send the work back to an earlier stage.
Related dot points
- Explain what an algorithm is, describe how a solution is designed and represented using flowcharts, pseudocode and structure diagrams, and explain the role of interface design and decomposition.
A CCEA GCSE Digital Technology answer on algorithms and design for the Programming route (Unit 4), covering what an algorithm is, designing and representing a solution with flowcharts, pseudocode and structure diagrams, decomposition, and interface design.
- Explain how programs store data in variables and constants, describe the common data types (integer, real, Boolean, character and string), and explain why the correct data type is chosen.
A CCEA GCSE Digital Technology answer on data, variables and data types for the Programming route (Unit 4), covering variables and constants, the common data types of integer, real, Boolean, character and string, and why the correct data type is chosen.
- Explain how programs are tested using a test plan and normal, boundary and erroneous test data, describe syntax, logic and runtime errors, and explain how a program is evaluated against its requirements.
A CCEA GCSE Digital Technology answer on testing and evaluating programs for the Programming route (Unit 4), covering test plans and normal, boundary and erroneous test data, the types of error (syntax, logic and runtime), and evaluating a program against its requirements.
- Outline the Unit 5 Digital Development Practice controlled assessment for the Programming route, including the CCEA-set task, the analyse, design, develop, test and evaluate stages, and how the work is assessed.
A CCEA GCSE Digital Technology overview of the Unit 5 Digital Development Practice controlled assessment for the Programming route, covering the CCEA-set task, the analyse, design, develop, test and evaluate stages, and how the practical programming work is assessed.
- Evaluate the ethical, legal, environmental and social impact of digital technology on society, and describe the purpose of the Data Protection legislation, the Computer Misuse Act and the Copyright, Designs and Patents Act.
A CCEA GCSE Digital Technology answer on the ethical, legal, environmental and social impact of digital technology on wider society, including the Data Protection legislation, the Computer Misuse Act and the Copyright, Designs and Patents Act.
Sources & how we know this
- CCEA GCSE Digital Technology (2017) specification — CCEA (2017)