← VCE Software Development U3O2

Context diagram (Level 0): data flows

A labelled arrow on a context diagram showing data passing between an entity and the system. The arrowhead shows direction (input or output) and the label names the data.

Part of: VCE Software Development - U3O2 - Analysis and Design — Module 41, QCE Digital Solutions Unit 2 — Data-Driven Problems and Solution Requirements — Module 85, QCE Digital Solutions Unit 3 — Interactions Between Users, Data and Digital Systems — Module 23, QCE Digital Solutions Unit 3 — Innovative Digital Solutions — Module 3, QCE Digital Solutions Unit 4 — Complex Digital Data Exchange Problems and Solution Requirements — Module 88

Understanding Context diagram (Level 0): data flows in VCE Software Development U3O2

What it does: 'Order details' names the exact data passing from the Customer to the system, which is what a good data flow label does. One arrow carries marks in and a separate arrow carries a report out, each with its own direction and label. The student is sending data in, so the arrowhead points at the system. This is an input. Labels name the data moving along the arrow. Programming languages are not shown on a context diagram. Inputs enter the system, so their arrowheads point at the system. Outputs leave it.

Common mistakes: The arrow direction is wrong. The due date is an output from the system to the member, so the arrowhead should point to Member: System -> Member: Due date. Every data flow arrow must be labelled with the data it carries. This arrow needs a name, such as System -> Student: Receipt.

Class: _____________________  ·  Name: _____________________  ·  Date: _________

Free printable worksheet with full answer key — or add this module to a class and your students practise it interactively.

🖨 Print worksheet + answer key Add Context diagram (Level 0): data flows to a class →

This module's key terms are also in a printable crossword (Modules 26–41) and word search (Modules 26–51).

Take this worksheet further — free with Cloodit

Each concept is reinforced from every angle — learned, then applied, then tested.

Learning
Duo
On a context diagram, what does an arrow between an entity and the system represent?
A physical delivery of hardware to the systemData passing between the entity and the system
Matches
Customer --- [Online Shop]
↓
The line has no arrowhead and no label, so it shows neither the direction of the data nor what data is passing.
Applying
Meanings
Term
data flow
Meaning
A labelled arrow on a context diagram showing data passing between an entity and the system. The arrowhead shows direction (input or output) and the label names the data.
Practice
Student -> Library System : Loan request
Testing
Gaps
Customer System : order details
Check Answer
Spots
3Staff -> System: Book details
4Member -> System: Due date

Cloodit turns curriculum-aligned coding content into journeys students work through one biome at a time.

The 'Dolphin' badge — Reef Streak, one of Cloodit's 106 collectible badges
Students earn collectable badges

Over 100 of them, across seven natural biomes.

Study Buddy
Students build a real study resource

Turns their work into revision material ready for Flash Cards and Exam study.

Diamond Dash — one of Cloodit's live, competitive Sprint games
Students lock in with Sprints

Live, competitive practice for the start of the lesson or a teacher-led lesson finisher.

A Cloodit certificate of achievement, ready to personalise and print
Custom printable certificates

Honour your top performers, or encourage a student who's trying hard — ready to print in seconds.

Add to class →

Quick Questions

1. On a context diagram, what does an arrow between an entity and the system represent?
A. Data passing between the entity and the system ✓
B. A physical delivery of hardware to the system
Each arrow is a data flow. It shows data moving between an external entity and the system.
2. A student submits an enrolment form to a school system. Which way should the arrowhead point?
A. From the system towards the Student entity
B. From the Student entity towards the system ✓
The student is sending data in, so the arrowhead points at the system. This is an input.
3. A system sends a receipt to a customer. Which statement is correct?
A. It is an output, so the arrow points to the Customer entity ✓
B. It is an input, so the arrow points to the system
Data leaving the system for an entity is an output. The arrowhead points at the entity.
4. Which is the better label for a data flow?
A. Booking request ✓
B. Sends stuff
A data flow label should be a noun phrase that names the data, such as 'Booking request'. Vague labels and verbs do not name the data.
5. A data flow on a context diagram should be labelled with:
A. The name of the programming language used
B. The name of the data being passed ✓
Labels name the data moving along the arrow. Programming languages are not shown on a context diagram.

Match the Pairs

Student --> [Library System] : Loan request → An input data flow: the arrow points from the entity into the system, labelled with the data being sent (Loan request).
[Library System] --> Student : Due date notice → An output data flow: the arrow points from the system out to the entity, labelled with the data being sent (Due date notice).
Each data flow on a context diagram needs a label that names the specific data being passed, not just a vague word like 'info'. → Customer --> [Online Shop] : Order details
Data flows between an entity and the system can go in both directions, so each direction is drawn as its own labelled arrow. → Teacher --> [Marks System] : Student marks [Marks System] --> Teacher : Class report
Customer --- [Online Shop] → The line has no arrowhead and no label, so it shows neither the direction of the data nor what data is passing.
[Online Shop] --> Customer : Order details → The arrow direction is wrong. Order details are sent by the customer into the system, so the arrow should point from Customer to the system.

Key Term

data flow
A labelled arrow on a context diagram showing data passing between an entity and the system. The arrowhead shows direction (input or output) and the label names the data.

Fill in the Blanks

1. Customer -> System : order details
Hint: Type the arrow symbol that shows data moving from the entity on the left into the system.
2. System -> Customer : receipt
Hint: Type the name of the single central process that every entity connects to on a context diagram.
3. Customer -> System : order details // input
Hint: Type the word for a data flow that enters the system from an entity.
4. System -> Customer : receipt // output
Hint: Type the word for a data flow that leaves the system and goes to an entity.
5. Customer -> System : order details System -> Customer : receipt
Hint: Type the external entity that sent the order and receives the reply back from the system.

Spot the Error

Question 1
A Context: Library System
B Member -> System: Loan form
C Staff -> System: Book details
D Member -> System: Due date
Line D — The arrow direction is wrong. The due date is an output from the system to the member, so the arrowhead should point to Member: System -> Member: Due date.
Question 2
A Context: Canteen System
B Student -> System: Order
C System -> Student
D Staff -> System: Menu update
Line C — Every data flow arrow must be labelled with the data it carries. This arrow needs a name, such as System -> Student: Receipt.
Question 3
A Context: Member
B Member -> System: Booking
C System -> Member: Timetable
Line A — The single central shape on a context diagram is the system, not an entity. It should read Context: Gym Booking System, with Member as an external entity sending and receiving flows.
Question 4
A Context: Tuckshop System
B Student -> System: Order
C System -> Kitchen: Data
D Kitchen -> System: Stock list
Line C — A data flow label must name the specific data being passed. 'Data' is too vague; it should be something like Order list.
Question 5
A Context: Banking App
B Customer -> Bank: Transfer
C Bank -> System: Approval
D System -> Customer: Balance
Line B — Data flows on a context diagram go between an entity and the system, never directly between two entities. The flow should be Customer -> System: Transfer.

Student with a class code? Join your class →