Software Engineering › Key terms › Y11 Programming Fundamentals › Flowchart
Flowchart
Term Diagram Y11 Programming Fundamentals Diagrams and tools
Definition
Flowchart Y11 Programming Fundamentals Term
A diagram of an algorithm drawn with standard symbols (terminator, process, input/output, decision) joined by arrows, read top to bottom and left to right. Decision arrows must be labelled (Yes/No).
Example: Check there is one Start, one End, labelled decision branches and arrowheads on every line.
Found in: syllabus, course specifications, school notes, past SDD papers.
Flowchart Diagrams and tools Diagram
Represents an algorithm with standard symbols connected by lines with arrowheads, read top to bottom and left to right, using only the standard control structures. Label arrows leaving a decision (Yes or No).
Example: Diamond: age >= 18? Yes: Display Adult.
Found in: syllabus, course specifications, past SDD papers.
Where it is used in the test
Syllabus area: Y11 Programming Fundamentals Diagrams and tools.
Question types it can appear in
- Drawing: Flowchart: Draw or complete a flowchart in the drawing tool Flowchart: Draw a flowchart
- Multiple choice: Pick the option that matches the definition or example.
- Code reading: Code or algorithm reading: interpret a fragment and state its output or purpose.
- Short answer: Define, outline or explain it and tie it to the scenario.
Where it has appeared in the paper
The Software Engineering Project (Part D). Part letters follow each paper’s own layout.
Related past questions
- 2021 Software Design and Development HSC Q22 (3 marks): Testing (live test data) The Software Engineering Project (Part D) · 3 marks · old syllabus
These are the questions the flashcard set links to this term. Open each one and compare your answer with its marking criteria.
Other questions that mention it
- 2023 Software Design and Development Q23 Secure Software Architecture (Part D) · 5 marks · old syllabus
- 2021 Software Design and Development Q24 The Software Engineering Project (Part D) · 3 marks · old syllabus
- 2021 Software Design and Development Q25 Secure Software Architecture (Part D) · 11 marks · old syllabus
- 2021 Software Design and Development Q26 The Software Engineering Project (Part D) · 4 marks · old syllabus
- 2021 Software Design and Development Q28 The Software Engineering Project (Part D) · 5 marks · old syllabus
- 2021 Software Design and Development Q29 The Software Engineering Project (Part D) · 3 marks · old syllabus
Study links
- Flashcard: Flowchart in Programming Fundamentals (Year 11) · study that set
- Flashcard: Flowchart in Diagrams and Modelling Tools (Years 11 and 12) · study that set
- Memorise: Software development steps and algorithm design
- Memorise: Drawing rules: DFD, structure chart, storyboard, decision tree, class diagram, ERD
- Master answer: sdd2023-q23 (5 marks, short answer / extended) (Master model answers: Secure Software Architecture)
- Notes: Flowchart rules (Pseudocode, flowcharts and diagram rules)
- Notes: Modelling tools: DFD, structure charts, storyboards, flowcharts, class diagrams (The Software Engineering Project (Year 12))
- Notes: Key Points (Pseudocode, flowcharts and diagram rules)
How to use it in an answer
A model sentence
“A diagram of an algorithm drawn with standard symbols (terminator, process, input/output, decision) joined by arrows, read top to bottom and left to right.” Then apply it: Check there is one Start, one End, labelled decision branches and arrowheads on every line.
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. (2021 Software Design and Development HSC Q22 (3 marks): Testing (live test data))
Technique for the question types
- Drawing: Use the online drawing tool: label every symbol and arrow, use the correct symbols from the specification, and add every required item.
- Multiple choice: Read all four options, rule out wrong ones, pick one; no penalty for guessing so never leave blank.
- Short answer: One clear point per mark, use the stimulus and course terms, and answer the command word.
What the marking guidelines and feedback say
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
- Drawing questions (2025 HSC exam Q22): refine attributes into separate inherited classes; use appropriate class diagram symbols.
- 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.
Related terms
Same group in the syllabus: Computational thinking · Algorithm · Sequence · Selection · Iteration (repetition) · Divide and conquer · Backtracking · Top-down design · Bottom-up design · Abstraction · Refinement · Pseudocode · Subroutine (module, subprogram, procedure) · Function v procedure