Topic module

2.1 Investigation

Analyse the annual scenario using decomposition, abstraction and pattern recognition to define data, users and requirements.

Long-form learning
Concept to Risk to Memory to Check-up

How to study WJEC GCSE Computer Science

Learn the computing principle, apply it to the named system or scenario, trace the data and control flow, and test the result against requirements.

Core concepts

Concept 1

Scenario interpretation, users, purpose, functional and non-functional requirements

Exam cue: Identify the current WJEC unit, the command word and whether the task asks for knowledge, application or computational analysis.

Concept 2

Decomposition, abstraction, pattern recognition and computational modelling

Exam cue: Turn each scenario statement into a testable requirement and separate essential data and behaviour from distracting detail.

Concept 3

Inputs, outputs, processing, data sources, constraints and success criteria

Exam cue: Use precise terminology, trace inputs and state changes, and test the answer against the data, scenario or program behaviour.

Risk pitfalls and guardrails

Starting to code before defining the users, required inputs, outputs, processing, constraints and measurable success criteria.

Guardrail: Avoid generic descriptions, unchecked traces and cross-board assumptions; make every answer depend on the named data, system, algorithm or scenario.

Importing the legacy WJEC structure, a different board's content or a Foundation/Higher tier assumption.

Guardrail: Use qualification code 3460QS or 3460CS and the current two-unit untiered structure; do not import a legacy or cross-board route.

Giving a generic description without applying it to the named system, data set, algorithm or pre-release scenario.

Guardrail: Practice cannot replace the annual live brief, specified Python environment, clean-copy rule, restricted examination files or Surpass upload process.

Memory anchors

Functional requirement

A service or behaviour the completed program must provide.

Non-functional requirement

A quality or constraint such as usability, performance, reliability or security.

Pattern recognition

Finding similarities or repeated structures that can support a reusable solution.

Data requirement

A precise statement of the values, types, ranges, formats and persistence the solution needs.

Constraint

A boundary on the solution, such as available time, tools, data, hardware or specified Python environment.

Success criterion

A measurable condition used to judge whether the solution meets a requirement.

Checkpoint rule

Do the check-up only after you can summarize each concept in one sentence and identify one dangerous pitfall from memory.

Knowledge Check (after reading)

Short check-up to confirm understanding of this module.

Check-up Questions

1-2 question checkpoint

Before coding a booking tool, what should be identified first?

Who is a stakeholder in a school-lunch system?

Answer all questions to submit.

Next step personalized recommendations

Continue learning

Move forward only after this module is stable.

What is Pass Harbor?

Completely free exam prep for 247 UK exams.

  • Practice questions
  • Flashcards
  • Study guides
  • Mock exams
  • No registration
  • No paywall
  • Start instantly
No more expensive exam prep. Quality study tools should be accessible to everyone.