Purpose of a software requirements specification (SRS)

Name:

Date:

Class:

Quick Questions

Shade in the A or B circle for each question.

1. What is the main purpose of a software requirements specification (SRS)?

A To record what the software must do so client and developer share the same understanding

B To store the finished source code of the software

2. Which statement about an SRS is correct?

A It is written by the developer alone and never shown to the client

B It acts as an agreement between the client and the developer

3. How does the design stage use the SRS?

A It is ignored until the software is finished

B It is the basis for design: designers work from the listed requirements

4. How is an SRS used in testing?

A Tests are based on the requirements to check the software does what was specified

B Testers decide for themselves what the software should do

5. A developer is unsure whether a feature is part of the project. What should they do?

A Check the SRS as a reference during development

B Guess based on memory of an earlier conversation

Match the Pairs

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

Left column		Right column
1Software requirements specification (SRS)		AAn SRS is a formal written document. If it is not recorded, the client and developer have no shared, agreed understanding.
2Client signs off the SRS		BDeveloper checks SRS: FR-5 - The system must email a receipt
3The SRS is the basis for design and testing: designers and testers use it to check the solution against the requirements		CTest case 4 checks requirement FR-3 from the SRS
4The SRS is a reference during development: developers return to it to confirm what the software must do		DThe SRS should be used throughout the project as the basis for design and testing and as a reference during development.
5The SRS is a verbal chat that is never written down, so each person remembers requirements their own way.		EA formal document that records what the software must do so developers and clients share the same understanding
6Once the SRS is written, it is filed away and not used again during design, testing or development.		FThe client and developer agree on what will be built, so the SRS acts as an agreement between them

Definitions

Software requirements specification (SRS)

Fill in the Blanks

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

SRS: Software Requirements _____________

SRS = formal _________ between client and developer

The SRS is the _____ for design and testing

Developers _________ the SRS while coding

The SRS records the client's ____________

Spot the Error

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

Question 1

A SRS: Canteen Ordering App

B Client: Mr Ali, canteen mgr

C Signed by: developer only

D Role: agreed record of needs

Question 2

A SRS: Gym Booking App

B Req 1: Members book classes

C Req 2: Staff view bookings

D Test: ignore Req 1 and Req 2

Question 3

A IF unsure what to build

B OPEN the SRS

C READ the requirement

D GUESS what client wants

E END IF

Question 4

A SRS: an informal verbal chat

B Records: what software must do

C Shared by: client, developer

Question 5

A Client: Ms Ruiz, bakery owner

B SRS lists: how to code it

C Both agree before design

Answer Key

Purpose of a software requirements specification (SRS)

Section A: Quick Questions

A — To record what the software must do so client and developer share the same understanding

B — It acts as an agreement between the client and the developer

B — It is the basis for design: designers work from the listed requirements

A — Tests are based on the requirements to check the software does what was specified

A — Check the SRS as a reference during development

Section B: Match the Pairs

Software requirements specification (SRS) → A formal document that records what the software must do so developers and clients share the same understanding

Client signs off the SRS → The client and developer agree on what will be built, so the SRS acts as an agreement between them

The SRS is the basis for design and testing: designers and testers use it to check the solution against the requirements → Test case 4 checks requirement FR-3 from the SRS

The SRS is a reference during development: developers return to it to confirm what the software must do → Developer checks SRS: FR-5 - The system must email a receipt

The SRS is a verbal chat that is never written down, so each person remembers requirements their own way. → An SRS is a formal written document. If it is not recorded, the client and developer have no shared, agreed understanding.

Once the SRS is written, it is filed away and not used again during design, testing or development. → The SRS should be used throughout the project as the basis for design and testing and as a reference during development.

Section C: Definitions

Software requirements specification (SRS) — A formal document recording what software must do, so client and developer agree, and used as the basis for design, testing and reference during development.

Section D: Fill in the Blanks

SRS: Software Requirements Specification

SRS = formal agreement between
client and developer

The SRS is the basis for design and testing

Developers reference the SRS while coding

The SRS records the client's requirements

Section E: Spot the Error

C — An SRS is an agreement between client and developer, so both should approve and sign it. The line should be 'Signed by: client, developer'.

D — The SRS is the basis for testing. Tests should check that each requirement is met, so the line should be 'Test: check each req is met'.

D — The SRS is a reference during development. A developer who is unsure should read the requirement and build to match it, not guess.

A — An SRS is a formal document, not an informal chat. The line should say it is a formal written record.

B — An SRS records what the software must do, not how to program it. The line should be 'SRS lists: what to build'.