008. systems analysis: mapping data flow (ks4)
Master systems analysis by creating data flow diagrams to map information through complex systems.
Before developers write complex code for a new system, they need to understand exactly how information will travel through it. Where does the data start, and where does it end up? We are going to master systems analysis by drawing Data Flow Diagrams (DFDs). You will learn how to visually map the journey of information, spotting bottlenecks and designing highly efficient digital systems.
The Digital Blueprint: Mastering Systems Analysis
Why Plan?
If you were building a house, you wouldn't just start laying bricks and hope for the best. You'd start with a blueprint. A blueprint shows where the walls, doors, and windows go, and how all the rooms connect. In the world of software development, a Data Flow Diagram (DFD) is the blueprint. It's a visual map that shows how information moves, or 'flows', through a system to accomplish a task. Without a DFD, developers might build a system that loses customer orders, sends invoices to the wrong people, or simply doesn't work. Systems analysis is the professional discipline of creating this blueprint.
The Anatomy of a Data Flow Diagram
A DFD has a very simple, standardised set of symbols that allows any analyst, anywhere in the world, to understand it. There are only four components to master:
External Entities: These are the people or systems that interact with your system from the outside. They are the sources of data and the destinations for it. For example, in an online shop system, the 'Customer' is an external entity. We draw them as a square or rectangle.
Processes: A process is an action that transforms data in some way. It takes incoming data and produces a different, new output. For example, a 'Calculate Total Cost' process would take the item prices and quantities, and output a final bill. We draw processes as a circle or a rounded rectangle.
Data Stores: A data store is where the system holds information for later use. It's the system's memory, like a digital filing cabinet. Examples include a 'Products' database or a 'Customer Accounts' table. We draw them as two parallel lines or an open-ended rectangle.
Data Flows: A data flow is simply the path that the data takes between the other three components. It's represented by an arrow, and it must have a label describing exactly what data is flowing. For instance, a data flow from a 'Customer' entity to an 'Order Pizza' process would be labelled 'Pizza Order Details'.
By combining these four simple symbols, a systems analyst can create a clear, unambiguous map of even the most complex digital system, ensuring everyone on the development team knows exactly what they need to build.
Plugged Task: The E-Commerce Investigator
You've just been hired as a Junior Systems Analyst for a brand-new online store called "Retro Threads", which sells vintage t-shirts. Your first task is to create a simple, high-level blueprint of the ordering system. You need to produce a 'Level 0' or 'Context' Data Flow Diagram to show the whole system as one single process and how it interacts with the outside world.
The Persona
As 'The Analyst', your job is not to code, but to understand and communicate. You must be precise with your symbols and labels. Your goal is to create a diagram that is so clear, a new developer could look at it and instantly understand the boundaries of the system.
1
Get Organised
Your diagram needs to show the core system and its interactions. First, on a piece of paper or in a text document, list the answers to these questions:
What is the single main process? (Hint: The name of the system itself!)
Who are the people or external companies interacting with the system? These are your External Entities. You will need three: The Customer, the Payment Processor (like a bank), and the Warehouse (which sends out the t-shirts).
2
Choose your tool
You will need a digital tool to draw your DFD. We recommend using a free, web-based diagramming tool.
Navigate to diagrams.net. This is a powerful and easy-to-use tool that runs in your browser.
3
Draw the Blueprint
Now, use the shapes available in the software to draw your DFD. Remember the rules for each symbol!
1
Create a single Process bubble in the middle of your page. Label it "Retro Threads Ordering System".
2
Create three External Entity boxes around the process. Label them "Customer", "Payment Processor", and "Warehouse".
3
Now, draw the Data Flows using arrows. You must label every single arrow. You will need to show:
From Customer to Process: "Order Details"
From Process to Payment Processor: "Payment Request"
From Payment Processor to Process: "Payment Confirmation"
From Process to Warehouse: "Shipping Instruction"
From Process to Customer: "Order Confirmation"
Act as a computing teacher. Explain the four main symbols used in a Data Flow Diagram (DFD). The audience is a 15-year-old student. Limit the response to 150 words. Use a confident and clear tone. NO intro, NO outro, NO deviation from the topic, NO follow-up questions
4
Review and Export
Look at your finished diagram. Does it clearly show how data moves in the system? Have you used the correct shapes and labelled every arrow?
Once you are happy, export your diagram. Go to File > Export as > PNG.
Make sure the "Include a copy of my diagram" option is checked.
Click Export and save the file with your name. Submit this PNG file as your work.
Outcome
You have created a single PNG image file.
Your diagram contains one central Process bubble, correctly labelled.
Your diagram includes three External Entity boxes, correctly labelled.
Your diagram shows five Data Flow arrows, all pointing in the correct direction and clearly labelled.
You have used the standard DFD shapes for each component.
Unplugged Task: The Library System Blueprint
Grab a pen and a piece of A4 paper. Your task is to design a Level 0 (Context) Data Flow Diagram for a school library's book borrowing system.
1
First, identify and list the External Entities. Who or what interacts with the system? You'll need at least "Student" and "Librarian".
2
Next, decide on the name for the single central Process. This should describe the whole system (e.g., "Library Loan System").
3
Draw the Process bubble in the centre of your page and the Entity boxes around it.
4
Finally, draw and label the Data Flows. Think about what information needs to pass between the entities and the system.
What information does the Student give the system?
What information does the system give back to the Student?
What information does the Librarian need from the system?
What information does the Librarian put into the system?
Last modified: June 24th, 2026
