Tip: Choose Save as PDF in the print dialog to download. Use A4 paper size.
Shade in the A or B circle for each question.
Draw a line connecting each item on the left to its match on the right.
| Left column | Right column | |
|---|---|---|
| 1Context diagram (Level 0) of the current system | ACurrent: Paper form -> Enter data | Proposed: Online form -> Validate | |
| 2Level 1 DFD of the current system | BPaper forms -> 2.0 Enter data manually -> Student records | |
| 3Finding a bottleneck: many data flows queue up at one manual process, such as paper forms waiting for one person to enter them | CA diagram of the existing system must show how things work now, not the planned solution. Mixing in new features hides the real problems. | |
| 4Comparing current and proposed: the new design replaces the manual step with an automated process | DBreaks the existing system into processes, data stores and flows so slow steps and bottlenecks can be spotted | |
| 5Drawing the proposed solution's new features on the diagram of the existing system | EWithout a diagram of the current system, bottlenecks and problems are not identified, so the new solution may not fix them. | |
| 6Skipping the current system diagram and starting to design the new solution straight away | FShows the existing system as one process with the external entities and data flows that enter and leave it |
Complete each line of code by filling in the missing parts.
Shade in the letter of the line that contains an error.
Depicting an existing system — Using analytical tools like context and data flow diagrams to show how the current system works, so bottlenecks and problems are exposed for the new solution to fix.Tool: context diagram shows whole systemA bottleneck is a step that slows the flowCompare current vs proposed system diagramsContext diagram has 1 process: the systemDiagrams of the current system expose
problems that the new solution must fix