WJEC A2 Unit 5: Programmed Solution
to a Problem

You describe your project to others, identify its limitations, and use feedback to sharpen your understanding of the problem. This is an oral or documented discussion, not just a written paragraph.

• Describe the broad aims of the project to peers or your teacher, using appropriate technical vocabulary.
• Identify and describe the possible limitations of a solution to the problem in detail.
• Consider feedback from others and use it to refine your understanding and proposed solution.

A thorough investigation of the existing system using a variety of methods, including desk research into similar solutions and a detailed look at stakeholders, data, processing, and outputs.

• Investigate the current system using interviews, questionnaires, observation, or document analysis.
• Research existing solutions to similar problems and identify features to include in your own solution.
• Identify all stakeholders and describe their requirements for the proposed system.
• Analyse data collected for input and processing by the current system.
• Identify and describe all outputs from the current system.
• Consider the limitations of the current system.
• Produce a working specification that summarises the purpose of the project.
• Justify the methods to be used in your solution.
• Set measurable objectives and success criteria for the proposed system.

Full documentation of the proposed solution before you write any final code. This section rewards thorough, clear design documentation that a competent third party could implement.

• Break the problem into sub-problems and explain the links between them and your objectives.
• Design and document all input and output interfaces, including screen layouts and reports.
• Design all data structures and describe methods of access.
• Ensure all data entered is valid, with validation rules documented.
• Design processing routines using a structured convention such as pseudocode or flowcharts.
• Describe the relationships between data and the processes that manipulate it.

A working early version of your system covering a justified subset of the full solution, built with realistic data and evaluated honestly.

• Justify which areas of the problem are included in the prototype and explain why others are omitted.
• Produce a range of screens and outputs for the chosen prototype areas.
• Create a functioning system that carries out all chosen processes using realistic data.
• Evaluate the prototype, identifying its good features, shortcomings, and specific improvements needed.

After evaluating your prototype you obtain feedback from a competent third party and revise your design documentation before building the final system.

• Obtain feedback on the prototype from a competent third party (not just a friend; someone who can assess the technical quality).
• Describe the feedback received and explain its implications for redesign.
• Revise input, output, data structures, and processing routines in response to the feedback.
• Justify any feedback suggestions that you have chosen not to implement.
• Produce fully updated processing routines in a recognised convention, in sufficient detail for implementation.

The largest section in the unit. You refine your prototype into a complete, functional, well-structured, and well-annotated solution. The code must be original and submitted with annotated listings.

• Refine the prototype using the amended design documentation.
• Produce a functioning solution that meets most objectives and is suitable for its audience and purpose.
• Make effective use of the programming language, including user-defined routines.
• Create a well-structured, modular solution using local variables and minimising global variables.
• Produce a well-structured data model; better candidates will normalise to third normal form.
• Write fully self-documenting code with annotation to allow a third party to maintain the solution.
• Implement validation for all key components; better candidates will use exception handling.
• Document all variables and data structures used.
• Provide a completed user interface with a full description of the features that make it fit for audience and purpose.

Testing is split into two sub-sections: developmental testing (5 marks) and final system testing (10 marks). Both require documented evidence, not just a table of results.

• Provide evidence of testing at each stage of development, not just at the end.
• Document all problems encountered during development and the actions taken to fix them.

• Design a comprehensive test plan covering every function of the system.
• Test each function with typical, extreme, and invalid data.
• Produce annotated test runs with commentaries on every outcome.
• Include specific suggestions to refine the system based on test results.

A reflective, analytical conclusion to the entire project. Band 3 requires you to use specialist vocabulary correctly and write virtually error-free English throughout.

• Evaluate the effectiveness of the programming language used, justifying the tools and techniques chosen.
• Compare your completed solution with similar commercially available systems.
• Identify successful features and shortcomings of your solution, and describe significant potential improvements.
• Evaluate your own strengths and weaknesses in the design and development process.
• Describe specific changes of approach you would adopt if tackling a similar problem in future.