0% found this document useful (0 votes)
51 views6 pages

Computing Project Assessment Grid

This document outlines the criteria for evaluating a computer science project at the A2 level. It provides descriptors for assessing students' work on four key elements: analysis, design, development, and iterative development of a coded solution. For each element, it lists point ranges and descriptions of what students would need to demonstrate to earn points in areas like identifying problems, requirements, features of the solution, testing, and providing evidence of an iterative coding process. The highest points are awarded for thoroughly researching the problem, systematically breaking it down, justifying design choices, and relating work to a thorough iterative development process.

Uploaded by

olufemimledu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
51 views6 pages

Computing Project Assessment Grid

This document outlines the criteria for evaluating a computer science project at the A2 level. It provides descriptors for assessing students' work on four key elements: analysis, design, development, and iterative development of a coded solution. For each element, it lists point ranges and descriptions of what students would need to demonstrate to earn points in areas like identifying problems, requirements, features of the solution, testing, and providing evidence of an iterative coding process. The highest points are awarded for thoroughly researching the problem, systematically breaking it down, justifying design choices, and relating work to a thorough iterative development process.

Uploaded by

olufemimledu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

A2 Level – Computer Science Project

Analysis (maximum 10 marks)


# 1–2 marks 3–5 marks 6–8 marks 9–10 marks
1 Identified some features that make the Described the features that make the Described the features that make the Described and justified the features
. problem solvable by computational problem solvable by computational problem solvable by computational that make the problem solvable by
methods. methods. methods and why it is amenable to a computational methods, explaining
computational approach. why it is amenable to a computational
approach.
2 Identified suitable stakeholders for the Identified suitable stakeholders for the Identified suitable stakeholders for the Identified suitable stakeholders for the
. project and described them and some project and described how they will project and described them and how project and described them explaining
of their requirements. make use of the proposed solution. they will make use of the proposed how they will make use of the
solution and why it is appropriate to proposed solution and why it is
their needs. appropriate to their needs.
3 Identified some appropriate features to Researched the problem looking at Researched the problem in depth Researched the problem in depth
. incorporate into their solution. existing solutions to similar problems looking at existing solutions to similar looking at existing solutions to similar
identifying some appropriate features problems identifying and describing problems, identifying and justifying
to incorporate into their solution. suitable approaches based on this suitable approaches based on this
research. research.
3 Identified some features of the Identified the essential features of the Identified and described the essential Identified the essential features of the
. proposed computational solution. proposed computational solution. features of the proposed proposed computational solution
computational solution. explaining these choices.
4 Identified some limitations of the Identified and described some Identified and explained any limitations Identified and explained with
. proposed solution. limitations of the proposed solution. of the proposed solution. justification any limitations of the
proposed solution.
6 Identified some requirements for the Identified most requirements for the Specified the requirements for the Specified and justified the
. solution. solution. solution including (as appropriate) any requirements for the solution including
hardware and software requirements. (as appropriate) any hardware and
software requirements.
7 Identified some success criteria for the Identified some measurable success Identified measurable success criteria Identified and justified measurable
. proposed solution. criteria for the proposed solution. for the proposed solution. success criteria for the proposed
solution.
Design (maximum 15 marks)
# 1–4 marks 5–8 marks 9–12 marks 13–15 marks
1 Described elements of the solution Broken the problem down Broken the problem down Broken the problem down
. using algorithms. systematically into a series of smaller systematically into a series of smaller systematically into a series of smaller
problems suitable for computational problems suitable for computational problems suitable for computational
solutions describing the process. solutions explaining the process. solutions, explaining and justifying the
process.
2 Described some usability features to be Defined the structure of the solution to Defined in detail the structure of the Defined in detail the structure of the
. included in the solution. be developed. solution to be developed. solution to be developed.

3 Identified the key variables / data Described the solution fully using Described the solution fully using Described the solution fully using
. structures / classes (as appropriate to appropriate and accurate algorithms. appropriate and accurate algorithms appropriate and accurate algorithms
the proposed solution). explaining how these algorithms form a justifying how these algorithms form a
complete solution to the problem. complete solution to the problem.

3 Described the usability features to be Described, explaining choices made, Described, justifying choices made, the
. included in the solution. the usability features to be included in usability features to be included in the
the solution. solution.
4 Identified the key variables / data Identified and justified the key variables Identified and justified the key variables
. structures / classes (as appropriate to / data structures / classes (as / data structures / classes (as
the proposed solution) and any appropriate to the proposed solution) appropriate to the proposed solution)
necessary validation. explaining any necessary validation. justifying and explaining any necessary
validation.
6 Identified some test data to be used Identified the test data to be used Identified and justified the test data to Identified and justified the test data to
. during the iterative or post during the iterative development of the be used during the iterative be used during the iterative
development phase of the process. solution. development of the solution. development of the solution.
7 Identified any further data to be used in Identified and justified any further data Identified and justified any further data
. the post development phase. to be used in the post development to be used in the post development
phase. phase.
Development (maximum 25 marks)
Iterative development of a coded solution (maximum 15 marks)
# 1–4 marks 5–8 marks 9–12 marks 13–15 marks
1 Provided evidence of some iterative Provided evidence for most stages of Provided evidence of each stage of the Provided evidence of each stage of the
. development for a coded solution. the iterative development process for a iterative development process for a iterative development process for a
coded solution describing what they did coded solution relating this to the coded solution relating this to the
at each stage. break down of the problem from the break down of the problem from the
analysis stage and explaining what they analysis stage and explaining what they
did at each stage. did and justifying why.
2 Solution may be linear. Solution will have some structure. Provided evidence of some prototype Provided evidence of prototype
. versions of their solution. versions of their solution for each stage
of the process.
3 Code may be inefficient. The solution will be modular in nature. The solution will be well structured and
. modular in nature.

4 Code may not be annotated Code will be briefly annotated to Code will be annotated to explain all Code will be annotated to aid future
. appropriately. explain key components. key components. maintenance of the system.

5 Variable names may be inappropriate. Some variable and/or structure names Most variables and structures will be All variables and structures will be
. will be largely appropriate. appropriately named. appropriately named.

6 There will be little or no evidence of There will be evidence of some basic There will be evidence of validation for There will be evidence of validation for
. validation. validation. most key elements of the solution. all key elements of the solution.

7 There will be little evidence of review There will be evidence that the The development will show review at The development will show review at
. during the development. development was reviewed at some most key stages in the process. all key stages in the process.
stage during the process.
Testing to inform development (maximum 10 marks)
# 1–2 marks 3–5 marks 6–8 marks 9–10 marks
1 Provided some evidence of testing Provided some evidence of testing Provided evidence of testing at most Provided evidence of testing at each
. during the iterative development during the iterative development stages of the iterative development stage of the iterative development
process. process. process. process.
2 Provided evidence of some failed tests Provided evidence of some failed tests Provided evidence of any failed tests
. and the remedial actions taken. and the remedial actions taken with and the remedial actions taken with full
some explanation of the actions taken. justification for any actions taken.
Evaluation (maximum 20 marks)
Testing to inform evaluation (maximum 5 marks)
# 1 mark 2 marks 3–4 marks 5 marks
1 Provided evidence of some post Provided evidence of final product Provided annotated evidence of post Provided annotated evidence of post
. development testing. testing for function. development testing for function. development testing for function and
robustness.
2 Provided annotated evidence for Provided annotated evidence for
. usability testing. usability testing.

Evaluation of solution (maximum 15 marks)


# 1–4 marks 5–8 marks 9–12 marks 13–15 marks
1 Commented on the success or failure of Cross referenced some of the test Used the test evidence to cross Used the test evidence to cross
. the solution with some reference to evidence with the success criteria and reference with the success criteria to reference with the success criteria to
test data. commented on the success or evaluate the solution identifying evaluate the solution explain how the
otherwise of the solution. whether the criteria have been met, evidence shows that the criteria has
partially met or unmet. been fully, partially or not met in each
case.
2 The information is basic and Provided comments on how any Provided comments on how any
. communicated in an unstructured way. partially or not met criteria could be partially or unmet criteria could be
addressed in further development. addressed in further development.
3 Provided evidence of usability features. Provided evidence of the usability Provided evidence of the usability
. features. features justifying their success, partial
success or failure as effective usability
features.
4 Provided comments on how any issues
. with partially or unmet usability
features could be addressed in further
development.
5 Considered maintenance issues and Considered maintenance issues and
. limitations of the solution. limitations of the solution.

6 Identified some limitations on the Described how the program could be


. solution. developed to deal with limitations of
potential improvements / changes.
7 The information is supported by limited The information has some relevance There is a line of reasoning presented There is a well developed line of
. evidence and the relationship to the and is presented with limited structure. with some structure. The information reasoning which is clear and logically
evidence may not be clear. The information is supported by limited presented is in the most part relevant structured. The information presented
evidence. and supported by some evidence. is relevant and substantiated.

You might also like