Blame
|
1 | > **DRAFT** — under teacher review. |
||||||
| 2 | ||||||||
| 3 | # Analytical Tools Template — UCD, Context Diagram, and DFD |
|||||||
| 4 | ||||||||
| 5 | Hamilton College · Year 12 · 2026 |
|||||||
| 6 | ||||||||
| 7 | When you update your analytical tools in C3-1 (Step 1), you need to reproduce a Use Case Diagram, a Context Diagram, and a Data Flow Diagram. Setting up the notation from scratch each time costs 15–20 minutes and introduces layout errors. This page explains what is in the pre-labelled Excalidraw template and how to use it. |
|||||||
| 8 | ||||||||
| 9 | --- |
|||||||
| 10 | ||||||||
| 11 | ## What the template contains |
|||||||
| 12 | ||||||||
| 13 | The Excalidraw file (`C03-Analytical-Tools.excalidraw`) has three pre-built diagram skeletons on a single canvas, each with placeholder nodes labelled by notation role: |
|||||||
| 14 | ||||||||
| 15 | | Diagram | Pre-built elements | |
|||||||
| 16 | |---|---| |
|||||||
| 17 | | **Use Case Diagram (UCD)** | System boundary box; actor stick figures (primary user, secondary user); labelled oval placeholders for use cases; `«include»` and `«extend»` relationship stubs | |
|||||||
| 18 | | **Context Diagram** | Central process circle (labelled with your system name placeholder); external entity rectangles on each side; labelled data-flow arrows in and out | |
|||||||
| 19 | | **Data Flow Diagram (DFD)** | Level 1 layout with process circles, data store open rectangles, external entity rectangles, and directional arrow stubs; numbered process placeholders | |
|||||||
| 20 | ||||||||
| 21 | All three diagrams use the standard Yourdon–DeMarco notation that VCAA markers expect. |
|||||||
| 22 | ||||||||
| 23 | --- |
|||||||
| 24 | ||||||||
| 25 | ## How to use it |
|||||||
| 26 | ||||||||
| 27 | 1. **Download the file** — ask your teacher for `C03-Analytical-Tools.excalidraw`. |
|||||||
| 28 | 2. **Open in Excalidraw** — go to [excalidraw.com](https://excalidraw.com) and drag the file onto the canvas, or use the **Open** menu. |
|||||||
| 29 | 3. **Replace placeholders** — click each labelled placeholder and type your own system name, actor names, use cases, data stores, and process names. |
|||||||
| 30 | 4. **Add or remove elements** — copy a placeholder shape to add more use cases, or delete extras. Keep the notation style consistent (don't mix shapes between diagram types). |
|||||||
| 31 | 5. **Export** — when done, export as PNG or SVG to paste into your SRS document. |
|||||||
| 32 | ||||||||
| 33 | --- |
|||||||
| 34 | ||||||||
| 35 | ## What to notice when you update |
|||||||
| 36 | ||||||||
| 37 | Coming back to these diagrams from C02, check: |
|||||||
| 38 | ||||||||
| 39 | - **New actors**: has your scope change added a new type of user? Add them to the UCD. |
|||||||
| 40 | - **New data flows**: does your updated scope require new data in or out? Update the Context Diagram arrows. |
|||||||
| 41 | - **New processes**: does the DFD reflect how data now moves through the updated system? |
|||||||
| 42 | ||||||||
| 43 | The rubric at 7–8 band requires diagrams that accurately reflect your current SRS — not your C02 version. Change what has changed; don't just copy-paste from C02. |
|||||||
| 44 | ||||||||
| 45 | --- |
|||||||
| 46 | ||||||||
| 47 | ## Notation quick reference |
|||||||
| 48 | ||||||||
| 49 | ### Use Case Diagram |
|||||||
| 50 | ||||||||
| 51 | | Symbol | Meaning | |
|||||||
| 52 | |---|---| |
|||||||
| 53 | | Stick figure | Actor (a person or external system that interacts with yours) | |
|||||||
| 54 | | Oval | Use case (a goal the actor achieves using the system) | |
|||||||
| 55 | | Rectangle | System boundary (what is inside vs outside the scope) | |
|||||||
| 56 | | `«include»` arrow | Use case A always includes use case B | |
|||||||
| 57 | | `«extend»` arrow | Use case B optionally extends use case A | |
|||||||
| 58 | ||||||||
| 59 | ### Context Diagram |
|||||||
| 60 | ||||||||
| 61 | | Symbol | Meaning | |
|||||||
| 62 | |---|---| |
|||||||
| 63 | | Circle | The system (one only — this is a Level 0 DFD) | |
|||||||
| 64 | | Rectangle | External entity (person, group, or system outside your scope) | |
|||||||
| 65 | | Arrow with label | Data flow (label = what data moves, direction = which way) | |
|||||||
| 66 | ||||||||
| 67 | ### Data Flow Diagram (Level 1) |
|||||||
| 68 | ||||||||
| 69 | | Symbol | Meaning | |
|||||||
| 70 | |---|---| |
|||||||
| 71 | | Circle | Process (transforms data; numbered: 1.0, 2.0…) | |
|||||||
| 72 | | Open rectangle | Data store (where data is held; labelled D1, D2…) | |
|||||||
| 73 | | Rectangle | External entity (same as context diagram) | |
|||||||
| 74 | | Arrow with label | Data flow | |
|||||||
| 75 | ||||||||
| 76 | --- |
|||||||
| 77 | ||||||||
| 78 | ## See also |
|||||||
| 79 | ||||||||
| 80 | - [Functional vs Non-Functional Requirements](/sd/C03/Functional%20vs%20Non-Functional%20Requirements) — requirements that feed into your diagrams |
|||||||
| 81 | - [Scope vs Constraints](/sd/C03/Scope%20vs%20Constraints) — what determines the system boundary in your UCD and Context Diagram |
|||||||
| 82 | - C03 Resources: [external reading and videos](/sd/Resources/C03-Resources) |
|||||||
| 83 | ||||||||
| 84 | --- |
|||||||
| 85 | ||||||||
| 86 | ← Back to [C03 Home](/sd/C03/C03-home) · [VCE Software Development Hub](/sd/VCE%20Software%20Development%20Hub) |
|||||||
