Nexus Learn

Practical 8: Writing an SRS II: Non-functional Requirements and Review

Lab Practical SE-401 Software Engineering 8 min read Updated 8 Nov 2026
On this page
  1. 1. Objectives
  2. 2. Word bank
  3. 3. Background
  4. 4. Before you start
  5. 5. Time plan (50 minutes)
  6. Part A: Warm-up: name the NFR category
  7. Part B: Predict: what happens if ...?
  8. Part C: Find the flaw: which SRS quality is broken?
  9. Part D: Graded tasks (10 marks)
  10. Part E: Post-lab questions
  11. Marking rubric
  12. Submission

How you work today

Work in your project team on your own SRS. In Task 3 your team swaps SRS files with another team named by the teacher and reviews it. Marks are given to each student.

1. Objectives

By the end of this practical you will be able to:

  • Write non-functional requirements that can be measured and tested.
  • Check an SRS against the qualities of a good SRS (correct, unambiguous, complete, consistent, ranked, verifiable, modifiable, traceable).
  • Build a traceability matrix from user stories to functional requirements.
  • Carry out a peer review and record problems in a review log.

2. Word bank

Word

Simple meaning

Real-world example

non-functional requirement

how well the system must work, or a limit on it

The menu shall load within 2 seconds on 4G.

measurable

has a number or clear test, so you can check it

'within 2 seconds' instead of 'fast'

verifiable

someone can test it and say pass or fail

5 new users each order within 2 minutes

unambiguous

has only one possible meaning

'send an SMS' instead of 'notify'

consistent

no two requirements contradict each other

cancel rules in FR-09 and FR-12 agree

traceability matrix

a table linking each user story to its requirements

US-02 → FR-03, FR-04, FR-05

peer review

checking another team's work to find problems

Team B reviews Team A's SRS

availability

the share of time the system can be used

99% between 8 a.m. and 5 p.m.

3. Background

In Practical 07 you wrote what your system must do (functional requirements). Today you write how well it must do it (non-functional requirements), link everything back to your user stories, and let another team review your SRS. A review is one of the umbrella activities from Lecture 08 (technical reviews).

Common NFR categories and how to make them measurable (based on Sommerville's metrics table):

Category

Vague (bad)

Measurable (good)

Performance

"The app shall be fast."

The menu shall load within 2 seconds on 4G for 95% of requests.

Capacity / load

"It shall handle many users."

The system shall accept 200 orders between 1:00 and 1:10 p.m. without errors.

Usability

"It shall be easy to use."

A first-time user shall place an order within 2 minutes without help.

Availability

"It shall always work."

Available 99% of the time between 8 a.m. and 5 p.m. on working days.

Security

"It shall be secure."

Passwords shall be stored only as salted hashes; all traffic shall use HTTPS.

Compatibility

"It shall work on phones."

The app shall run on Android 8.0 and later.

Qualities of a good SRS (IEEE 830). Use them as a checklist in your review:

Quality

Ask yourself

Correct

Does every requirement describe something the client really needs?

Unambiguous

Can each requirement be understood in only ONE way?

Complete

Is anything important missing (e.g. what happens when payment fails)?

Consistent

Do any two requirements contradict each other?

Ranked

Does each requirement have a priority (Must / Should / Could)?

Verifiable

Can a tester check each requirement and say pass or fail?

Modifiable

Is it organised (IDs, sections) so changes are easy?

Traceable

Does each requirement show where it came from (user story or stakeholder)?

Real-world example: a review comment that helps

Bad: "FR-07 is wrong."

Good: "FR-07 (unambiguous): 'notify the user' can mean SMS, e-mail or an in-app message. Suggest: 'shall send an in-app notification within 10 seconds'."

A good review comment says WHERE, WHICH quality is broken, WHAT the problem is, and a FIX.

Word help

metric = a measurement used to check a requirement

contradict = say the opposite

4. Before you start

1. Open your team's SRS from Practical 07 (SRS_<TeamName>_v1).

2. Have your Trello board open to check user story IDs.

3. The teacher will name the team whose SRS you review in Task 3 and share files at 0:30.

5. Time plan (50 minutes)

Time

What you do

0:00-0:05

Teacher: vague vs measurable NFRs; the SRS quality checklist

0:05-0:15

Parts A, B and C (on paper)

0:15-0:22

Task 1: make three vague NFRs measurable

0:22-0:30

Task 2: five NFRs for your project (section 4)

0:30-0:45

Task 3: peer review of another team's SRS, then your traceability matrix

0:45-0:50

Teacher checks; start Part E (finish at home)

Part A: Warm-up: name the NFR category

For the bus-booking app from Practical 07, write the category of each NFR: performance, usability, security, availability, compatibility or capacity.

(a) The seat map shall load within 3 seconds on 4G.

(b) Passengers' CNIC numbers shall be stored in encrypted form.

(c) The system shall accept 500 bookings in the hour before Eid without errors.

(d) A passenger who has never used the app shall book a seat within 3 minutes.

(e) The booking service shall be available 99.5% of the time.

Part B: Predict: what happens if ...?

Predict the result of each SRS problem.

(a) The SRS says "The app shall be fast." At the end of the project the client says it is too slow; the team says it is fast. Who wins, and why?

(b) FR-09 says "Users can cancel an order at any time before pickup." FR-12 says "Orders cannot be cancelled after cooking starts." What will the developer do?

Part C: Find the flaw: which SRS quality is broken?

Name the main SRS quality each item breaks (unambiguous, complete, consistent, verifiable, traceable, ranked) and suggest a fix.

(1) NFR-03: "The system shall be secure."

(2) FR-11 has no value in the Source column, and no user story mentions it.

(3) The SRS describes paying by wallet but says nothing about what happens if the payment fails.

(4) FR-05: "The system shall show the pickup time in a suitable format."

Part D: Graded tasks (10 marks)

Task

Level

What you build

Marks

T1

Easy

Make three vague NFRs measurable

3

T2

Medium

Section 4: five non-functional requirements

3

T3

Challenge

Peer review and traceability

4

Total

10

T1 Make three vague NFRs measurable (3 marks · Easy)

1. Rewrite each of these for your project so it contains a number and can be tested: (a) "The system shall be fast." (b) "The system shall be easy to use." (c) "The system shall always be available."

2. Under each rewrite, write in one line how you would test it.

Sample: Model answer (cafeteria app)

(a) The menu shall load within 2 seconds on 4G for 95% of requests. Test: time 20 loads.

(b) A first-time student shall place an order within 2 minutes without help. Test: 5 new students with a stopwatch.

(c) The system shall be available 99% of the time between 8 a.m. and 5 p.m. on working days. Test: uptime monitor for a month.

T2 Section 4: five non-functional requirements (3 marks · Medium)

1. In section 4 of your SRS, write at least 5 NFRs (NFR-01 ...) from at least 4 different categories.

2. Each NFR has a measure and a test method in the last column.

3. Do not repeat T1 word for word; you may improve them.

Sample: Model rows (cafeteria app)

NFR-02 · Performance (load) · The system shall accept 200 orders placed between 1:00 and 1:10 p.m. without errors. · Load test with a script.

NFR-03 · Security · The system shall not store wallet PINs or card numbers; payment shall use only the provider's API over HTTPS. · Code review and database inspection.

T3 Peer review and traceability (4 marks · Challenge)

1. Open the other team's SRS. Use the eight SRS qualities as a checklist.

2. In section 6 (Review log) of THEIR file, record at least 4 problems: where (ID or section), which quality is broken, the problem, and a suggested fix. Each member of your team writes at least one entry.

3. Back in YOUR SRS, fill section 5 (traceability matrix): every user story → its FR IDs. Mark any story with no FR and any FR with no story.

4. Fix 2 problems in your own SRS (from your matrix or the review you received) and save as SRS_<TeamName>_v2.

Sample: Review log entry

Where: FR-07 · Quality: Unambiguous · Problem: 'notify' does not say how · Fix: 'shall send an in-app notification within 10 seconds'.

Traceability (model): US-02 → FR-03, FR-04, FR-05; US-08 → FR-10.

Part E: Post-lab questions

1. Why must a non-functional requirement contain a measure?

2. What is a traceability matrix, and how does it help when a requirement changes?

3. Which umbrella activity from Lecture 08 did you carry out today? Give one benefit.

Marking rubric

Task

Marks

Full marks when ...

T1 Make three vague NFRs measurable

3

1 mark per NFR with a measure and a matching test

T2 Section 4: five non-functional requirements

3

1 mark: 5+ NFRs from 4+ categories

1 mark: every NFR measurable

1 mark: every NFR has a matching test method

T3 Peer review and traceability

4

1 mark: 4+ useful review entries (own entry checked individually)

1 mark: qualities named correctly with fixes

1 mark: complete traceability matrix

1 mark: two fixes made and saved as v2

Parts A, B, C and E are not marked separately; they prepare you for the tasks and the viva.

Submission

  • The teacher checks your section 4, your traceability matrix and the review log you wrote for the other team.
  • Upload SRS_<TeamName>_v2.docx to the LMS by the end of the day. Return the reviewed file to the other team.
  • Copy your NFRs from Task 1 and your own review entry into the Lab Book (Practical 08 page).
  • Keep the SRS. Later practicals (DFD, ERD, use cases) build on it.

← All SE-401 material