Preparing your design workspace

Loading the problem and your saved attempt…

Design Recurring Meeting-Room Booking

Model rooms, recurrence rules, generated occurrences, conflicts, and safe edits to one occurrence or an entire series.

For this exercise, assume employees book rooms for one-time or recurring meetings. A request contains a room, organizer, local start time, duration, time zone, and either no recurrence or a weekly recurrence with selected weekdays and a finite end date no more than one year away.

Creating a recurring meeting succeeds only when every generated occurrence is available; otherwise all conflicts are returned and nothing is created. Each live occurrence occupies a half-open interval for one room, and overlapping concurrent requests cannot both succeed.

The organizer may cancel or move one occurrence, or replace all future occurrences from a selected date, without rewriting past occurrences. Exact command retries return the prior result, while a stale series update returns a conflict. Design the objects, responsibilities, interfaces, and interactions.

Calendar invitations, attendee availability, catering, room sensors, and distributed notification delivery are outside scope.