Community resourceWorksheet

OCR H446 2.2.2 Visualisation for understanding and planning

Part 12 of 14 · H446 2.2.2 · Computational methods

Visualisation earns marks in H446 2.2.2 only when the mapping is explained, so a diagram of labelled boxes will not do. Dependency graphs for a workflow give students something concrete to read, extend and judge, and the worksheet also draws the line between visualisation and abstraction.

Students will:

  • state what each symbol and arrow in a visual representation stands for
  • read a dependency graph for ordering constraints and for work that could run concurrently
  • extend a diagram with a new task and explain what the added arrow means
  • explain how visualisation depends on abstraction without being the same idea
  • design a visualisation for a software release and evaluate how useful it would be

Inside: 7 explanation cells, 1 multiple-choice question, 2 fill-in-the-blanks cells and 2 written answers. 20 marks, about 20 to 30 minutes.

Series: H446 2.2.2 · Computational methods, part 12 of 14.

Shared by Coding PathwayVerified teacher

  • 12 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.

Visualisation for understanding and planning

A complex workflow may be easier to reason about when tasks and dependencies are made visible. Visualisation creates an external or mental model that supports understanding, planning and communication.

By the end, you will be able to

  • explain the purpose of visualisation as a computational method;
  • map visual symbols explicitly to a problem;
  • use a diagram to identify order, concurrency and constraints;
  • distinguish visualisation from abstraction while explaining their overlap.

Reactivate: a graph contains nodes and edges; direction can represent dependency.

A useful visual has a mapping

Visualising task dependenciescollect datavalidatecleananalyse resultsNodes represent tasks; arrows represent dependencies. The diagram exposes order and possible concurrency.

In this dependency graph, each node represents a task and each arrow means ‘the source must complete before the destination can begin’. The diagram shows that validate and clean can run after collection and may proceed concurrently, but analysis waits for both.

An examination answer should state what the symbols represent in the scenario. ‘It makes the problem easier to see’ is incomplete unless it explains what becomes visible and how that supports a plan or decision.

Worked reasoning

Scenario: prepare event data for analysis.

  • Representation: tasks become labelled nodes; prerequisites become directed arrows.
  • Insight: two branches from collection reveal possible concurrent work.
  • Constraint: analysis has two incoming arrows, so it cannot start after only one predecessor.
  • Decision: staff can allocate separate workers to validation and cleaning, then synchronise their results.
  • Limit: the graph does not show duration unless time labels or another visual encoding are added.

The visual is useful because its mapping exposes relationships relevant to planning.

Multiple choice1 mark

Which explanation best describes the role of visualisation here?

  • AIt removes the need to understand the problem
  • BIt guarantees the fastest implementation
  • CIt stores every real-world detail
  • DIt maps tasks and dependencies into a model that helps identify order and possible concurrency
Fill in the blanks3 marks
In the dependency graph, nodes represent gap 1, arrows represent gap 2, and branching may reveal possible gap 3.
  • tasks
  • dependencies
  • concurrency
  • data types

Guided checkpoint: read before redesigning

Add a new task approve report after analysis. State the node and arrow you would add, then explain what the arrow means. Next, suggest one annotation that would make the visual useful for estimating completion time. This forces every mark on the diagram to carry defined information.

Written answer5 marks

Describe the visual changes and explain how they improve planning.

Include symbol-to-problem mapping and one planning consequence.

Students type their answer here.

Visualisation and abstraction

They can work together but are not synonyms. Abstraction selects relevant details for a purpose. Visualisation represents selected information in a form that helps someone form a mental model. A dependency graph therefore relies on abstraction because the designer omits irrelevant details, but its distinctive contribution is making relationships visible for reasoning and communication.

Written answer7 marks

A team must plan a software release involving code review, security testing, documentation, deployment approval and release. Describe a visualisation that would help and evaluate its usefulness.

Name the symbols, their meanings, one insight, one decision and one limitation.

Students type their answer here.

Closed-book checkpoint

Complete each sentence from memory. There is no answer bank and correctness is held for teacher review.

Fill in the blanks4 marks
A visual needs an explicit checkpoint gap 1 between each symbol and the problem. Arrows can expose a prerequisite checkpoint gap 2. The model supports understanding and checkpoint gap 3. Selecting which details to show requires checkpoint gap 4.

Review your understanding

Before submitting, check that you can explain the central distinction in your own words, expose the intermediate state that supports your answer and apply the method in an unfamiliar context.