Community resourceWorksheet
OCR H446 1.2.4 Paradigms, language levels and contextual choice
Part 1 of 10 · H446 1.2.4 · Types of programming language
OCR H446 1.2.4 treats language level and programming paradigm as two separate classifications, but examination answers often collapse them into a vague claim that high-level languages are easier. This worksheet keeps the two questions apart and builds matched comparisons that tie a mechanism to its consequence.
Students will:
- separate the question of language level from the question of paradigm
- judge whether a statement about language level is accurate
- compare assembly and high-level code using the same criteria on both sides
- recommend a language level and organisational approach for a portable app, memory-limited firmware and a large team-maintained simulation
- justify each recommendation from the stated project constraints
Inside: 5 explanation cells, 1 multiple-choice question, 2 fill-in-the-blanks cells and 2 written answers. 21 marks, about 30 to 40 minutes.
Series: H446 1.2.4 · Types of programming language, part 1 of 10.
Shared by Coding PathwayVerified teacher
- 10 cells
- About 30 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.
Paradigms, language levels and contextual choice
A language level describes distance from machine operation. A paradigm describes how a solution is organised. Keeping these two questions separate prevents a common examination trap.
By the end, you will be able to
- distinguish low/high level from procedural/object-oriented;
- make a paired comparison;
- choose an approach from project constraints rather than task size alone.
Two classification questions
Low-level code exposes processor-specific instructions and direct hardware/memory control. Assembly uses mnemonics and needs an assembler; machine code is binary. High-level languages use greater abstraction and generally improve readability, development and portability, but still need translation for a target machine.
A procedural solution organises operations into procedures and a controlled sequence of steps. An object-oriented solution organises state and behaviour into interacting objects. Neither paradigm label fixes the language level or guarantees suitability.
Worked paired comparison
Weak: ‘High-level languages are easier.’
Stronger: ‘Assembly maps closely to processor instructions and gives direct control, whereas a high-level language hides much of that machine detail. The high-level route is usually quicker to develop and more portable, while assembly may suit a constrained device requiring precise hardware access.’
The stronger answer uses one criterion on both sides, then applies the consequence.
Which statement is accurate?
- AAssembly uses mnemonics and an assembler
- BEvery procedural language is low level
- CObject-oriented is a language level
- DMachine code needs an interpreter
- processor
- portable
- abstraction
- binary
Compare assembly and high-level languages using two matched criteria.
For each criterion, state both sides. Suitable criteria include notation/translation, instruction mapping, control or portability.
Students type their answer here.
Apply the model independently
The remaining tasks change the context or reduce the support. Complete them without copying the worked model, then check that each explanation connects a mechanism to its consequence.
A team is building (1) a portable school timetable app, (2) firmware for a novel sensor with 4 KB free memory, and (3) a large simulation maintained by several teams. Recommend a language level and organisational approach for each. Justify each choice from the stated constraints.
Use feature → constraint → consequence. More than one answer can be defensible for the simulation if it is reasoned.
Students type their answer here.
Review your understanding
Before submitting, check that you can explain the main distinction in your own words, apply it in an unfamiliar context and justify each consequence rather than only naming a feature.