Software Engineering › Key terms › Y11 Programming Fundamentals › Refinement
Refinement
Term Diagram Y11 Programming Fundamentals Diagrams and tools
Definition
Refinement Y11 Programming Fundamentals Term
Adding successively more detail: a subroutine is expanded into its own algorithm or structure chart, named the same as the subroutine.
Example: Show the refinement of the Validate subroutine in a separate chart.
Found in: syllabus, course specifications, school notes.
Refinement Diagrams and tools Diagram
Providing successively more detail as needed; a lower-level subroutine is shown in its own structure chart with the same name.
Example: Expand Validate Input into its own chart.
Found in: syllabus, course specifications, school notes.
Where it is used in the test
Syllabus area: Y11 Programming Fundamentals Diagrams and tools.
Question types it can appear in
- Drawing: Refinement: structure chart Refinement: Draw or label it in the online drawing tool.
- Pseudocode: Use it correctly in the exam pseudocode editor.
- 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). Part letters follow each paper’s own layout.
Related past questions
- Familiarisation Q4 (2 marks): Structure charts The Software Engineering Project (Part C) · 2 marks
- Sample exam Q10 (2 marks): Structure charts The Software Engineering Project (Part B) · 2 marks
These are the questions the flashcard set links to this term. Open each one and compare your answer with its marking criteria.
Study links
- Flashcard: Refinement in Programming Fundamentals (Year 11) · study that set
- Flashcard: Refinement 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
- Notes: Modelling tools: DFD, structure charts, storyboards, flowcharts, class diagrams (The Software Engineering Project (Year 12))
- Notes: Pseudocode rules (Pseudocode, flowcharts and diagram rules)
- Notes: Drawing rules: DFD, structure chart, storyboard, decision tree, class diagram, ERD (Pseudocode, flowcharts and diagram rules)
How to use it in an answer
A model sentence
“Adding successively more detail: a subroutine is expanded into its own algorithm or structure chart, named the same as the subroutine.” Then apply it: Show the refinement of the Validate subroutine in a separate chart.
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
No linked question shows the command word for this term. Across the past drawing and pseudocode and short answer questions in this bank the words used most are: Explain, Outline, Describe, Compare, Classify, Analyse. Check the actual word in your question.
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.
- Pseudocode: Write HSC-style pseudocode: capital keywords, paired END words, indentation; initialise variables; output the required result.
- Short answer: One clear point per mark, use the stimulus and course terms, and answer the command word.
- Multiple choice: Read all four options, rule out wrong ones, pick one; no penalty for guessing so never leave blank.
What the marking guidelines and feedback say
Know the notation: rectangle = module; arrow with open circle = data couple; arrow with filled circle = control flag; diamond = selection; curved arrow = iteration.
Common mistakes
- Drawing questions (2025 HSC exam Q22): refine attributes into separate inherited classes; use appropriate class diagram symbols.
- Pseudocode questions (2025 HSC exam Q17): use pseudocode control structures accurately; iterate an array and sum it; apply relational operators correctly; use the stimulus to choose the right structures.
- 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 · Pseudocode · Flowchart · Subroutine (module, subprogram, procedure) · Function v procedure