Software Engineering › Key terms › Y11 Programming Fundamentals › IPO chart (Input, Process, Output)
IPO chart (Input, Process, Output)
Term Check Y11 Programming Fundamentals
Definition
A table listing the inputs, the processes applied and the outputs of a system or subroutine; used when determining specifications.
Example: IPO: Input username and password, Process compare with stored hash, Output access granted or denied.
Check this one: Not named in the 2022 syllabus text; taught in the school notes and used in past SDD papers.
Found in: past SDD papers.
Where it is used in the test
Syllabus area: Y11 Programming Fundamentals.
Question types it can appear in
- Drawing: table
- Multiple choice: Pick the option that matches the definition or example.
- 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
- 2022 Software Design and Development HSC Q27 (10 marks): Modelling and design (IPO, data structure, Gantt) The Software Engineering Project (Part D) · 10 marks · old syllabus
- 2024 Software Design and Development HSC Q24 (10 marks): Social and ethical issues The Software Engineering Project (Part D) · 10 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.
Study links
- Flashcard: IPO chart (Input, Process, Output) in Programming Fundamentals (Year 11) · study that set
- Memorise: Software development steps and algorithm design
How to use it in an answer
A model sentence
“A table listing the inputs, the processes applied and the outputs of a system or subroutine; used when determining specifications.” Then apply it: IPO: Input username and password, Process compare with stored hash, Output access granted or denied.
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
- Describe: Provide characteristics and features. (2022 Software Design and Development HSC Q27 (10 marks): Modelling and design (IPO, data structure, Gantt))
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).
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
- Check the sources: Not named in the 2022 syllabus text; taught in the school notes and used in past SDD papers.
- 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 · Flowchart · Subroutine (module, subprogram, procedure)