Non-functional requirements

Name:

Date:

Class:

Quick Questions

Shade in the A or B circle for each question.

1. Which one is a non-functional requirement for a school canteen ordering app?

A The app must load the menu in under 3 seconds.

B The app must let students add food to an order.

2. True or false: A non-functional requirement describes how well a solution must work.

A False

B True

3. Which requirement is about usability?

A A Year 7 student should be able to use the app without any help.

B The app must save each student's score to a list.

4. Which requirement is about performance?

A The quiz must show the result within 2 seconds of the last answer.

B The quiz must show the result after the last answer.

5. A game must not crash during a 30-minute play session. What kind of requirement is this?

A Functional (a feature)

B Non-functional (reliability)

Match the Pairs

Draw a line connecting each item on the left to its match on the right.

Left column		Right column
1The app must load in under 2 seconds.		AFunctional: The app lets users save a score. Non-functional: Saving takes under 1 second.
2A new user must be able to use the app without training.		BLoading speed is performance, not usability. A usability requirement should be about ease of use, such as 'Buttons must be big and clearly labelled'.
3A reliability requirement says the solution must keep working without failing.		CThe app must work 99% of the time without crashing.
4A functional requirement says what the solution does, while a non-functional requirement says how well it does it.		DA performance non-functional requirement: it says how fast the solution must work.
5Non-functional requirement: The app must let users send messages.		ESending messages is something the app does, so it is a functional requirement. A non-functional requirement should say how well it works, such as 'Messages must send in under 3 seconds'.
6Usability requirement: The website must load in 1 second.		FA usability non-functional requirement: it says how easy the solution must be to use.

Definitions

non-functional requirement

Fill in the Blanks

Complete each line of code by filling in the missing parts.

A ______________ requirement describes how well a solution must work.

Requirement: Pages must load in 2 seconds. Quality: ___________

Requirement: Buttons must be easy to read. Quality: _________

Requirement: The app must not crash. Quality: ___________

Lets users log in = __________ Loads in 2 seconds = non-functional

Spot the Error

Shade in the letter of the line that contains an error.

Question 1

A App: Canteen order app

B Type: non-functional

C Rule: Students can pay online

Question 2

A Type: non-functional

B Category: usability

C Rule: Site never goes offline

Question 3

A Category: performance

B Rule: Search is quite quick

C Type: non-functional

Question 4

A Category: reliability

B Rule: App must not crash

C Test: Count how fast it loads

Question 5

A Game: Quiz app

B Functional: Loads in 3 seconds

C Non-functional: Easy to read

Answer Key

Non-functional requirements

Section A: Quick Questions

A — The app must load the menu in under 3 seconds.

B — True

A — A Year 7 student should be able to use the app without any help.

A — The quiz must show the result within 2 seconds of the last answer.

B — Non-functional (reliability)

Section B: Match the Pairs

The app must load in under 2 seconds. → A performance non-functional requirement: it says how fast the solution must work.

A new user must be able to use the app without training. → A usability non-functional requirement: it says how easy the solution must be to use.

A reliability requirement says the solution must keep working without failing. → The app must work 99% of the time without crashing.

A functional requirement says what the solution does, while a non-functional requirement says how well it does it. → Functional: The app lets users save a score. Non-functional: Saving takes under 1 second.

Non-functional requirement: The app must let users send messages. → Sending messages is something the app does, so it is a functional requirement. A non-functional requirement should say how well it works, such as 'Messages must send in under 3 seconds'.

Usability requirement: The website must load in 1 second. → Loading speed is performance, not usability. A usability requirement should be about ease of use, such as 'Buttons must be big and clearly labelled'.

Section C: Definitions

non-functional requirement — A rule about how well a solution must work, such as how fast, easy to use or reliable it is. It is not about what the solution does, which is a functional requirement.

Section D: Fill in the Blanks

A non-functional requirement describes
how well a solution must work.

Requirement: Pages must load in 2 seconds.
Quality: performance

Requirement: Buttons must be easy to read.
Quality: usability

Requirement: The app must not crash.
Quality: reliability

Lets users log in = functional
Loads in 2 seconds = non-functional

Section E: Spot the Error

C — Paying online is something the app does, so it is a functional requirement. A non-functional rule describes how well it works, such as 'Pages load in 2 seconds'.

C — Staying online is about reliability, not usability. A usability rule is about ease of use, such as 'Buttons are easy to see'.

B — A performance requirement should be measurable. 'Quite quick' is vague. It should give a clear limit, such as 'Search takes under 2s'.

C — Counting load speed tests performance, not reliability. A reliability test checks that the app keeps working, such as running for 1 hour with no crash.

B — How fast something loads is a non-functional requirement. A functional requirement says what the app does, such as 'Show the score'.