Requirements, Analysis and Specification
Investigating a substantial problem, defining users and constraints, modelling the existing situation and writing measurable requirements and success criteria.
How to study A-level Computer Science
Define the problem and representation, trace the state change, justify the algorithm or architecture, then test the result against requirements, evidence and constraints.
Core concepts
Concept 1
Problem analysis establishes the real need, stakeholders, current process, data, constraints and feasible scope.
Exam cue: Gather evidence from relevant users or sources and record how it changes the requirements.
Concept 2
A specification translates the analysis into clear functional and non-functional requirements.
Exam cue: Write each requirement so an independent reviewer can decide whether it is satisfied.
Concept 3
Measurable success criteria make later testing and evaluation traceable to the original purpose.
Exam cue: Control scope by separating essential outcomes from optional extensions.
Risk pitfalls and guardrails
Choosing a technology before understanding the problem.
Guardrail: Do not substitute a memorised definition or generic advantage until you have identified the input, state, stakeholder and constraint in the task.
Writing vague objectives such as easy to use without a measurable criterion.
Guardrail: Do not substitute a memorised definition or generic advantage until you have identified the input, state, stakeholder and constraint in the task.
Describing the proposed interface instead of analysing user and data needs.
Guardrail: Do not substitute a memorised definition or generic advantage until you have identified the input, state, stakeholder and constraint in the task.
Memory anchors
Requirement
A requirement states a capability or constraint the solution must satisfy.
Functional Requirement
A functional requirement describes behaviour or a service the system must provide.
Non-functional Requirement
A non-functional requirement constrains qualities such as performance, usability or security.
Success Criterion
A success criterion is a measurable condition used to judge the completed solution.
Scope
Scope defines what the project includes, excludes and can realistically deliver.
Checkpoint rule
Do the check-up only after you can summarize each concept in one sentence and identify one dangerous pitfall from memory.
Knowledge Check (after reading)
Short check-up to confirm understanding of this module.
Check-up Questions
What is the purpose of requirements analysis?
A booking system affects customers, staff, funders and support teams. Which description identifies who counts as a stakeholder?
Answer all questions to submit.
Next step personalized recommendations
Continue learning
Move forward only after this module is stable.
What is Pass Harbor?
Completely free exam prep for 247 UK exams.
- Practice questions
- Flashcards
- Study guides
- Mock exams
- No registration
- No paywall
- Start instantly
“No more expensive exam prep. Quality study tools should be accessible to everyone.”