SRS content: requirements, constraints and scope

Name:

Date:

Class:

Quick Questions

Shade in the A or B circle for each question.

1. Which SRS section lists what the software must do, such as 'the system must let a user reset their password'?

A Requirements section (functional requirements)

B Scope section

2. A student writes 'The app must load each page in under 2 seconds' in an SRS. What type of requirement is it?

A Functional requirement, because it states a feature the system must have

B Non-functional requirement, because it measures how well the system performs

3. Which statement belongs in the constraints section of an SRS?

A The solution must be completed within a budget of $5000

B The solution will include a student login screen

4. Which statement belongs in the scope section of an SRS?

A Version 1 will not include a mobile app version

B The system must comply with the Privacy Act 1988

5. True or false: an SRS only needs to list the functional requirements.

A True: functional requirements are the only content needed

B False: it also covers non-functional requirements, constraints and scope

Match the Pairs

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

Left column		Right column
1SRS requirements section		AStates what is included in the solution and what is not included, so everyone agrees on its boundaries.
2SRS scope section		BThe report must load within 3 seconds.
3A constraint in the SRS limits how the solution can be developed, such as a budget or a legal limit.		CConstraint: Total cost must not exceed $8,000.
4A measurable non-functional requirement in the SRS states how well the solution must perform.		DThis is a functional requirement, not a constraint. A constraint limits the solution, such as budget, law, time or technology.
5Scope: The app will do everything the client might ever want.		EThe scope is vague and unlimited. A scope section must state clearly what is included and what is excluded, so the boundaries are agreed.
6Constraints: The system must let users reset their password.		FLists the functional requirements (what the solution must do) and the non-functional requirements (how well it must perform).

Definitions

SRS content

Fill in the Blanks

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

SRS Section 1: ____________

SRS Section 2: ___________

SRS Section 3: _____ (in and out)

Requirements: __________: Save the user's score

Requirements: ______________: Load in 3 seconds

Spot the Error

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

Question 1

A SRS: Canteen Ordering App

B Requirements section

C NFR1: Users can order lunch

D NFR1: Pages load in 2 seconds

Question 2

A Scope section

B C1: Budget limited to $5000

C C2: Must run on Windows 10

Question 3

A Constraints section

B In scope: online booking

C Out of scope: payroll

Question 4

A Non-functional requirements

B NFR1: Loads very quickly

C NFR2: Uptime of 99% each month

Question 5

A Constraints section

B C1: Must use Python 3

C C2: Users can reset passwords

Answer Key

SRS content: requirements, constraints and scope

Section A: Quick Questions

A — Requirements section (functional requirements)

B — Non-functional requirement, because it measures how well the system performs

A — The solution must be completed within a budget of $5000

A — Version 1 will not include a mobile app version

B — False: it also covers non-functional requirements, constraints and scope

Section B: Match the Pairs

SRS requirements section → Lists the functional requirements (what the solution must do) and the non-functional requirements (how well it must perform).

SRS scope section → States what is included in the solution and what is not included, so everyone agrees on its boundaries.

A constraint in the SRS limits how the solution can be developed, such as a budget or a legal limit. → Constraint: Total cost must not exceed $8,000.

A measurable non-functional requirement in the SRS states how well the solution must perform. → The report must load within 3 seconds.

Scope: The app will do everything the client might ever want. → The scope is vague and unlimited. A scope section must state clearly what is included and what is excluded, so the boundaries are agreed.

Constraints: The system must let users reset their password. → This is a functional requirement, not a constraint. A constraint limits the solution, such as budget, law, time or technology.

Section C: Definitions

SRS content — The parts of an SRS that state the functional and non-functional requirements, the constraints on the solution, and its scope (what is and is not included).

Section D: Fill in the Blanks

SRS Section 1: Requirements

SRS Section 2: Constraints

SRS Section 3: Scope (in and out)

Requirements:
Functional: Save the user's score

Requirements:
Non-functional: Load in 3 seconds

Section E: Spot the Error

C — Ordering lunch is something the system does, so it is a functional requirement. It should be labelled FR1, not NFR1.

A — The lines below are limits on the solution (budget and platform). The heading should be Constraints section, not Scope section.

A — The lines list what is included and excluded, which is the scope. The heading should be Scope section, not Constraints section.

B — A non-functional requirement should be measurable. 'Very quickly' cannot be tested. It should state a figure, such as 'Loads within 3 seconds'.

C — Resetting passwords is a function of the system, so it belongs in the requirements section. A constraint is a limit such as budget or technology, e.g. 'Budget is under $3000'.