Software Engineering › Key terms › Y12 SE Project › Requirements
Requirements
Term Y12 SE Project
Definition
What the solution must do (functionality) and how well (performance), found by analysing the problem.
Example: The app must show results within 2 seconds.
Found in: syllabus, 2025 HSC marking guidelines, 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.
- Extended response: Use it as a supporting point linked to the stimulus.
- Multiple choice: Pick the option that matches the definition or example.
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 Q25 (11 marks): Development approach, implementation, testing, quality of experience The Software Engineering Project (Part D) · 11 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: Requirements in The Software Engineering Project (Year 12) · study that set
- Memorise: Define and analyse the requirements of a problem
How to use it in an answer
A model sentence
“What the solution must do (functionality) and how well (performance), found by analysing the problem.” Then apply it: The app must show results within 2 seconds.
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 and extended response 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.
- Extended response: Plan with the command word, give a judgement or explanation supported by named details from the stimulus, use course terms and cover both sides when asked.
- 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
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: Need or opportunity · Feasibility · Functionality and performance requirements · Boundaries · Data structures and data types (defining) · Brainstorming, mind-mapping and storyboards · Data dictionary · Code generation · Installation · Maintenance