Software Engineering › Learn step by step › Y11 Programming Fundamentals
Item 48 of 426 · Year 11: Programming Fundamentals, 2 of 69
Requirements definition
Process
Jump to a topic
- Exam format, question types and command words (46)
- Year 11: Programming Fundamentals (69)
- Year 11: The Object-Oriented Paradigm (33)
- Year 11: Programming Mechatronics (29)
- Year 12: Secure Software Architecture (57)
- Year 12: Programming for the Web (59)
- Year 12: Software Automation (35)
- Year 12: The Software Engineering Project (47)
- Diagrams and modelling tools (18)
- Python, SQL, pseudocode and CSS patterns (33)
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 you'll use it 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
How to use it
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)
Official worked answer
Sample exam Q1 (1 mark): Software development steps (1 mark): official criteria and sample answer
Criteria
1: Identifies the correct answer.
Sample answer
Documenting the needs and constraints of the software
Go deeper
- 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))
- Full term page: every question, note and marking comment for Requirements definition
Check yourself
Say the steps or stages of “Requirements definition” in order.
Reveal the answer
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.'
Could be tested as: Multiple choice, Fill in the blanks, Short answer.
Quick multiple choice
Which of the following should take place during the requirements definition step when developing a software solution?
- Identifying algorithms to be used
- Documenting security vulnerabilities
- Identifying potential security threats in the software
- Documenting the needs and constraints of the software
Show the answer
D
NESA answer: documenting the needs and constraints of the software.
Source: NESA Sample Exam (Software Engineering 2022 syllabus) questions and Marking Guidelines. Open it in the multiple-choice bank.