All diagram examples
Every diagram example in one list. They also appear in the deep dives: planning examples in Criterion B, design examples in Criterion C.
Planning examples (Criterion B)
Design examples (Criterion C)
1. What does the system do and for whom?
2. What parts make up the system?
Architecture diagramWhere the software runs, its main parts and how they communicate. Site map / screen navigation diagramEvery screen and the links between them, by role. Module/function structure chartFor procedural code: which function calls which, and what is passed. UML class diagramFor OOP: classes, attributes, methods and relationships.
3. How is data organised and stored?
ERD with relational schemaEntities, keys and relationships, then the tables. Firestore collection/document diagramCollections, documents, fields, subcollections and references. Firebase Realtime Database JSON treeOne JSON tree: keys, paths and nested values. File structure and data dictionaryFolders and files, file formats and every field's definition. Data structure diagramsArrays, linked lists, queues, stacks, sets, maps, trees and graphs.
4. How does the user interact with the system?
UI wireframes and annotated screen designsScreen layouts with numbered notes, plus journeys, CLI sessions and chatbot flows. Input validation and error-message tableEvery input, its rule, test values and the exact message.
5. How does the system process information?
Algorithm flowchart and pseudocodeThe logic of one algorithm, as a flowchart and as pseudocode. Data flow diagramWhere data comes from, which process changes it and where it is stored. Sequence diagramMessages between user, interface, server and database, in time order. State transition diagram, decision table and event–action tableLifecycles, rules for every combination, and responses to events. SQL query design tablePurpose, inputs, query logic and expected output of significant queries.