Overview

Assessment criteria

All 24 criteria, worded exactly as in the specification. The PO code (performance objective) is printed next to each criterion in the OCR sample assignment.

PassMeritDistinction
Task 1: Design
P1: Describe the solution overview for the software solution. (PO2)M1: Explain how the functional and non-functional requirements impact the design of the software solution. (PO2)D1: Explain how constraints impact the design for the software solution. (PO2)
P2: Describe the client requirements for the software solution. (PO2)M2: Explain how the software design documentation created allows the requirements of the SDS to be realised. (PO2)D2: Assess the software solution design in relation to the software design principles. (PO3)
P3: Create data structure and interface designs for the software solution. (PO4)M3: Justify the appropriateness of the testing. (PO3)
P4: Create data flow diagrams and algorithm designs for the software solution. (PO4)
P5: Describe how the software solution will be tested. (PO2)
Task 2: Create
P6: Create a user interface for the software solution. (PO4)M4: Use programming techniques to implement appropriate file manipulation in the software solution. (PO4)D3: Use programming techniques to implement appropriate encapsulation in the software solution. (PO4)
P7: Create the output(s) for the software solution. (PO4)M5: Use programming techniques to implement appropriate data structures in the software solution. (PO4)D4: Use programming techniques to implement appropriate searching and/or sorting in the software solution. (PO4)
P8: Use programming techniques to implement appropriate selection and iteration in the software solution. (PO4)M6: Use programming techniques to implement appropriate error handling in the software solution. (PO4)
P9: Use source code comments, indentation and version control to make the software solution maintainable. (PO4)
P10: Use appropriate naming conventions and data types in the software solution. (PO4)
Task 3: Test and review
P11: Test the software solution and document results. (PO4)M7: Analyse test results documenting any required remedial action. (PO3)D5: Discuss potential improvements and further development opportunities for the software solution. (PO3)
P12: Assess the suitability of the software solution for meeting the requirements. (PO3)

Grading: The specification calls the approach compensatory: the unit grade depends on the total number of criteria achieved, from any mix of Pass, Merit and Distinction. You do not need every Pass criterion to be awarded a Merit criterion.

All or nothing: A criterion is only awarded when all aspects of a criterion have been met in sufficient detail. If the work does not fully meet it, the assessor must not award that criterion. (Spec 5.3.5, introduction to the assessment criteria)

Scenario: Your centre gives you OCR's live assignment, which has its own client, data and required features. The 24 criteria are the same whatever the scenario, so the steps below apply to any brief. The first card in Task 1 shows how to read your scenario before you start.

Language: OCR does not name a programming language for F166. You use the one your centre has taught. The F166 revision notes show each programming technique in C#.

Examples marked Sample use OCR's published sample assignment scenario, Final Vinyl: a shop selling second hand vinyl records that wants software to store customers' details and a stock list, produce an invoice for each order and output the total value of sales for a week. Your scenario will ask for a different solution, so use the examples to see how a step works, not as content to copy.

Task 1

Designing the software solution

P1 P2 P3 P4 P5  M1 M2 M3  D1 D2

Sample assignment estimate: about 5 hours. Assesses Topic Areas 1, 2, 4 and 5. Evidence must include a Software Design Specification (SDS), Software Design Documentation (SDD) and written evidence.

Before you start

Read your scenario

Every later step depends on the scenario, so pull these seven things out of it first and keep the list next to you. Use the scenario's own words where it gives them.

FindSpec termsUsed inSample
The client and the problemTopic Area 2.1.1: solution overviewP1A shop selling second hand vinyl records that wants a new software solution for its orders
What the solution will doTopic Area 2.1.1: solution overview, functional requirementsP1, P2, M1Store customers' details; store a stock list; produce an invoice for each customer order; output the total value of sales for any given week
The data: every item the scenario says is recordedTopic Area 2.1.2: data structure designP3, M4, M5Customer name, address, telephone number, email address and a unique customer number; each record's ID, category, artist, title and price
The outputsTopic Area 2.1.2: algorithm designs for outputP4, P7An invoice; the weekly sales total
Rules and required featuresTopic Area 2.1.1: functional and non-functional requirementsP2, M1, M4, M6A customer can buy only one copy of each record; passwords; data entry error handling; backup of files
The user and the interfaceTopic Area 2.1.2: interface designP3, P6, M1A user with limited computer experience; every area reached from a central menu
Limits: anything that restricts what you build or howTopic Area 2.1.1: constraintsD1The solution is limited to the stated requirements

Documents: Task 1 produces two documents. The SDS says what the solution must do (Steps 1 to 4). The SDD holds the designs that show how it will be built (Steps 5 to 8). The testing description in Steps 9 and 10 is written evidence.

Common mistake: Designing for the sample scenario, or adding features the brief did not ask for. Every feature the client names should become a requirement in Step 2.
Step 1
P1

Describe the solution overview

Students must extract the specific objectives of the software solution from the scenario and describe them in a Software Design Specification (SDS).OCR Spec 5.3.5, guidance for P1

The solution overview is the first section of the SDS (Topic Area 2.1.1). State who the client is, the problem, and then each objective: one thing the solution will do. Take them from the scenario, one objective per sentence or list item.

Describe: "Describe" means giving an account with the relevant characteristics. For each objective, say what the solution will do and what that involves, not only its name.

Common mistake: Writing the overview as a separate document. The guidance says the objectives are described in an SDS, so set the SDS up first, with a title, author, date, version and numbered sections.
Step 2
P2

Describe the client requirements

Students must describe the client requirements in a Software Design Specification (SDS) expanding the descriptions into specific requirements which can be used as criteria to review against in Task 3.OCR Spec 5.3.5, guidance for P2

Go through what you found in the scenario and write each thing the client asks for as a numbered requirement. Then expand it until it can be checked with a yes or no. Split them into functional requirements (what the solution must do) and non-functional requirements (how well it must do it), the next two sections of the SDS in Topic Area 2.1.1.

Sample: all areas of the software solution need to be accessible from a central menu becomes "NFR1: every function can be reached from the main menu, and every screen has an option that returns to it".

Common mistake: Copying the scenario back out. A requirement that cannot be checked cannot be reviewed against in Step 23.
Step 3
M1

Explain how the requirements impact the design

M1 is an extension of P1 and P2. Students must explain how the functional and non-functional requirements of the solution will influence the design of the software solution.OCR Spec 5.3.5, guidance for M1

Take the requirements from Step 2 and, for each one or each group, say what it means the design must contain. Functional requirements lead to data that must be stored, processes, inputs and outputs. Non-functional requirements shape how those are designed: the interface style, validation, security and backup.

Explain: "Explain" means giving reasons. Use the pattern "because the client needs X, the design will Y". Cover both kinds of requirement; the criterion names both.

Step 4
D1

Explain how constraints impact the design

Students must consider at least three potential constraints and explain how they would impact the design of the software solution.OCR Spec 5.3.5, guidance for D1

Constraints are the last section of the SDS. Topic Area 2.1.1 gives ten examples: audience, budget, client requirements, external dependencies, hardware limitations, industry standards, language limitations, organisational policies, technical requirements and time. Choose at least three that apply to your scenario and to how you are working.

For each one, name the constraint, say where it comes from, and explain what it changes in the design.

Common mistake: Listing constraints without the impact. "Time is a constraint" earns nothing; what the time limit makes you design differently is the explanation.
Step 5
P3

Create the data structure and interface designs

The data structure design(s) must show how the data will be stored. Students must use at least one of the software design tools in Topic Area 2.1.2. The designs must contain enough detail for them to be interpreted by someone who hasn't seen them before.OCR Spec 5.3.5, guidance for P3

Data structure design: For each set of data you found in the scenario, a table of its fields with the data type, size or format and validation for each, the file it is saved in, and how the sets are linked. Add the structures the program will hold the data in while it runs.

Interface design: The Topic Area 2.1.2 tools are a navigation diagram, wireframes and visualisation diagrams. A navigation diagram shows how the user reaches each function; a wireframe for each screen or menu shows its layout, prompts and messages. The spec's interface design examples also include user help, error messages and command labelling.

Check: Read each design as if you had never seen the scenario. Do this yourself: the assignment is completed under supervision, so the designs cannot be shown to other people.

Common mistake: Fields with no data types. The design has to show how the data will be stored, and Step 19 (P10) then uses those data types in the code.
Step 6
P4

Create the data flow diagrams and algorithm designs

Students must create data flow diagrams to show how data will flow through the software solution. Students must use at least one of the software design tools in Topic Area 2.1.2 to create algorithm designs for the software solution.OCR Spec 5.3.5, guidance for P4

Data flow diagrams: Topic Area 2.1.2 lists Level 0 and Level 1. Level 0 shows the whole solution as one process with its external entities. Level 1 breaks it into the main processes and adds the data stores, which should match the files in your data structure design. Label every flow.

Algorithm designs: The tools are flowcharts and pseudocode. The spec lists algorithm designs for input, process, storage and output, so design at least one of each: for example validating an entry, a calculation, saving and loading a file, and producing an output.

Common mistake: A data flow diagram drawn as a flowchart, with decisions and loops. It shows data moving between entities, processes and stores, not the order of steps.
Step 7
M2

Explain how the designs allow the SDS requirements to be realised

Students must explain how each of the designs created in P3 and P4 (data structure, interface, data flow and algorithms) relate to the requirements detailed in the SDS.OCR Spec 5.3.5, guidance for M2

Four designs, so four parts to the explanation. For each design, point to the numbered requirements it delivers and say how. A table with a row per requirement and a column per design is one way to make sure nothing is missed, with the explanation written underneath.

Check: A requirement that no design covers is a gap in the designs. Go back to Step 5 or 6 and add it.

Step 8
D2

Assess the design against the software design principles

Students must assess the extent to which the software design principles in Topic Area 1.1 have been applied to the software solution design. The criterion is achieved if students consider at least three of the software design principles.OCR Spec 5.3.5, guidance for D2

The Topic Area 1.1 principles: stepwise refinement, abstraction (functional, data, control), decomposition, modularity, object-orientated programming, maintainability and encapsulation. Choose at least three and, for each, show where your design applies it and how fully.

Assess: "Assess" means a reasoned judgement informed by facts. Say where a principle has been applied well, and where it has only partly been applied or could have been used more.

Step 9
P5

Describe how the solution will be tested

Students must describe the testing methods and testing types they will use to test the software solution and the elements of the software solution they intend to test.OCR Spec 5.3.5, guidance for P5

Three parts: Methods: dry run/trace table, iterative, test plan. Types: requirements testing, component testing, integration testing, system testing. Elements: input, output, navigation, error handling, data storage. All three lists are in Topic Area 4.1.

Template: Use the test table in your live assignment if it has one. OCR's sample assignment includes a test table with these columns: test number, test type, test description, test data, expected result, actual result, remedial action required. Writing the first five columns now gives you the test plan.

Step 10
M3

Justify the testing approach

Students must justify the approach to testing detailed in P5.OCR Spec 5.3.5, guidance for M3

Give a reason for each method, type and element you chose, linked to the solution and its requirements. Topic Area 4.1 covers when it is appropriate to use each testing type and how and why to test iteratively.

Justify: "Justify" means giving valid reasons. "Requirements testing checks each numbered requirement in the SDS, so the review in Task 3 has evidence for every one" is a reason; "testing is important" is not.

Task 2

Creating the software solution

P6 P7 P8 P9 P10  M4 M5 M6  D3 D4

Sample assignment estimate: about 8 hours. Assesses Topic Areas 1 and 3. Evidence must include the source code and the final software solution, either in a format that can be used without installing specialist software or as video/screen recordings of it being demonstrated.

Before you start

What the assessor needs to see

Ideally, students will create the software solution designed in Task 1. However, if students deviate from the design(s) they should not be penalised when assessing Task 2.OCR Spec 5.3.5, guidance for Task 2

Format: The assessor must be able to see the final solution working, so submit a version that runs without specialist software, or recordings of it being demonstrated. A recording that walks through every menu option also shows the interface, outputs and error handling in one place.

Source code: For nine of the ten criteria in this task, the guidance says the source code or the final solution will be sufficient evidence. Hand in all of it, in a form that keeps the indentation.

Version control: Start the version log in your first session (Step 20). It cannot be filled in properly afterwards.

Step 11
P6

Create the user interface

Students must create a user interface for the software solution. The final software solution will be sufficient evidence for this assessment criterion.OCR Spec 5.3.5, guidance for P6

Build the interface you designed in Step 5: the menus or screens, prompts, labels and messages. A text menu in a console program is a user interface. Match the navigation diagram, so every function can be reached and left again.

Sample: the scenario asks for every area to be reached from a central menu, for a user with limited computer experience, so the menu wording and prompts matter.

Step 12
P7

Create the outputs

Students must create the output(s) for the software solution. The final software solution will be sufficient evidence for this assessment criterion.OCR Spec 5.3.5, guidance for P7

The outputs are the ones you found when reading the scenario. Each should contain the right data, correctly calculated, in a clear layout. If the scenario shows an example of an output, compare yours with it.

Common mistake: Building the data entry and running out of time before the outputs. They are a Pass criterion and are often what the client actually asked for.
Step 13
P8

Use selection and iteration

Students must use the programming techniques in Topic Area 3.1 (as required) to add selection and iteration to the software solution, so it functions as intended.OCR Spec 5.3.5, guidance for P8

Selection (Topic Area 3.1.3): If Then Else, Else If, Case/Switch. Iteration (3.1.4): fixed loops and conditional loops, pre-condition or post condition. Both are needed. A menu that repeats until the user chooses to exit, with a branch for each option, uses the two together.

"Appropriate" means the construct fits the job: a fixed loop when the number of repeats is known, a conditional loop when it depends on the data or the user.

Step 14
M5

Use data structures

Students must use the programming techniques in Topic Area 3.1 (as required) to create the data structures for the software solution, so it functions as intended.OCR Spec 5.3.5, guidance for M5

Topic Area 3.1.7 lists arrays, linked lists, stacks and queues. Build the structures from your data structure design in Step 5, and use them to hold the data while the program runs.

"Appropriate" means the structure suits the data: whether its size is fixed or changes, and the order in which items are needed.

Step 15
M4

Use file manipulation

Students must use the programming techniques in Topic Area 3.1 (as required) to add file manipulation to the software solution, so it functions as intended.OCR Spec 5.3.5, guidance for M4

Topic Area 3.1.6: opening and closing files, reading from and writing to files, and managing files (create, copy, delete and backup). Data the scenario says is stored should still be there after the program is closed and opened again.

Sample: the scenario requires backup of files, so that solution needs a way to make a backup copy as well as saving and loading.

Step 16
M6

Use error handling

Students must use the programming techniques in Topic Area 3.1 (as required) to add error handling during user input to prevent the software solution from unexpected and unintended closure.OCR Spec 5.3.5, guidance for M6

Topic Area 3.1.8: try and exception, and validation rules. Go through every point where the user types something and make sure that text in a number field, an empty entry or an out-of-range value gives a message and another attempt, not a crash.

Common mistake: Handling errors on one input only. The guidance is about user input in general, and the tests in Step 21 will try the others.
Step 17
D3

Use encapsulation

Students must use the programming techniques in Topic Area 3.1 (as required) to add encapsulation that improves the efficiency of the software solution.OCR Spec 5.3.5, guidance for D3

Topic Area 3.1.5: modules, procedures, functions, classes with properties and methods, libraries, parameter passing and return values (byref and byval), getters and setters.

The guidance asks for encapsulation that improves efficiency. Code that would otherwise be repeated (validating a number, loading a file, printing a heading) written once as a function with parameters and called wherever it is needed is the direct way to show that. A class for each kind of record does the same for data.

Common mistake: One long main routine with everything in it, or functions that are each called only once and pass nothing. Neither shows encapsulation improving the solution.
Step 18
D4

Use searching and/or sorting

Students must use the programming techniques in Topic Area 3.1 (as required) to add searching and/or sorting to the software solution, so it functions as intended.OCR Spec 5.3.5, guidance for D4

The criterion says "and/or", so one of the two can meet it. It has to be something the solution needs: finding one item in the stored data from a value the user enters, or putting a list in order for an output.

Step 19
P10

Use naming conventions and data types

Students must use a consistent and understandable naming convention for variables, constants, files, data structures and encapsulation.OCR Spec 5.3.5, guidance for P10

Topic Area 3.1.1 lists camel case and kebab case, and the data types integer, floating point, string and Boolean. Pick a convention for each kind of name and keep to it in every part of the code. The guidance covers five kinds of name: variables, constants, files, data structures, and the procedures, functions and classes you write.

Data types: Each variable should have the type its data needs, matching your data structure design: a whole-number type for a count, a floating point type for a price, a Boolean for a yes or no.

Common mistake: Names such as x, temp2 or data1. The test in the guidance is whether someone who hasn't seen the code before can interpret them.
Step 20
P9

Make the code maintainable: comments, indentation and version control

For the code to be maintainable, someone who hasn't seen it before must be able to be interpret it. This assessment criterion could be evidenced by the source code from the final software solution and screen shots or photographs showing the use of version control.OCR Spec 5.3.5, guidance for P9

The criterion has three parts, all from Topic Area 3.2, and all three are needed:

PartSpec contentEvidence
Source code commentsProgram headers, an overview of the purpose of each code segment, syntax commentsThe source code
IndentationOne consistent source code indentation styleThe source code
Version controlVersion number, date amended, amended by, amendsScreenshots or photographs of the version log or tool
Common mistake: Leaving version control to the end. One saved version with a made-up history is not use of version control; record each version as you make it.

Task 3

Testing and reviewing the software solution

P11 P12  M7  D5

Sample assignment estimate: about 2 hours. Assesses Topic Areas 4 and 5. Evidence must include documented test results and written evidence.

Step 21
P11

Test the solution and document the results

Students must have evidence of the actual test results for example screen shots, photographs or video/screen recordings.OCR Spec 5.3.5, guidance for P11

Run the tests planned in Step 9 and fill in the actual result for each. OCR recommends its test plan template, and a different appropriate template must not be penalised. If your testing differs from what you described in Task 1, the guidance says that should not be penalised either.

Test numberTest typeTest descriptionTest dataExpected resultActual resultRemedial action required
1ComponentPrice input rejects textabcError message shown; prompt repeatsAs expected (screenshot 1)None
2SystemCustomer added, program closed and reopenedOne new customerCustomer is still listedCustomer list is empty (screenshot 2)Call the save routine when a customer is added
The two rows are an illustration for the sample scenario, not a model answer.
Step 22
M7

Analyse the results and document remedial action

Students must analyse the test results generated in P11 and explain any remedial action required to resolve the issues found during testing. Students are not expected to fix errors found in the software solution during final testing.OCR Spec 5.3.5, guidance for M7

Analyse: For each failed or partly passed test: what went wrong, why, its effect on the user, and the fix needed. Look for patterns, such as several failures that come from one missing validation routine.

You do not have to carry the fixes out. The marks are for the analysis and the explanation of what is required.

Step 23
P12

Assess how well the solution meets the requirements

Students must assess the suitability of the software solution for meeting the requirements in Topic Area 5.1.OCR Spec 5.3.5, guidance for P12

The Topic Area 5.1 list: suitability for meeting the client requirements, functional requirements and non-functional requirements, then maintainability and robustness. Work through your numbered requirements from Step 2 and judge each as met, partly met or not met, with evidence from testing. Then judge how maintainable the code is and how well it copes with invalid input.

Common mistake: Stopping at the requirements. Maintainability and robustness are in the 5.1 list too.
Step 24
D5

Discuss improvements and further development

Students must discuss potential improvements and further developments to the software solution. Successful achievement of P12 and/or M7 could support this.OCR Spec 5.3.5, guidance for D5

Improvements from Topic Area 5.2.1: code efficiency, HCI design principles, HCI accessibility principles, data exchange and security, considered against the constraints (programming constructs, language chosen, skills of the developer, development environment). Further developments from 5.2.2: portability of the solution and code reusability.

Discuss: "Discuss" means presenting and evaluating points to reach a reasoned judgement. Weigh each improvement's benefit against its cost and effort, and say which should come first. Cover both improvements and further development.

Reference

Command words

The verbs in the F166 criteria, with OCR's definitions from the NEA command words table in the sample assignment.

WordOCR definitionCriteria
DescribeGive an account that includes the relevant characteristics, qualities or eventsP1, P2, P5
ExplainGive reasons for and/or causes of something. Make something clear by describing and/or giving informationM1, M2, D1
JustifyGive valid reasons for offering an opinion or reaching a conclusionM3
AssessOffer a reasoned judgement of the standard or quality of situations or skills. The reasoned judgement is informed by relevant factsD2, P12
AnalyseSeparate or break down information into parts and identify their characteristics or elements. Explain the different elements of a topic or argument and make reasoned comments. Explain the impacts of actions using a logical chain of reasoningM7
DiscussPresent, analyse and evaluate relevant points (for example, for/against an argument) to make a reasoned judgementD5
Create, Test, UseNot defined in the table: OCR says other command words are commonly used words whose meaning will be made clear from the context in which they are usedP3, P4, P6 to P11, M4 to M6, D3, D4