PyQdeck LogoPyQdeckSubjectsSyllabusBlog
Back to the 2026 paper

Module 2: Requirements & SRS

20267m

Construct an SRS-oriented requirement analysis for a hotel management system covering major user needs, functional requirements, constraints and quality requirements.

Search GoogleAsk AI
Worked SolutionAI Assisted

SRS-Oriented Requirement Analysis: Hotel Management System

1. Introduction

  • Purpose: automate room booking, check-in/out, billing and housekeeping for a hotel.
  • Scope: reception, guests, housekeeping, restaurant billing, management reports.
  • Users: Guest, Receptionist, Housekeeping staff, Manager/Admin.

2. Major user needs

User Need
Guest Search available rooms, book/cancel online, view bill
Receptionist Quick check-in/out, room allocation, payment collection
Housekeeping See room status (clean/dirty/occupied), task list
Manager Occupancy, revenue and staff reports

3. Functional requirements

  • FR1 Room management: add/update rooms, types and tariffs; show real-time availability.
  • FR2 Reservation: book, modify, cancel a room for given dates; prevent double booking.
  • FR3 Check-in/Check-out: record guest ID, allocate room, close the stay.
  • FR4 Billing: calculate room charges, taxes, restaurant/service charges; generate invoice.
  • FR5 Payment: cash, card and online payment; issue receipt.
  • FR6 Housekeeping: update and track room status.
  • FR7 Reports: daily occupancy, revenue, guest history.
  • FR8 User management: role-based login.

4. Constraints

  • Must run on a web browser and a standard database (e.g. MySQL).
  • Must follow tax/billing laws and guest-ID record rules.
  • Payment through an approved gateway; fixed budget and delivery time.
  • Must work with existing hardware (reception PCs, printers).

5. Quality (non-functional) requirements

Quality Requirement
Performance Search/booking response within 3 seconds for up to 100 concurrent users
Security Encrypted passwords, role-based access, secure payments
Reliability/Availability 99.5% uptime; daily backups
Usability Simple screens; staff trained within one day
Scalability Support more rooms/branches later
Maintainability Modular design with documentation

6. Assumptions

Online payment gateway and internet are available; figures such as response time are assumed values.

In the exam, present these in the IEEE SRS layout: Introduction, Overall Description, Specific Requirements.

Similar questions

Software EngineeringDiscuss the characteristics of a good Software Requirement Specification and its components.20257mSoftware EngineeringThe main purpose of an SRS (Software Requirements Specification) document is to: (i) Describe coding standards (ii) Provide a user manual (iii) Serve as a contract between client and developer (iv) Define the software test cases20252mSoftware EngineeringDefine Requirement Analysis. Why is it considered one of the most critical stages in the software development life cycle?20257mSoftware EngineeringPrepare SRS for an 'Inventory Management System' for a retail medical store. Also explain the risk assessment and management in brief. Make necessary assumptions.20217m
PreviousCompare Agile development with a conventional sequential process in terms of iteration, customer participation, requirement change and software delivery.NextDevelop a decision table for an online loan-processing system using customer eligibility, income level, credit score and document verification as conditions. Derive the corresponding system actions.
Student FinanceWeb Platform

Pocketly — Personal Finance for Students

Keep your hostel and college expenses under control. Track accounts, log spending in seconds, and stay within your monthly budget.

Open Pocketly