Project Booklet Differences Identified
Project Booklet Differences Identified
The project is a substantial piece of work which assesses a variety of different skills including the development and demonstration of
computational thought processes.
Students will need to choose a well defined user-driven problem. The choice of project must enable students to:
meet all assessment requirements as contained in the specification
use an appropriate programming language which is non-trivial and has a substantial coded element
solve a problem sensibly within the constraints of resources available
facilitate the successful completion of a whole task from its definition to its acceptance and evaluation by that user
involve all elements of the skills of analysis, design, development and evaluation.
Evidence Generation: it is important that students establish thorough and robust working practices at an early stage. The projects should contain
as standard the following:
Title
Contents list
Description of investigation
Justification of investigation
Analysis, design and methods used
Evaluation
Bibliography
Pages numbered
Appropriate annotated evidence should be used to support the report – eg screen dumps or photographs taken of screen layouts. It is important
that students generate their own individual, authentic evidence to show that they have met key assessment criteria. Any evidence submitted to
demonstrate the development of solution must be able to be assessed without the use of any specific hardware or software.
Students will be expected to analyse, design, develop, test, evaluate and document a program written in a suitable programming language. The
underlying approach to the project is to apply the principles of computational thinking to a practical coding problem. Students are expected to
apply appropriate principles from an agile development approach to the project development.
While the project assessment criteria are organised into specific categories, it is anticipated the final report will document the agile development
process, and elements for each of the assessment categories will appear throughout the report.
The programming project will be submitted in the form of a report that will contain the solution to a problem, selected by the student and school,
written in a suitable programming language.
3.1. Analysis of the problem (10 marks) a
3.1.1 Problem identification 3.2.3 Describe the approach to testing
Describe and justify the features that make the problem Identify the test data to be used during the iterative
solvable by computational methods development and post development phases and justify the
Explain why the problem is amenable to a computational choice of this test data.
approach. 3.3 Developing the solution (25 marks)
3.1.2 Stakeholders 3.3.1 Iterative development process
Identify and describe those who will have an interest in the Provide annotated evidence of each stage of the iterative
solution explaining how the solution is appropriate to their development process justifying any decision made.
needs (this may be named individuals, groups or persona Provide annotated evidence of prototype solutions
that describes the target end user). justifying any decision made.
3.1.3 Research the problem 3.3.2 Testing to inform development
Research the problem and solutions to similar problems to Provide annotated evidence for testing at each stage
identify and justify suitable approaches to a solution. justifying the reason for the test.
Describe the essential features of a computational solution Provide annotated evidence of any remedial actions taken
explaining these choices. justifying the decision made.
Explain the limitations of the proposed solution. 3.4 Evaluation (20 marks)
3.1.4 Specify the proposed solution 3.4.1 Testing to inform evaluation
Specify and justify the solution requirements including Provide annotated evidence of testing the solution of
hardware and software configuration (if appropriate). robustness at the end of the development process.
Identify and justify measurable success criteria for the Provide annotated evidence of usability testing (user
proposed solution. feedback).
3.2 Design of the solution (15 marks) 3.4.2 Success of the solution
3.2.1 Decompose the problem Use the test evidence from the development and post
Break down the problem into smaller parts suitable for development process to evaluate the solution against the
computational solutions justifying any decisions made. success criteria from the analysis.
3.2.2 Describe the solution 3.4.3 Describe the final product
Explain and justify the structure of the solution. Provide annotated evidence of the usability features from
Describe the parts of the solution using algorithms the design, commenting on their effectiveness.
justifying how these algorithms form a complete solution to 3.4.4 Maintenance and development
the problem. Discuss the maintainability of the solution.
Describe usability features to be included in the solution. Discuss potential further development of the solution.
Identify key variables / data structures / classes justifying
choices and any necessary validation.
3.1. Analysis of the problem (10 marks)
3.1.2 Stakeholders
Identify and describe those who will have an interest in the solution explaining how the solution is appropriate to their needs (this may
be named individuals, groups or persona that describes the target end user).