7
Back to Problem Dungeon

Hotel Booking System

medium

Step 1: Requirements

Requirements

Questions to ask

  • How many room types? (single, double, suite, etc.)
  • Can a booking span multiple rooms?
  • Do we need dynamic pricing (seasonal, demand-based)?
  • What is the cancellation policy?
  • Do we need to handle overbooking?
  • Should we notify housekeeping, billing, etc. on booking events?

Functional requirements

  1. Search available rooms by date range and type
  2. Create, confirm, cancel, and check-in/check-out bookings
  3. Calculate pricing based on room type, season, and demand
  4. Notify relevant systems (billing, housekeeping) on booking state changes

Non-functional requirements

  • No double-booking (a room can only be booked once per date)
  • Booking lifecycle must be atomic (no partial states)
  • Pricing must be consistent during a booking flow

1 / 7 — Requirements