← VCE Software Development U3O2

SRS content: requirements, constraints and scope

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).

Understanding SRS content: requirements, constraints and scope in VCE Software Development U3O2

What it does: A budget cap is an economic constraint, so it belongs in the constraints section of the SRS. A response time target is a measurable non-functional requirement, so it is recorded in the requirements section. The SRS content covers functional and non-functional requirements, the constraints on the solution, and the scope. Together these give a complete picture of what is to be built. The existing hardware and operating system limit how the solution can be built, so this is a technical constraint. It is not a feature the user interacts with. Requirements in an SRS should be clear and specific enough to check. Vague words such as 'easy' and 'nice' cannot be tested or measured.

Common mistakes: Ordering lunch is something the system does, so it is a functional requirement. It should be labelled FR1, not NFR1. The lines below are limits on the solution (budget and platform). The heading should be Constraints section, not Scope section.

Class: _____________________  ·  Name: _____________________  ·  Date: _________

Free printable worksheet with full answer key — or add this module to a class and your students practise it interactively.

This module's key terms are also in a printable crossword (Modules 52–71) and word search (Modules 52–85).

Take this worksheet further — free with Cloodit

Each concept is reinforced from every angle — learned, then applied, then tested.

Learning
Duo
Which SRS section lists what the software must do, such as 'the system must let a user reset their password'?
Scope sectionRequirements section (functional requirements)
Matches
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.
Applying
Meanings
Term
SRS content
Meaning
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).
Practice
REQUIREMENTS
Testing
Gaps
SRS Section 1:
Check Answer
Spots
2Requirements section
3NFR1: Users can order lunch

Cloodit turns curriculum-aligned coding content into journeys students work through one biome at a time.

The 'Woolly Mammoth' badge — Tundra Master, one of Cloodit's 106 collectible badges
Students earn collectable badges

Over 100 of them, across seven natural biomes.

Study Buddy
Students build a real study resource

Turns their work into revision material ready for Flash Cards and Exam study.

Diamond Dash — one of Cloodit's live, competitive Sprint games
Students lock in with Sprints

Live, competitive practice for the start of the lesson or a teacher-led lesson finisher.

A Cloodit certificate of achievement, ready to personalise and print
Custom printable certificates

Honour your top performers, or encourage a student who's trying hard — ready to print in seconds.

Quick Questions

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
Functional requirements describe what the solution must do. They sit in the requirements section of the SRS. The scope section states what is and is not included.
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 ✓
Non-functional requirements describe qualities such as speed, security or usability, and should be measurable. The 2-second target is a measurable performance quality.
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
A budget is an economic constraint that limits the solution. A login screen is a feature, so it belongs in the requirements section.
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
The scope section sets the boundaries by stating what is and is not included. Compliance with the Privacy Act is a legal constraint, so it goes in the constraints section.
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 ✓
The SRS content covers functional and non-functional requirements, the constraints on the solution, and the scope. Together these give a complete picture of what is to be built.

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.

Key Term

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).

Fill in the Blanks

1. SRS Section 1: Requirements
Hint: Type the section name that lists what the solution must do and how well it must do it.
2. SRS Section 2: Constraints
Hint: Type the section name for limits on the solution, such as budget, law or technology.
3. SRS Section 3: Scope (in and out)
Hint: Type the section name that sets what is and is not included in the solution.
4. Requirements: Functional: Save the user's score
Hint: Type the requirement type that describes what the system must do.
5. Requirements: Non-functional: Load in 3 seconds
Hint: Type the requirement type that describes how well the system performs or its quality.

Spot the Error

Question 1
A SRS: Canteen Ordering App
B Requirements section
C NFR1: Users can order lunch
D NFR1: Pages load in 2 seconds
Line C — Ordering lunch is something the system does, so it is a functional requirement. It should be labelled FR1, not NFR1.
Question 2
A Scope section
B C1: Budget limited to $5000
C C2: Must run on Windows 10
Line A — The lines below are limits on the solution (budget and platform). The heading should be Constraints section, not Scope section.
Question 3
A Constraints section
B In scope: online booking
C Out of scope: payroll
Line A — The lines list what is included and excluded, which is the scope. The heading should be Scope section, not Constraints section.
Question 4
A Non-functional requirements
B NFR1: Loads very quickly
C NFR2: Uptime of 99% each month
Line B — A non-functional requirement should be measurable. 'Very quickly' cannot be tested. It should state a figure, such as 'Loads within 3 seconds'.
Question 5
A Constraints section
B C1: Must use Python 3
C C2: Users can reset passwords
Line 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'.

Student with a class code? Join your class →