Skip to main content
Northern IrelandSoftware Systems DevelopmentSyllabus dot point

How is a complete software solution planned, built, tested and evaluated for the A2 2 Implementing Solutions project?

The A2 2 Implementing Solutions practical project - applying the full software development process to design, implement, test, document and evaluate a working solution.

A CCEA A-Level Software Systems Development overview of the A2 2 Implementing Solutions practical project: applying the full software development process to analyse, design, implement, test, document and evaluate a working software solution.

Generated by Claude Opus 4.812 min answer

Reviewed by: AI editorial process; not yet individually human-reviewed

Have a quick question? Jump to the Q&A page

Jump to a section
  1. What this dot point is asking
  2. The answer
  3. Examples in context
  4. Try this

What this dot point is asking

A2 2 Implementing Solutions is the practical project: you apply the complete software development process to one substantial problem, producing a working software solution together with the analysis, design, testing and evaluation that surround it. This page is a concise overview of what the project involves and how the process from the rest of the course comes together in it. (CCEA also assesses written understanding of this development process.)

The answer

What the project is

The point is to demonstrate, on a single sizeable piece of work, that you can plan, build, test and judge software, not just answer questions about it.

The stages of the project

How the course comes together

The project is where the rest of the specification is applied. Object oriented design (classes, encapsulation, inheritance) and event driven techniques (forms, controls, file handling) from the AS units build the solution; the database and SQL skills from A2 1 structure and query its data; and the systems discipline (requirements, modelling, a test plan, evaluation) organises the work. Good practice throughout - clear requirements, sensible design, readable code, thorough testing and an honest evaluation - is what distinguishes a strong project.

Worked example: planning a project end to end

Examples in context

Example 1. A school library loan system. The project gathers requirements from the librarian, designs Book, Member and Loan tables with an ERD, builds an event driven interface with validated inputs, tests issuing and returning books with normal, boundary and erroneous data, and evaluates the result against the requirements, recommending an overdue-reminder feature. Every part of the course is exercised on one coherent problem.

Example 2. A small business invoicing tool. Requirements (create invoices, record payments, list debtors) drive a design with Customer and Invoice tables and SQL queries for the debtor report. The solution is implemented in stages, tested against a prepared plan, documented, and evaluated honestly, noting that a planned PDF export was not completed, an example of identifying a limitation against the original objectives.

Try this

Q1. State two stages of the software development process that come before implementation. [2 marks]

  • Cue. Analysis (gathering requirements) and design (planning the interface, data, algorithms and test plan).

Q2. State the three categories of test data a project's test plan should include. [3 marks]

  • Cue. Normal (valid), boundary (on and just beyond the limits) and erroneous (invalid) data.

Q3. Explain what an evaluation of the finished solution should be measured against. [2 marks]

  • Cue. Against the original requirements and objectives set during analysis, stating which were met, which were not, and possible improvements.

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 20198 marksDescribe the main stages a developer works through when completing a software development project, from understanding the problem to reviewing the finished solution.
Show worked answer →

A software development project applies the full development process to one substantial problem.

Analysis and requirements: investigate the problem, identify the user and their needs, and write clear, testable requirements and objectives for the solution.

Design: plan how the solution will meet the requirements, including the interface (screen and report layouts), the data structures and any database (tables, keys, an entity relationship diagram), the algorithms and the structure of the program (its classes and methods), and a test plan prepared in advance.

Implementation: build the solution from the design, writing well-structured, readable code with sensible names, validation and comments, developed in stages.

Testing: run the prepared test plan with normal, boundary and erroneous data, record actual against expected results, and correct any faults found.

Documentation and evaluation: produce the necessary documentation (such as user and technical guidance) and evaluate the finished solution against the original requirements, judging how well it meets them and identifying limitations and improvements.

Markers reward a sensible end-to-end sequence (analysis, design, implementation, testing, documentation and evaluation) with a correct description of the purpose of each stage.

CCEA 20216 marksExplain why a test plan and an evaluation against the original requirements are important parts of a software development project.
Show worked answer →

A test plan is important because it provides systematic, repeatable evidence that the solution works and meets its requirements. Prepared in advance, it lists each test, the test data (normal, boundary and erroneous), the expected result and, once run, the actual result. Testing against the plan finds errors before the solution is handed over, and using boundary and erroneous data as well as normal data confirms the solution handles limits and invalid input safely, not just typical cases.

An evaluation against the original requirements is important because it judges, objectively, how well the finished solution does what it was supposed to do. By measuring the solution against each requirement and objective set during analysis, the developer can show which were met, identify any that were not, and recommend limitations and future improvements. This closes the loop: requirements set the target at the start, and the evaluation checks the target was hit at the end.

Markers reward the test plan's role (systematic, planned evidence using all three data categories to find faults) and the evaluation's role (judging the solution against the original requirements, identifying what was met, limitations and improvements).

Related dot points

Sources & how we know this