How you work today Work in your project team on ONE shared copy of the SRS template (Google Docs, or one laptop with Word). Every member writes at least 2 functional requirements and puts their initials in the Author column. Marks are given to each student. |
1. Objectives
By the end of this practical you will be able to:
- Explain what a Software Requirements Specification (SRS) is and what goes in its first three sections.
- Write a clear purpose and scope (in scope and out of scope) for your project.
- Identify stakeholders and user classes, with constraints and assumptions.
- Turn user stories into functional requirements that are clear, testable and traceable.
2. Word bank
Word | Simple meaning | Real-world example |
|---|---|---|
SRS | Software Requirements Specification: a document that says WHAT the system must do | the 10-page SRS a software house sends a client for approval |
scope | the boundary of the project: what is included and what is not | pickup orders: in scope; delivery to hostels: out of scope |
stakeholder | anyone who affects or is affected by the system | students, canteen owner, payment provider |
user class | a group of users who use the system in a similar way | kitchen staff use a tablet; students use phones |
functional requirement | something the system must DO (a service or behaviour) | The system shall display today's menu with prices. |
non-functional requirement | HOW WELL the system must do it (quality or constraint) | The menu shall load within 2 seconds. |
constraint | a limit the team must work within | must run on Android 8 or later |
assumption | something believed true but not yet checked | the owner updates the menu every morning |
traceable | you can follow a requirement back to where it came from | FR-04 comes from user story US-02 |
3. Background
In Practical 2 you wrote user stories on Trello. Stories are short reminders for conversations. Many clients, especially when there is a contract or a government tender, also want a written Software Requirements Specification (SRS): one document that says what the system must do, which both sides can read and approve. Today and in Practical 08 your team writes an SRS-lite for your semester project.
SRS-lite section | Contents | Practical |
|---|---|---|
1 Introduction | Purpose, scope (in and out), definitions | 07 |
2 Overall description | Stakeholders, user classes, constraints, assumptions | 07 |
3 Functional requirements | FR-01, FR-02 ... with priority and source | 07 |
4 Non-functional requirements | NFR-01 ... with a measure and a test | 08 |
5 Traceability matrix | User story → functional requirements | 08 |
6 Review log | Problems found by another team | 08 |
Functional or non-functional? A functional requirement (FR) says what the system must do. A non-functional requirement (NFR) says how well it must do it (speed, security, ease of use) or a constraint it must respect.
Rules for writing a good functional requirement:
1. Start with "The system shall ..." and give it an ID (FR-01).
2. One requirement per statement: no "and ... and ..." lists of features.
3. Make it testable: a tester can say yes or no. Avoid vague words: fast, easy, user-friendly, etc.
4. Say what, not how: no design choices such as "use MySQL" or "use React".
5. Give a priority (Must / Should / Could) and a source (the user story or stakeholder it came from).
Real-world example: from a user story to functional requirements User story US-02: As a student, I want to pre-order my lunch so that I do not wait in the queue. FR-03 The system shall allow a logged-in user to add menu items to a cart and change their quantities. FR-04 The system shall allow the user to place a pickup order from a cart that is not empty. FR-05 The system shall display an order number and an estimated pickup time after an order is placed. One story often becomes two or three requirements. |
Word help specification = an exact written description testable = a tester can check it and say yes or no |
4. Before you start
1. Download SE-401_SRS_Template.docx from the LMS (or the Labs folder) and open it in Word, or upload it to Google Docs and share it with your team and your teacher.
2. Open your team's Trello board from Practical 2 so you can see your user stories.
3. Give each user story an ID (US-01, US-02 ...) on its card if it does not have one.
5. Time plan (50 minutes)
Time | What you do |
|---|---|
0:00-0:05 | Teacher: what an SRS is; one user story turned into FRs on the projector |
0:05-0:15 | Parts A, B and C (on paper) |
0:15-0:22 | Task 1: purpose, scope and definitions |
0:22-0:30 | Task 2: stakeholders, user classes, constraints, assumptions |
0:30-0:45 | Task 3: 10 functional requirements |
0:45-0:50 | Teacher checks; start Part E (finish at home) |
Part A: Warm-up: functional or non-functional?
A bus company in Burewala wants a seat-booking app for its Lahore and Multan routes. Write F (functional) or NF (non-functional) for each requirement.
(a) The system shall let a passenger choose a seat from a seat map.
(b) The seat map shall load within 3 seconds on a 4G phone.
(c) The system shall send an SMS with the ticket number after payment.
(d) Passengers' CNIC numbers shall be stored in encrypted form.
(e) The system shall let the booking clerk cancel a ticket and release the seat.
(f) The app shall work on Android 8 and later.
Part B: Predict: what happens if ...?
Predict the result of each SRS decision for the bus-booking project.
(a) The SRS lists what is in scope but has no out-of-scope list. Three months later the company asks for parcel booking, "because it was obviously included". What is likely to happen?
(b) The SRS says only: "The system shall notify the passenger." The developer sends an e-mail; the company expected an SMS. Who is right?
Part C: Find the flaw: bad functional requirements
Each requirement has ONE main problem. Name it and rewrite the requirement correctly.
(1) "The system shall be user-friendly."
(2) "The system shall use MySQL to store bookings."
(3) "The system shall let passengers search buses, book seats, pay online and print tickets."
(4) "The system shall handle payments."
Part D: Graded tasks (10 marks)
Task | Level | What you build | Marks |
|---|---|---|---|
T1 | Easy | Section 1: purpose, scope and definitions | 3 |
T2 | Medium | Section 2: stakeholders, user classes, constraints, assumptions | 3 |
T3 | Challenge | Section 3: ten functional requirements | 4 |
Total | 10 |
T1 Section 1: purpose, scope and definitions (3 marks · Easy)
1. In 1.1 Purpose, write 2-3 sentences: what the system is, who it is for, and who will read the SRS.
2. In 1.2 Scope, list at least 4 in-scope features and at least 3 out-of-scope items.
3. In 1.3 Definitions, explain at least 4 terms a reader might not know.
Sample: Model scope (cafeteria app) In scope: view today's menu with prices; place pickup orders; pay at counter or by wallet; kitchen queue and 'ready' message; owner manages menu; daily sales report. Out of scope: delivery to hostels; table reservations; loyalty points; stock purchasing; more than one cafeteria. |
T2 Section 2: stakeholders, user classes, constraints, assumptions (3 marks · Medium)
1. In 2.1, list at least 5 stakeholders with role, main interest and how you will involve them. Include at least one that is not a user (e.g. a payment provider or an authority).
2. In 2.2, describe at least 3 user classes (how often they use it, device, skills, special needs).
3. In 2.3 and 2.4, write at least 2 constraints and 2 assumptions.
Sample: Model rows (cafeteria app) Stakeholder: Kitchen staff · User · Clear list of orders in the right order · Observation in the kitchen User class: Kitchen staff · tablet in the kitchen; limited English, so Urdu labels and large buttons Constraint: payments only through the provider's official API. Assumption: Wi-Fi or mobile data works in the cafeteria. |
T3 Section 3: ten functional requirements (4 marks · Challenge)
1. Take your Practical 2 user stories. Turn them into at least 10 functional requirements in the table (FR-01 ... FR-10).
2. Each one: "The system shall ...", one requirement per row, testable, no design choices.
3. Fill Priority (Must / Should / Could) and Source (the user story ID, e.g. US-02).
4. Every member writes at least 2 requirements and puts their initials in the Author column.
5. Check every row against the five rules in the background before you call the teacher.
Sample: Model rows (cafeteria app) FR-02 The system shall show sold-out items in grey and shall not allow them to be added to the cart. · Must · US-04 FR-07 The system shall allow kitchen staff to mark an order as Ready, and shall then notify the user who placed it. · Must · US-06 FR-09 The system shall allow the user to cancel an order until kitchen staff start preparing it. · Should · US-07 |
Part E: Post-lab questions
1. What is the difference between a functional and a non-functional requirement? Give one example of each from your project.
2. Why is an out-of-scope list as important as an in-scope list?
3. Your client says, "Just write that the app must be fast and easy." How do you turn this into requirements you can test?
Marking rubric
Task | Marks | Full marks when ... |
|---|---|---|
T1 Section 1: purpose, scope and definitions | 3 | 1 mark: clear purpose (system, users, readers) 1 mark: 4+ in-scope and 3+ out-of-scope items 1 mark: 4+ useful definitions |
T2 Section 2: stakeholders, user classes, constraints, assumptions | 3 | 1 mark: 5+ stakeholders, at least one non-user, with interests 1 mark: 3 user classes with real characteristics 1 mark: 2+ constraints and 2+ assumptions (not mixed up) |
T3 Section 3: ten functional requirements | 4 | 1 mark: 10+ FRs in 'The system shall' form with IDs 1 mark: one requirement per row, testable, no design choices 1 mark: priority and source on every row 1 mark: own 2+ FRs with initials, correctly written (individual) |
Parts A, B, C and E are not marked separately; they prepare you for the tasks and the viva.
Submission
- The teacher checks sections 1-3 of your SRS before you leave.
- Save the file as SRS_<TeamName>_v1.docx and upload it to the LMS by the end of the day (one per team).
- Copy your own 2+ functional requirements and your answer to Part E question 1 into the Lab Book (Practical 07 page).
- Bring the SRS to Practical 08: another team will review it.