Complete the Unit 5 software development programming project: analyse a problem, design, implement, test, document and evaluate a solution.

What this dot point is asking

Unit 5 Software Development is the non-exam assessment (the programming project): a substantial piece of coursework in which you analyse a problem, then design, implement, test, document and evaluate a working software solution. This is a single overview because the unit is a project, not a body of content to revise: it is assessed by what you produce and document, drawing on the skills from Units 1 to 4 rather than introducing new theory. The guidance here frames the stages and what each is assessed on, without padding a coursework task into multiple revision pages.

The answer

What the project is

Because it is coursework, success comes from a well-chosen problem, disciplined documentation, and a solution that genuinely meets clear objectives, all worked on over an extended period rather than revised for an exam.

The stages

Each stage builds on the previous, so weak analysis undermines everything after it: objectives set in analysis are the benchmark for both testing and evaluation.

Why objectives matter

Clear, measurable objectives are the spine of the project. They guide design and implementation (every feature should trace to an objective), and they are what testing and evaluation are measured against. Vague objectives cannot be tested or evaluated objectively, so the analysis stage shapes the marks for the later stages.

How it is marked

Examples in context

Example 1. Choosing a problem of the right scope

A project to build a small club's membership and subscription system is well scoped: rich enough to show analysis, data structures, searching and validation, but achievable in the time. A project that is too trivial cannot demonstrate the skills, and one that is too ambitious is never finished, which is why scoping the problem is part of doing the analysis well.

Example 2. A test plan written during design, not after

A strong project writes its test plan during design, listing the data and expected results for each objective before coding. When implementation is done, testing simply executes the plan. This mirrors the professional life cycle from Unit 3 and shows why design includes the test plan, rather than testing being an afterthought.

Example 3. An honest evaluation scores well

A candidate whose evaluation states plainly which objectives were fully met, which were partly met, and what a future version would improve demonstrates genuine critical judgement. An evaluation claiming everything worked perfectly is less credible and scores less well, illustrating that the evaluation rewards honest, evidence-based reflection against the objectives.

Try this

Q1. Name, in order, the main stages of the Unit 5 software development project. [5 marks]

• Cue. Analysis, design, implementation, testing and evaluation.

Q2. State why testing should be carried out against the objectives set during analysis. [2 marks]

• Cue. The objectives are the measurable benchmark; testing against them shows whether the solution actually does what it was required to do, which the evaluation then judges.