Software Engineering › Key terms › Y11 Programming Fundamentals › Divide and conquer
Divide and conquer
Term Y11 Programming Fundamentals
Definition
Breaking a large problem into smaller sub-problems, solving each one and combining the results (for example binary search or splitting a program into subroutines).
Example: Use it to explain why a program is split into subroutines.
Found in: syllabus.
Where it is used in the test
Syllabus area: Y11 Programming Fundamentals.
Question types it can appear in
- Multiple choice: Pick the option that matches the definition or example.
- Fill in the blanks: Choose this term to complete a statement or table.
- Short answer: Describe the technique
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 Q28 (5 marks): Debugging an algorithm (binary search) The Software Engineering Project (Part D) · 5 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: Divide and conquer in Programming Fundamentals (Year 11) · study that set
- Memorise: Software development steps and algorithm design
- Notes: Software development steps and algorithm design (Year 11 content (Programming fundamentals, OOP, Mechatronics))
How to use it in an answer
A model sentence
“Breaking a large problem into smaller sub-problems, solving each one and combining the results (for example binary search or splitting a program into subroutines).” Then apply it: Use it to explain why a program is split into 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.
Command words used with it
No linked question shows the command word for this term. Across the past 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
- Multiple choice: Read all four options, rule out wrong ones, pick one; no penalty for guessing so never leave blank.
- Fill in the blanks: Choose the right word from a list; use exact syllabus terms.
- 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
- 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) · Backtracking · Top-down design · Bottom-up design · Abstraction · Refinement · Pseudocode · Flowchart · Subroutine (module, subprogram, procedure) · Function v procedure