Software Engineering › Key terms › Y12 SE Project › Boundaries
Boundaries
Term Y12 SE Project
Definition
What is included in the solution and what is not (its scope).
Example: The system covers booking, not payment.
Found in: syllabus, sample exam and familiarisation guidelines, school notes, past SDD papers.
Where it is used in the test
Syllabus area: Y12 SE Project.
Question types it can appear in
- Short answer: Define, outline or explain it and tie it to the scenario.
- Multiple choice: Pick the option that matches the definition or example.
No past question in this bank is linked to this term yet. It can still be tested through the question types above.
Other questions that mention it
- Familiarisation Q5 The Software Engineering Project (Part C) · 3 marks
- Sample exam Q11 The Software Engineering Project (Part B) · 3 marks
Study links
- Flashcard: Boundaries in The Software Engineering Project (Year 12) · study that set
- Memorise: Define and analyse the requirements of a problem
- Notes: Define and analyse the requirements of a problem, including demonstrating need(s) or… (The Software Engineering Project (Year 12))
- Master answer: fam-q5 (3 marks, table (test data)) (Master model answers: code, SQL, pseudocode, diagrams and tables)
- Notes: Explore by implementation how patterns in human behaviour influence ML and AI software… (Software Automation (Year 12))
- Notes: Define and analyse the requirements of a problem (The Software Engineering Project (Year 12))
How to use it in an answer
A model sentence
“What is included in the solution and what is not (its scope).” Then apply it: The system covers booking, not payment.
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
- 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.
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: Requirements · Need or opportunity · Feasibility · Functionality and performance requirements · Data structures and data types (defining) · Brainstorming, mind-mapping and storyboards · Data dictionary · Code generation · Installation · Maintenance