WJEC A-Level Computer Science Unit 5 Software Development: the programming project (non-exam assessment) and how to approach it
A WJEC A-Level Computer Science guide to Unit 5 Software Development, the programming project assessed as non-exam assessment. Explains how the project is structured and marked, the analysis, design, implementation, testing and evaluation stages, the importance of clear objectives, and how it draws on the skills from Units 1 to 4.
Reviewed by: AI editorial process; not yet individually human-reviewed
Jump to a section
What Unit 5 actually demands
Unit 5 Software Development is the programming project, assessed as a non-exam assessment rather than by a written paper. Over an extended period you analyse a problem, then design, implement, test, document and evaluate a working software solution. It does not add new theory: it is where the analysis, design, programming, testing and evaluation skills from Units 1 to 4 come together in one substantial piece of work.
Because it is a project rather than examinable content, this guide is short and focuses on how to approach and document the work. There is one matching dot-point page; this overview frames the stages and the marking.
How the project is structured and marked
The project is marked on its documented stages, carried out in order:
- Analysis. Investigate the problem and set clear, measurable objectives for the solution.
- Design. Specify the algorithms, data structures, user interface and a test plan, in enough detail to be implemented.
- Implementation. Develop the solution, evidencing the code and the techniques used.
- Testing. Test the solution against the plan and the objectives, using normal, boundary and erroneous data, and document the results.
- Evaluation. Judge the finished solution against its objectives and the user's needs, and identify limitations and improvements.
It contributes 20 per cent of the full A level. The quality of the documentation at each stage, and how well the stages connect, drive the marks.
The importance of clear objectives
Clear, measurable objectives are the spine of the project. They guide design and implementation, because every feature should trace back to an objective, and they are the benchmark for testing and evaluation. Vague objectives cannot be tested or evaluated, so strong analysis underpins strong marks throughout.
Choosing and scoping the problem
Choose a problem rich enough to demonstrate analysis, suitable data structures, algorithms and validation, but achievable in the time. Too trivial a problem cannot show the skills; too ambitious a one risks being unfinished. A realistic scenario or real user helps you set meaningful objectives and gives the evaluation something concrete to judge.
How Unit 5 draws on the course
The project applies, rather than extends, the course. The life cycle and testing strategies of Unit 3 shape its structure; the programming principles and data structures of Unit 1 and the practical programming of Unit 2 build the solution; and good design, validation and honest evaluation run throughout. It is the capstone where everything is used together.
The matching dot point
The unit has one dot-point page setting out the project stages in more detail, with worked guidance and cross-links to the analysis, design and testing topics it applies. Browse it from this overview and the subject hub.
For the official specification
WJEC publishes the full specification, the non-exam assessment guidance, deadlines and exemplar material at wjec.co.uk. Always follow the current WJEC assessment guidance and submission deadlines, because the project rules and mark allocations are board-specific.