CSE Roadmap

Core tier · about 3 hours · 7 parts

Part 3 of 7 · 1 min read

Steps 1 and 2

Requirements and entities, done quickly.

Step 1 gives, as in module 2, these rules: many rooms with a capacity; a booking is one room and one slot; active bookings of one room must not overlap; a booking can be cancelled; out of scope are payments and repeats.

Step 2 gives the entities and values: Room (entity), Booking (entity), TimeSlot (value), BookingStatus (enum), and the service that owns the rule.

Saying it aloud takes under ten minutes: "The key rule is no overlap. A booking holds a room, a user and a slot. The service sees all bookings, so it owns the rule."

Check yourself: 1. Which class owns the no-overlap rule? 2. Which entity is a value object? 3. What is out of scope?