Community resourceWorksheet

OCR H446 1.2.3 Software Development exam transition

Part 6 of 6 · H446 1.2.3 · Software development

This assessment closes H446 1.2.3, worked independently and without checking answers along the way. Methodology questions in examination phrasing come first, then tracing, fault diagnosis and full algorithm construction, including the file effects candidates most often leave out.

Students will:

  • answer methodology questions to the command word and the evidence given
  • justify waterfall, spiral, agile with XP, or RAD for contrasting project briefs
  • discuss competing approaches for one project and commit to a recommendation
  • trace a supplied algorithm and explain why a counted result differs from the number of inputs
  • write code that calls a supplied function, stores every returned value and writes to a file

Inside: 2 explanation cells, 1 multiple-choice question, 2 fill-in-the-blanks cells, 9 written answers and 1 trace table. 66 marks, about 60 to 75 minutes.

Series: H446 1.2.3 · Software development, part 6 of 6.

Shared by Coding PathwayVerified teacher

  • 15 cells
  • About 60 minutes
  • CC BY-SA 4.0
  • Shared 31 Aug 2026
  • Updated 3 Sept 2026

Preview

The whole resource, exactly as a class sees it. Answers and marking are held back.

Software Development examination transition

Complete this assessment independently and without checking answers as you go. Use the command words, supplied evidence and context carefully; correctness is held where the platform supports it.

Multiple choice1 mark

Which description is accurate?

  • ASpiral uses risk analysis to decide work in each repeated cycle
  • BWaterfall is defined by daily user-reviewed prototypes
  • CRAD means writing final code without evaluation
  • DXP is unrelated to agile development
Fill in the blanks4 marks
Waterfall has planned gap 1. Agile delivers small gap 2 and reprioritises from feedback. XP supplies engineering gap 3. RAD refines rapid gap 4 with users.
  • stages
  • increments
  • practices
  • prototypes
  • risks
Written answer4 marks

Give two paired differences between waterfall and spiral.

Compare the same criterion on both sides. A pair must say more than linear versus iterative.

Students type their answer here.

Written answer5 marks

A university is replacing a stable payroll system. Rules and acceptance tests are contractually agreed, and complete audit documents are required. Explain one benefit and one drawback of waterfall.

Apply the exact project evidence.

Students type their answer here.

Written answer6 marks

A drone-control project uses an unproven sensor, has severe failure consequences and expensive field trials. Explain why spiral may be suitable and why it still creates a management cost.

Use the four cycle responsibilities and the supplied risks.

Students type their answer here.

Written answer7 marks

A community app has changing priorities, a representative available each week and a team maintaining one shared codebase. Explain how agile and two XP practices could support the work, then state one limitation.

Separate agile iteration/feedback from the XP quality mechanisms.

Students type their answer here.

Written answer6 marks

A small charity wants to refine a new donation-screen design with staff over six weeks. Evaluate RAD for the task.

Explain prototype/evaluation cycles, benefits, drawbacks and reach a qualified judgement.

Students type their answer here.

Written answer12 marks

A travel platform has changing user priorities, a fixed four-month launch, an available product representative and a high-risk connection to live rail data. Discuss the relative suitability of waterfall, agile/XP, spiral and RAD, then recommend a primary methodology.

Compare mechanisms in context and make a balanced, supported judgement.

Students type their answer here.

Trace table25 marks

Trace the algorithm for readings [18, 40, 75]. Record each reading, label, count and final output.

Complete the trace without checking intermediate answers. Record changed values and output in order.

Use one row for each statement as it runs. Fill in a box only when that value changes on that row, and leave the rest blank.

ProgramPython
  1. def classify(reading):
  2. if reading < 20:
  3. return "LOW"
  4. if reading <= 70:
  5. return "NORMAL"
  6. return "HIGH"
  7. readings = [18, 40, 75]
  8. count = 0
  9. for reading in readings:
  10. label = classify(reading)
  11. if label != "NORMAL":
  12. count = count + 1
  13. print(count)
Trace table with 10 columns
Rowreadingscountreadingreading (classify)labelReturn valuereading < 20reading <= 70label != "NORMAL"Output
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
Written answer5 marks

State each returned label and explain why the final output is 2 rather than 3.

Distinguish loop iterations, return values and the selected accumulator update.

Students type their answer here.

Written answer10 marks

The supplied function valid(code) returns a Boolean. Write coherent pseudocode or program code that inputs five codes, calls valid for each, stores every returned Boolean, counts the valid codes, outputs the count, appends the count to summary.txt and closes the file.

Do not rewrite valid. Include every required input, call, returned value and side effect.

Students type their answer here.

Written answer3 marks

A candidate instead rewrites valid, prints each Boolean and never stores it. Explain two ways this fails the stated task even if the printed Booleans happen to be correct.

Compare the behaviour with the interface and output requirements.

Students type their answer here.

Fill in the blanks3 marks
A recommendation needs process checkpoint gap 1, project application and a supported judgement. A supplied function's returned value must be checkpoint gap 2 or used. File output is incomplete until every required value is written and the file is checkpoint gap 3.

Review your responses

Check every response against its command word and the supplied constraints. Strengthen unsupported assertions with an accurate mechanism and a contextual consequence before submitting.