Software Engineering › Learn step by step › Diagrams and tools
Item 383 of 426 · Diagrams and modelling tools, 8 of 18
Structure chart
Diagram
Jump to a topic
- Exam format, question types and command words (46)
- Year 11: Programming Fundamentals (69)
- Year 11: The Object-Oriented Paradigm (33)
- Year 11: Programming Mechatronics (29)
- Year 12: Secure Software Architecture (57)
- Year 12: Programming for the Web (59)
- Year 12: Software Automation (35)
- Year 12: The Software Engineering Project (47)
- Diagrams and modelling tools (18)
- Python, SQL, pseudocode and CSS patterns (33)
Definition
Shows the separate subroutines that make up a system and their relationship to each other, top-down from the main routine.
Example: Main calls Get Data, Process Data, Display Results.
Found in: syllabus, course specifications, sample exam and familiarisation guidelines, school notes, past SDD papers.
Where you'll use it in the test
Syllabus area: Diagrams and tools.
Question types it can appear in
- Drawing: Draw a structure chart (sample Q10, familiarisation Q4)
- Short answer: Define, outline or explain it and tie it to the scenario.
- Multiple choice: Pick the option that matches the definition or example.
Where it has appeared in the paper
The Software Engineering Project (Part B, C, D). Part letters follow each paper’s own layout.
Related past questions
- Sample exam Q10 (2 marks): Structure charts The Software Engineering Project (Part B) · 2 marks
- Familiarisation Q4 (2 marks): Structure charts The Software Engineering Project (Part C) · 2 marks
- 2023 Software Design and Development HSC Q27 (10 marks): User interface, structure chart, quality assurance The Software Engineering Project (Part D) · 10 marks · old syllabus
1 more on the full term page.
How to use it
A model sentence
Diagram: “Shows the separate subroutines that make up a system and their relationship to each other, top-down from the main routine.” Then apply it: Main calls Get Data, Process Data, Display Results.
In a short answer, give the definition in your own words first, then tie it to the situation in the question. Do not copy the example above unless it fits the scenario.
Command words used with it
- Explain: Relate cause and effect; make the relationship between things evident; provide why and/or how. (2024 Software Design and Development HSC Q25 (4 marks): Documentation)
Go deeper
- Flashcard: Structure chart in Diagrams and Modelling Tools (Years 11 and 12) · study that set
- Memorise: Drawing rules: DFD, structure chart, storyboard, decision tree, class diagram, ERD
- Notes: Part 3. Where this has been examined (see ../../question_bank.md) (The Software Engineering Project (Year 12))
- Notes: Part 3. Where this has been examined (see ../../question_bank.md) (Pseudocode, flowcharts and diagram rules)
- Master answer: sdd2023-q27 (10 marks, extended) (Master model answers: The Software Engineering Project (written answers))
- Notes: Structure Chart (Pseudocode, flowcharts and diagram rules)
- Full term page: every question, note and marking comment for Structure chart
Check yourself
Describe or sketch “Structure chart”: what it shows, its parts and when you would use it.
Reveal the answer
Shows the separate subroutines that make up a system and their relationship to each other, top-down from the main routine.
Example: Main calls Get Data, Process Data, Display Results.
Could be tested as: Drawing, Short answer, Multiple choice.