SRS Case Study
Purpose of a Case Study Topic
This topic asks you to apply SRS concepts to a concrete example system (e.g., Library Management System, ATM, Online Bookstore, Hospital Management System) — demonstrating you can produce a mini-SRS, not just define terms.
How to Answer an SRS Case Study Question
Step 1: Introduction
- Purpose: why the system is being built
- Scope: what the system will and will not cover
Step 2: Overall Description
- Product perspective (standalone/part of larger system)
- User classes (e.g., Admin, Member, Librarian for a Library System)
- Assumptions and constraints
Step 3: Functional Requirements (write 5–8 "shall" statements)
Example for a Library Management System:
- FR1: The system shall allow members to search for books by title, author, or ISBN
- FR2: The system shall allow librarians to issue and return books
- FR3: The system shall automatically calculate fines for overdue books
- FR4: The system shall send email reminders 2 days before the due date
- FR5: The system shall allow admins to add/remove book records
Step 4: Non-functional Requirements (write 3–5)
- NFR1: The system shall respond to search queries within 2 seconds
- NFR2: The system shall support up to 500 concurrent users
- NFR3: The system shall be available 99% of the time during library hours
- NFR4: The system shall encrypt member personal data
Step 5: External Interface Requirements
- User Interface: web-based dashboard
- Hardware Interface: barcode scanner for book IDs
- Software Interface: integration with email service for notifications
Exam Strategy
When given a case study prompt, structure your answer exactly like a mini real SRS: Introduction → Functional Requirements → Non-Functional Requirements → Interfaces. Use "shall" statements consistently.
Exam tip: Practice writing a mini-SRS (5+ FRs, 3+ NFRs) for common systems: Library System, ATM, E-commerce, Hospital Management, Hotel Booking — these are the most frequently asked case-study scenarios.