TK Study

Software Engineering › Key terms › Diagrams and tools › Structure chart

Structure chart

Diagram Diagrams and tools

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 it is used in the test

Syllabus area: Diagrams and tools.

Question types it can appear in

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

These are the questions the flashcard set links to this term. Open each one and compare your answer with its marking criteria.

Study links

How to use it in an answer

A model sentence

General advice, built from the definition and example above

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

From the linked past questions
  • 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)

Technique for the question types

What the marking guidelines and feedback say

Sample exam Q10 (2 marks): Structure charts

Know the notation: rectangle = module; arrow with open circle = data couple; arrow with filled circle = control flag; diamond = selection; curved arrow = iteration.

2023 Software Design and Development HSC Q27 (10 marks): User interface, structure chart, quality assurance

Old-syllabus question. Use for practice on the overlapping skill only. The new Software Engineering exam does not use the old SDD terms (e.g. CASE tools, system flowcharts, EBNF, assembly).

2024 Software Design and Development HSC Q25 (4 marks): Documentation

Old-syllabus question. Use for practice on the overlapping skill only. The new Software Engineering exam does not use the old SDD terms (e.g. CASE tools, system flowcharts, EBNF, assembly).

Common mistakes

Marker feedback on other questions of the same type (code and diagram feedback often applies across questions)
  • Drawing questions (2025 HSC exam Q22): refine attributes into separate inherited classes; use appropriate class diagram symbols.
General advice
  • Use the term exactly as the syllabus words it, then link it to the scenario in the question; the 2025 feedback repeatedly rewards using the stimulus.
  • Answer the command word: outline gives main points only, explain gives a reason or cause, discuss gives both sides.

Same group in the syllabus: Structure chart data couple (empty circle) · Structure chart flag (filled circle) · Structure chart decision (diamond) · Structure chart repetition (curved arrow) · Refinement