Back to the map

Module 03 · Design notation · Drill

Design notation drill

Scenario prompts that check whether design notation is usable under pressure. Answer out loud, then compare.

4 prompts25 minNew

0 of 4 graded

  1. Prompt 1

    Draw (or describe precisely) the class diagram for a library: books with multiple physical copies, members who borrow copies, loans with due dates, reservations queued on a book, and fines. Give every relationship type and multiplicity and justify the ones an interviewer is likely to question.

    Say your answer out loud first. Thirty seconds is enough.
  2. Prompt 2

    Write the sequence for 'customer checks out a cart' in an e-commerce service: validating stock, reserving inventory, charging payment, creating the order and sending a confirmation. Include the failure paths, the transaction boundary, and where you would use asynchronous messages.

    Say your answer out loud first. Thirty seconds is enough.
  3. Prompt 3

    Design the state machine for a ride in a ride-hailing app from request to completion, including cancellations by rider and driver, no-shows and payment. List states, events, guards and actions, and explain how you prevent two drivers from accepting the same ride.

    Say your answer out loud first. Thirty seconds is enough.
  4. Prompt 4

    Apply the requirements-to-objects method to 'design a meeting room booking system for an office': clarify, mine nouns and verbs, classify, assign responsibilities, walk the 'book a room' flow, and then absorb the change 'recurring weekly meetings'.

    Say your answer out loud first. Thirty seconds is enough.
Design notation drill · Backplane