Solution Functional Requirements
Name:
Date:
Class:
A
Quick Questions
Shade in the A or B circle for each question.
1. Does a functional requirement describe what a system must do?
2. Which is a functional requirement: 'the system must send an email' or 'the system must look modern'?
3. Should a functional requirement be specific and testable?
4. Are functional requirements written before or after development begins?
5. Are functional requirements derived from identified user needs?
B
Match the Pairs
Draw a line connecting each item on the left to its match on the right.
| Left column | Right column | |
|---|---|---|
| 1The system must allow users to log in | AFunctional requirements must describe specific, testable actions, not vague qualities | |
| 2The system must send a confirmation email | BA functional requirement describing an email-sending action | |
| 3A statement describing a specific, testable action a system must perform | CA functional requirement describing a login action | |
| 4A requirement based on identified user needs before development begins | DAppearance-based statements are non-functional, not functional, requirements | |
| 5The requirement was written as 'the system should be nice to use' | EThe system must allow users to search for items | |
| 6A requirement said 'the app must be colourful and modern' | FThe system must let users book a slot |
C
Definitions
Functional requirement
D
Fill in the Blanks
Complete each line of code by filling in the missing parts.
1.
The system ____ allow users to log in
2.
The system must let users ____ a slot
3.
The system must send a ____________ email
4.
A functional requirement describes what a
system must __
5.
Functional requirements are derived from
user _____
E
Spot the Error
Shade in the letter of the line that contains an error.
Question 1
A
It is always about how the system looks, not what it does.
B
A functional requirement describes what a system must do.
C
It describes a specific action or feature.
D
It can be tested to check if it has been met.
Question 2
A
Functional requirements are derived from user needs.
B
They are impossible to check once the system is built.
C
They guide what features must be built.
D
They should be specific and testable.
Question 3
A
"The system must allow login" is a functional requirement.
B
Functional requirements describe specific actions.
C
"The system must be fast" is a functional requirement.
D
They focus on features, not general qualities.
Question 4
A
Functional requirements list what a system must do.
B
Each requirement should be clear and specific.
C
A vague requirement is hard to test.
D
Vague requirements are always the best kind to write.
Question 5
A
"Send a confirmation email" is a functional requirement.
B
It describes a specific system action.
C
It can be tested by checking if the email is sent.
D
Functional requirements are usually written as clear statements.
E
Functional requirements never involve user actions like logging in.
Answer Key
Solution Functional Requirements
Section A: Quick Questions
Q1
B — True
Q2
A — Must send an email
Q3
B — Yes
Q4
A — Before
Q5
A — True
Section B: Match the Pairs
Q1
The system must allow users to log in → A functional requirement describing a login action
Q2
The system must send a confirmation email → A functional requirement describing an email-sending action
Q3
A statement describing a specific, testable action a system must perform → The system must let users book a slot
Q4
A requirement based on identified user needs before development begins → The system must allow users to search for items
Q5
The requirement was written as 'the system should be nice to use' → Functional requirements must describe specific, testable actions, not vague qualities
Q6
A requirement said 'the app must be colourful and modern' → Appearance-based statements are non-functional, not functional, requirements
Section C: Definitions
Q1
Functional requirement — A specific action, task, or feature that a solution must be able to performSection D: Fill in the Blanks
Q1
The system must allow users to log inQ2
The system must let users book a slotQ3
The system must send a confirmation emailQ4
A functional requirement describes what a
system must doQ5
Functional requirements are derived from
user needsSection E: Spot the Error
Q1
A — A functional requirement is about what the system does, not how it looks — appearance belongs to non-functional requirements.
Q2
B — Functional requirements can and should be checked once the system is built, to confirm they've been met.
Q3
C — "The system must be fast" describes a quality, not a specific action, so it's a non-functional requirement instead.
Q4
D — Vague requirements are hard to test and should be avoided — clear, specific requirements are preferred.
Q5
E — Functional requirements often involve user actions, like logging in or booking, since these describe what the system enables users to do.