Software Engineering › Key terms › Y11 OOP › Clear and uncluttered mainline
Clear and uncluttered mainline
Term Y11 OOP
Definition
A mainline that only calls well-named subroutines or methods in order, so the overall flow is easy to follow.
Example: Keep the mainline to a few calls; put detail in subroutines.
Found in: syllabus.
Where it is used in the test
Syllabus area: Y11 OOP.
Question types it can appear in
- Multiple choice: Pick the option that matches the definition or example.
- Multi-select: You tick every correct option, so know all its features or goals.
- Pseudocode: Use it correctly in the exam pseudocode editor.
- Python: Write or complete it in the online Python tool.
Where it has appeared in the paper
The Software Engineering Project (Part B). Part letters follow each paper’s own layout.
Related past questions
- Sample exam Q14 (3 marks): Algorithm design (subroutines) The Software Engineering Project (Part B) · 3 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: Clear and uncluttered mainline in The Object-Oriented Paradigm (Year 11) · study that set
- Memorise: Testing and code quality (Year 11)
- Notes: Object-oriented concepts (Year 11 content (Programming fundamentals, OOP, Mechatronics))
How to use it in an answer
A model sentence
“A mainline that only calls well-named subroutines or methods in order, so the overall flow is easy to follow.” Then apply it: Keep the mainline to a few calls; put detail in subroutines.
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.
Technique for the question types
- Multiple choice: Read all four options, rule out wrong ones, pick one; no penalty for guessing so never leave blank.
- Multi-select: Pick ALL correct options; the guideline marks it right only if you tick every correct one (and no wrong one).
- Pseudocode: Write HSC-style pseudocode: capital keywords, paired END words, indentation; initialise variables; output the required result.
- Python: Write code that runs: indentation, quotes, define functions before calling them, print the required output, meet every listed requirement.
Worked answers from the marking guidelines
Sample exam Q14 (3 marks): Algorithm design (subroutines) (3 marks): criteria and sample answer
Criteria
3: Substantially correct pseudocode that includes at least ONE subroutine. 2: Addresses some of the requirements. 1: Some understanding of the problem.
Sample answer
BEGIN main Get num_pizzas total_cost = 0 FOR i = 1 TO num_pizzas Get pizza_size Get num_toppings cost_per_pizza = calculate_pizza_cost(pizza_size, num_toppings) DISPLAY cost_per_pizza total_cost = total_cost + cost_per_pizza NEXT i DISPLAY total_cost END main
BEGIN calculate_pizza_cost(size, num_toppings) base_price = 10 topping_price = 1.5 IF size = "Medium" THEN base_price = base_price + 2 ELSEIF size = "Large" THEN base_price = base_price + 4 ENDIF pizza_cost = base_price + num_toppings * topping_price RETURN pizza_cost END calculate_pizza_cost
Common mistakes
- 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.
- Python questions (2025 HSC exam Q19): process string inputs; use a selection structure; code must execute in the environment; use correct indentation; call functions in the main program after defining them.
- Python questions (2025 HSC exam Q26): replicate the grid; use the random library; use selection and looping to access the list; include a method of checking the number of values; use meaningful variable names and constants; avoid overly complex structures such as nested IF loops.
- 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: One logical task per subroutine · Stub · Ease of maintenance · Regular backup · Unit testing · Subsystem testing · System testing · Black box testing · White box testing · Grey box testing · Quality assurance