Software Engineering › Key terms › Y11 Programming Fundamentals › Requirements definition
Requirements definition
Process Y11 Programming Fundamentals
Definition
Finding out what the client needs: gathering and documenting the problem, users, functional and non-functional requirements and constraints (client scenario, environment, objectives).
Example: Outline pattern: 'Meet the client and document what the software must do, such as login and data storage.'
Found in: syllabus, school notes.
Where it is used in the test
Syllabus area: Y11 Programming Fundamentals.
Question types it can appear in
- Multiple choice: Which task belongs to requirements definition?
- Fill in the blanks: Choose this term to complete a statement or table.
- Short answer: Outline the purpose of this step
Where it has appeared in the paper
The Software Engineering Project (Part B); Secure Software Architecture (Part C). Part letters follow each paper’s own layout.
Related past questions
- Sample exam Q1 (1 mark): Software development steps The Software Engineering Project (Part B) · 1 mark
- Familiarisation Q1 (1 mark): Development steps Secure Software Architecture (Part C) · 1 mark
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 definition in Programming Fundamentals (Year 11) · study that set
- Memorise: Software development steps and algorithm design
- Notes: Fundamental software development steps for secure code (Secure Software Architecture (Year 12))
- Notes: Interpret and apply fundamental software development steps to develop secure code,… (Secure Software Architecture (Year 12))
- Notes: Software development steps and algorithm design (Year 11 content (Programming fundamentals, OOP, Mechatronics))
How to use it in an answer
A model sentence
“Finding out what the client needs: gathering and documenting the problem, users, functional and non-functional requirements and constraints (client scenario, environment, objectives).” Then apply it: Outline pattern: 'Meet the client and document what the software must do, such as login and data storage.'
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
- Identify: Recognise and name. (Sample exam Q1 (1 mark): Software development steps)
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
Know the order of the software development cycle: define and understand the problem (requirements) -> plan and design -> develop/construct -> test and evaluate -> deploy/implement -> maintain.
Worked answers from the marking guidelines
Sample exam Q1 (1 mark): Software development steps (1 mark): criteria and sample answer
Criteria
1: Identifies the correct answer.
Sample answer
Documenting the needs and constraints of the software
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: Software development steps (the order) · Determining specifications · Design · Development · Integration · Testing and debugging · Installation · Maintenance · Online code collaboration tools