Based on F454 from the OCR Computing A Level the project is a substantial piece of work, requiring analysis and design over an extended period of time, which is organised, evaluated and presented in a report.Candidates choose, in conjunction with their teacher, a well-defined user-driven problem of an appropriate size which enables them to demonstrate their skills in Analysis, Design, Software Development, Testing, Implementation, Documentation and Evaluation, and their interrelation, and to give a completed overall system that solves the problem.
How does it fit in with the rest of the course?
- 20% of the total Advanced GCE marks
- 80 marks
Marking GridYr13 Project Mark Scheme is the marking grid we use for the OCR Computing ALevel (circa 2012) to ensure that all the marks are applied fairly for all students. Roughly speaking:
- Missing means this aspect of the report is missing or not found when marking. Ensuring you put in clear headings for each section and using headers/footers/page numbers will help prevent this.
- Vague will indicate that you have attempted a section but that it lacks accuracy, detail and/or clarity. Make sure you understand what is being asked for and know how to achieve it.
- Good will be present and on the whole correct to the appropriate level of detail.
- Excellent will leave the examiner in no doubt about what you are trying to say/achieve.
Explanation of the problem to be solved, the user’s requirements and how they were obtained. Evidence of the development of a requirement specification and a clear statement of requirements.
- Define a task
- Research the task and needs of the end-user(s)
- Record findings
- Analyse findings
- Project plan including specification of the requirements:
DesignA Detailed system design including
- data structures
- input-output format
- processes involved
- Specify the objectives relating them to the requirements specification
- Input design
- Output design
- Design and test plan and test data
- Data structures/variables
- Test algorithms
Development and Testing
Develop a software solution and, using the test plan developed in Part 2: Design, show that the system works with valid, invalid and borderline data (or, if it does not, under which circumstances it fails) Test plan should be clearly cross-referenced to evidence that the system has been tested during development and implementation. The development and testing section should include:
- Evidence of user testing
- Software development
- Alpha testing
- Response to the results of testing
- Beta testing
- Response to the results of beta testing
- Modularisation of code
- Code documentation
- Use of modules, data structures and objects
- In-code documentation
- Code structure
- Applying the test plan and data
The software solution should be self documenting with suitable on-screen help and support for the end user(s). All necessary supporting documentation required to enable the end user to make effective use of the solution.
Discussion of the degree of success in meeting the original objectives as specified in the requirements specification including an evaluation of the project management – to include an evaluation of the ease of the use of the package, acceptability to the users, the choice of task, the project plan and desirable extensions/modifications
- Evaluate results against the requirement specification showing that the objectives in Topic 2: Design have been satisfied
- Evaluate the project management
- Evaluate user responses
- Identify the good and bad points of the final system, including any limitations and necessary extensions or modifications to the system