Software Requirements Specification: [RoomFinder]
System | [RoomFinder: room and study-space booking system] |
Organisation | [Westbrook University, Estates and IT Services] |
Document owner | [Name, Lead Business Analyst] |
Version | [1.0 for approval] |
Date | [December 2026] |
Status | [Draft / In review / Approved] |
Revision history
Version | Date | Author | Changes |
|---|---|---|---|
[0.1] | [Oct 2026] | [Name] | [Initial draft] |
[0.9] | [Nov 2026] | [Name] | [Workshop feedback; non-functional requirements added] |
[1.0] | [Dec 2026] | [Name] | [For approval] |
1. Introduction
1.1 Purpose
[This document specifies the functional and non-functional requirements for RoomFinder release 1. It is intended for the project sponsor, development and test teams, and the estates and timetabling teams who will operate the system.]
1.2 Scope
[RoomFinder lets students and staff find and book study rooms, meeting rooms and bookable teaching spaces across three campuses, check in on arrival, and release rooms automatically when not used. It replaces email and spreadsheet booking. Timetabled teaching remains in the timetabling system; RoomFinder reads it to show availability. Out of scope for release 1: catering orders, equipment loans and external customer bookings.]
1.3 Definitions and acronyms
Term | Meaning |
|---|---|
[Bookable space] | [A room or study pod configured in RoomFinder] |
[Check-in] | [Confirming arrival by scanning the room QR code within the grace period] |
[Grace period] | [Time after booking start within which check-in is required (default 15 minutes)] |
[SSO] | [Single sign-on through the university identity provider] |
[Shall / should / may] | [Mandatory / desirable / optional requirement] |
1.4 References
[RoomFinder Business Case v2.1]
[University Information Security Policy]
[Accessibility standard: WCAG 2.2 level AA]
[Timetabling system integration guide v4]
1.5 Document overview
[Section 2 describes the product context, users and constraints. Section 3 lists the specific requirements. Section 4 covers data requirements, and section 5 approval.]
2. Overall description
2.1 Product perspective
[RoomFinder is a new web application with a mobile-responsive interface. It integrates with the identity provider (authentication), the timetabling system (teaching bookings, read-only), the student and HR systems (user attributes) and the email service (notifications).]
2.2 Product functions (summary)
[Search and view availability of bookable spaces]
[Book, amend and cancel bookings, including recurring bookings for staff]
[Check in by QR code; release no-show bookings automatically]
[Manage spaces, opening hours and booking rules (administrators)]
[Report on utilisation and no-shows]
2.3 User classes
User class | Description | Approx. number | Key needs |
|---|---|---|---|
[Students] | [Undergraduate and postgraduate students] | [18,000] | [Find and book study rooms quickly on mobile] |
[Staff] | [Academic and professional staff] | [3,200] | [Book meeting rooms, recurring bookings] |
[Space administrators] | [Estates and faculty administrators] | [40] | [Configure spaces and rules, resolve conflicts] |
[Report viewers] | [Estates planning, senior managers] | [15] | [Utilisation reports] |
2.4 Operating environment
[Hosted on the university’s cloud tenancy. Supported browsers: latest two versions of Chrome, Edge, Safari and Firefox, on desktop and mobile. Room-door QR codes are printed labels; no hardware is installed in rooms in release 1.]
2.5 Design and implementation constraints
[Must authenticate through the university identity provider using SAML 2.0 or OpenID Connect.]
[Personal data must be stored in [region] data centres.]
[Must meet the University Information Security Policy and WCAG 2.2 AA.]
2.6 Assumptions and dependencies
[The timetabling system exposes an availability API updated at least every 15 minutes.]
[Estates will provide an accurate list of rooms, capacities and features before testing.]
3. Specific requirements
3.1 External interface requirements
ID | Interface | Requirement |
|---|---|---|
[IF-01] | [User interface] | [The system shall provide a responsive web interface usable at screen widths from 360 px.] |
[IF-02] | [Identity provider] | [The system shall authenticate users via SSO and receive role attributes (student, staff, administrator).] |
[IF-03] | [Timetabling system] | [The system shall import teaching bookings every 15 minutes and treat them as unavailable time.] |
[IF-04] | [Email service] | [The system shall send booking confirmations, reminders and cancellations by email.] |
[IF-05] | [Calendar] | [The system should attach an iCalendar file to booking confirmations.] |
3.2 Functional requirements
#### 3.2.1 Search and availability
ID | Requirement | Priority | Acceptance criteria |
|---|---|---|---|
[FR-01] | [The system shall let users search spaces by campus, date, time, capacity and features.] | [Must] | [Search returns only spaces matching all filters and free for the whole requested period.] |
[FR-02] | [The system shall show a day view of availability for a selected space in 15-minute slots.] | [Must] | [Booked, timetabled and closed periods are visibly distinct.] |
[FR-03] | [The system should show spaces on a campus map.] | [Should] | [Each result links to a map pin.] |
#### 3.2.2 Booking
ID | Requirement | Priority | Acceptance criteria |
|---|---|---|---|
[FR-10] | [The system shall let an authenticated user book an available space in one step from search results.] | [Must] | [Booking confirmed on screen and by email within 1 minute.] |
[FR-11] | [The system shall prevent double booking of a space.] | [Must] | [Concurrent requests for the same slot result in exactly one booking.] |
[FR-12] | [The system shall enforce booking rules per space: maximum duration, advance window and user classes allowed.] | [Must] | [Students cannot book study rooms for more than 3 hours per day or more than 7 days ahead (default rules).] |
[FR-13] | [The system shall let staff create weekly recurring bookings for up to 12 weeks.] | [Must] | [Conflicting occurrences are listed before confirmation.] |
[FR-14] | [The system shall let users amend or cancel their bookings up to the start time.] | [Must] | [Cancelled time becomes available immediately.] |
#### 3.2.3 Check-in and release
ID | Requirement | Priority | Acceptance criteria |
|---|---|---|---|
[FR-20] | [The system shall let the booker check in by scanning the room QR code while signed in.] | [Must] | [Check-in only succeeds between 10 minutes before start and the end of the grace period.] |
[FR-21] | [The system shall release a booking that is not checked in by the end of the grace period.] | [Must] | [Released time shows as available within 1 minute; the booker is notified.] |
[FR-22] | [The system should suspend booking rights for 7 days after 3 no-shows in 30 days.] | [Should] | [Suspension and its end date are shown to the user.] |
#### 3.2.4 Administration and reporting
ID | Requirement | Priority | Acceptance criteria |
|---|---|---|---|
[FR-30] | [The system shall let administrators create, edit and deactivate spaces, with capacity, features, photos and opening hours.] | [Must] | [Changes take effect for new searches immediately.] |
[FR-31] | [The system shall let administrators override or cancel any booking with a reason, notifying the booker.] | [Must] | [Audit log records who, when and why.] |
[FR-32] | [The system shall provide utilisation reports by space, building and period, exportable to CSV.] | [Must] | [Report shows booked hours, checked-in hours and no-show rate.] |
3.3 Non-functional requirements
ID | Category | Requirement |
|---|---|---|
[NFR-01] | [Performance] | [Search results shall return within 2 seconds for 95% of requests at 1,000 concurrent users.] |
[NFR-02] | [Capacity] | [The system shall support 25,000 registered users and 600 bookable spaces.] |
[NFR-03] | [Availability] | [Monthly availability shall be at least 99.5% between 07:00 and 23:00, excluding planned maintenance announced 3 days ahead.] |
[NFR-04] | [Security] | [All traffic shall use TLS 1.2 or higher; data at rest shall be encrypted.] |
[NFR-05] | [Security] | [Administrative functions shall require MFA.] |
[NFR-06] | [Privacy] | [Booking records linked to individuals shall be deleted or anonymised 13 months after the booking date.] |
[NFR-07] | [Accessibility] | [The user interface shall conform to WCAG 2.2 level AA.] |
[NFR-08] | [Usability] | [80% of first-time student users shall complete a booking unaided in under 90 seconds in usability testing.] |
[NFR-09] | [Auditability] | [All booking changes and administrator actions shall be logged with user, timestamp and before/after values, kept for 13 months.] |
[NFR-10] | [Maintainability] | [Booking rules shall be configurable by administrators without code changes.] |
4. Data requirements
Entity | Key attributes | Source | Retention |
|---|---|---|---|
[User] | [ID, name, email, user class, department] | [Identity provider, student and HR systems] | [While account active] |
[Space] | [ID, name, building, campus, capacity, features, rules, opening hours] | [Administrators] | [Indefinite; deactivated not deleted] |
[Booking] | [ID, space, user, start, end, status, check-in time, recurrence] | [RoomFinder] | [13 months, then anonymised] |
[Audit event] | [Event type, user, timestamp, details] | [RoomFinder] | [13 months] |
5. Open issues
# | Issue | Owner | Due |
|---|---|---|---|
[1] | [Confirm whether postgraduate research students have different booking limits] | [Graduate School] | [15 Jan 2027] |
[2] | [Agree no-show suspension policy with the Students’ Union] | [Estates] | [31 Jan 2027] |
6. Approval
Role | Name | Signature | Date |
|---|---|---|---|
Project sponsor | [Name, Director of Estates] | [Date] | |
Business owner | [Name, Head of Space Management] | [Date] | |
IT architect | [Name] | [Date] | |
Test lead | [Name] | [Date] |