← VCE Software Development U3O2

Drawing a context diagram from a scenario

Shows the whole system as one process, with the external entities around it and a labelled data flow arrow for each piece of data going in or out. Built by reading a scenario.

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

Understanding Drawing a context diagram from a scenario in VCE Software Development U3O2

What it does: When reading a scenario, you pick out who or what interacts with the system. These become the external entities placed around the central process. A complete flow has a direction, a start and end (system and entity) and a label naming the data. This arrow has all three. A context diagram only shows data flowing to or from the system. Flows between two entities happen outside the system and are not shown.

Common mistakes: The app is the system, not an external entity. The entity is the person or group outside it, so line 2 should be 'Entity: Student'. A database is stored inside the system, so it is not an external entity. Line 2 should name an outside entity such as 'Entity: Member'.

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 Drawing a context diagram from a scenario to a class →

This module's key terms are also in a printable crossword (Modules 42–51) 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
A scenario says: 'Students use a library app to borrow books, and the app sends overdue notices to students.' How should you draw the system on a context diagram?
Separate boxes for 'borrow books' and 'send notices' inside the systemOne central process named 'Library app' with Student as an external entity
Matches
Member --> Library System (no label on the arrow)
↓
The data flow arrow is missing a label, so we cannot tell what data is moving between the entity and the system
Applying
Meanings
Term
context diagram
Meaning
Shows the whole system as one process, with the external entities around it and a labelled data flow arrow for each piece of data going in or out. Built by reading a scenario.
Practice
System: Canteen Ordering System
Testing
Gaps
Context diagram processes:
Check Answer
Spots
1System: Canteen Order App
2Entity: Canteen Order App

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

The 'Parrotfish' badge — Function Builder, 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. A scenario says: 'Students use a library app to borrow books, and the app sends overdue notices to students.' How should you draw the system on a context diagram?
A. Separate boxes for 'borrow books' and 'send notices' inside the system
B. One central process named 'Library app' with Student as an external entity ✓
A Level 0 context diagram shows the whole system as ONE process. Breaking it into smaller processes belongs in a Level 1 data flow diagram.
2. When reading a scenario to find external entities, what should you look for?
A. Every database table and screen that the software uses internally
B. People, organisations or other systems outside the software that send data in or receive data out ✓
External entities sit outside the system boundary. Internal tables and screens are not shown on a context diagram.
3. A scenario says: 'A customer enters their order details into the website.' Which data flow label is best for the arrow from Customer to the system?
A. Order details ✓
B. Customer
Data flow labels name the data being moved, such as 'Order details'. The entity name goes in the entity box, not on the arrow.
4. You have finished drawing your context diagram. Which check should you do?
A. Every arrow has a label naming the data and a direction showing where it goes ✓
B. Arrows can be left unlabelled if the entity names make the meaning obvious
Every data flow must be labelled and have an arrowhead. An unlabelled arrow loses marks because the data is not identified.
5. Which is a common mistake when drawing a context diagram from a scenario?
A. Drawing a data flow directly between two external entities ✓
B. Drawing a data flow between an external entity and the system
A context diagram only shows data flowing to or from the system. Flows between two entities happen outside the system and are not shown.

Match the Pairs

Library System (one central process box) → The whole system is drawn as ONE process in the centre, named after the system, with no internal detail
Member --> [ book request ] --> Library System → A labelled data flow arrow from an external entity into the system, showing what data enters
Reading a scenario: each person, organisation or other system that sends data to or receives data from the system is an external entity → Entities: Member, Librarian, Publisher
Checking every flow has a label: each arrow shows the data it carries and the direction of travel → Library System --> [ overdue notice ] --> Member
Member --> Library System (no label on the arrow) → The data flow arrow is missing a label, so we cannot tell what data is moving between the entity and the system
Member --> [ book request ] --> Catalogue Database → A data store is drawn in a context diagram and the flow bypasses the system, but context diagrams show only the system process and external entities

Key Term

context diagram
Shows the whole system as one process, with the external entities around it and a labelled data flow arrow for each piece of data going in or out. Built by reading a scenario.

Fill in the Blanks

1. Context diagram processes: 1
Hint: Type the number of processes shown in the centre of a context diagram.
2. Scenario: Parent sends payment details. Parent --> School System : Payment details
Hint: Type the label for this data flow, taken from the scenario.
3. Scenario: A coach views the team roster. External entity: Coach
Hint: Type the external entity named in the scenario that sits outside the system.
4. Scenario: System sends report to teacher. Marks System --> Teacher : Report
Hint: Type the arrow that shows the direction this data flows.
5. Context diagram: data stores = 0
Hint: Type how many data stores appear on a Level 0 context diagram.

Spot the Error

Question 1
A System: Canteen Order App
B Entity: Canteen Order App
C Student -> System: order
D System -> Student: receipt
Line B — The app is the system, not an external entity. The entity is the person or group outside it, so line 2 should be 'Entity: Student'.
Question 2
A System: Gym Booking App
B Entity: Booking database
C Entity: Trainer
D Member -> System: booking
E System -> Trainer: roster
Line B — A database is stored inside the system, so it is not an external entity. Line 2 should name an outside entity such as 'Entity: Member'.
Question 3
A System: Library Loan App
B Entity: Member
C Member -> System: book request
D System -> Member:
Line D — Every data flow must have a label naming the data that moves. Line 4 should be 'System -> Member: loan receipt'.
Question 4
A Entity: Parent
B System: Validate and Store
C Parent -> System: fee payment
D System -> Parent: receipt
Line B — A context diagram shows the whole system as one process with one name. Splitting it into steps belongs in a Level 1 DFD. It should be 'System: School Payment App'.
Question 5
A System: Clinic Booking App
B Entity: Patient
C System -> Patient: booking
D System -> Patient: reminder
Line C — The patient supplies the booking details, so the arrow must point from the patient into the system: 'Patient -> System: booking'.

Student with a class code? Join your class →