CCEA A-Level Software Systems Development A2 2 Implementing Solutions: a complete overview of the practical project and the software development process

What this unit demands

A2 2 Implementing Solutions is the practical project of CCEA A-Level Software Systems Development. It asks you to take one substantial problem through the complete software development process and deliver a working solution, demonstrating that you can plan, build, test and evaluate software, not just answer questions about it. It is the synthesis of the whole course, and quality across the entire process is what earns marks.

This guide gives an end-to-end overview of the project. The single dot-point page for the unit covers the same ground with practice questions; this overview ties it to the rest of the specification.

Analysis and design

The project begins with analysis: understanding the problem and its user, and writing clear, testable requirements and objectives. Design then plans how the solution will meet them - the interface (screen and report layouts), the data structures and database (tables, keys, an entity relationship diagram), the algorithms, and the program structure (classes and methods) - and prepares a test plan in advance. A thorough analysis and design prevent building the wrong solution, exactly as the systems development lifecycle prescribes.

Implementation and testing

Implementation builds the solution from the design in stages, with well-structured, readable code: sensible names, input validation, sound use of object oriented and event driven techniques, and helpful comments. Testing then runs the prepared test plan with normal, boundary and erroneous data, recording actual against expected results and correcting faults. Using all three data categories shows the solution handles limits and invalid input, not just typical cases.

Documentation and evaluation

The project finishes with the required documentation and an evaluation against the original requirements. The evaluation judges, objectively, how well the finished solution meets each requirement and objective set during analysis: which were met, which were not, and realistic limitations and improvements. This closes the loop from the targets set at the start to the judgement at the end.

How the course is applied

The project applies the rest of the specification. Object oriented design and event driven techniques from AS 1 and AS 2 build the solution; the database and SQL skills from A2 1 structure and query its data; and the systems discipline organises the work. A strong project combines all of these with clear requirements, a sensible design, readable validated code, thorough testing and an honest evaluation.

How this unit is examined

A typical profile for A2 2:

• Process understanding. Describing the stages of the development process and the purpose of each.
• Design and testing. Explaining the role of design artefacts, a test plan and the three data categories.
• Evaluation. Explaining how a solution is judged against its original requirements.
• Application. Showing how object oriented, event driven, database and systems skills come together in one solution.

Check your knowledge

A mix of recall and applied questions covering the unit. Attempt them under timed conditions, then check against the solutions.

1. Name the stages of the software development process applied in the project. (3 marks)
2. State two things a design should specify before implementation begins. (2 marks)
3. State the three categories of test data a test plan should include. (3 marks)
4. State what an evaluation of the finished solution should be measured against. (1 mark)
5. State two qualities of well-written implementation code. (2 marks)
6. Name one skill from A2 1 that the project applies. (1 mark)
7. Explain why testing with only normal data is insufficient. (2 marks)
8. State the purpose of writing testable requirements during analysis. (2 marks)