Administrator: “In step 5, the system saves the reservation to the database. What happens if the seats are not available any more by the time you click the reservation button?”

Employee: “I don't know. I have been working here for three years, but that never happened to me.”

Manager: “I am sure that we do not sell the same seat twice for the same show. There have never been any complaints.”

Us: “Still, it would be interesting to know how the ticket system reacts.”

Administrator: “I will check the documentation when I am back in the office.”

Us: “Back to your 'challenging' customers. What would be different if such a customer wants to make a reservation?”

Employee: “In step 1, the customer would request certain seats.”

Us: “If these seats are available, the story does not change, does it?”

Employee: “You are right. But if they are not available, I give them other options.”

Us: “How do you do that?”

Employee: “The easiest way is to turn my display to the customer so that he can see the available seats in the screen plan.”

Administrator: “But the screen plan is tiny! And the display stand doesn't rotate! Do you really work like that?”

Employee: “Sadly, yes.”

Us: “Let's make an annotation to our Domain Story.



We write: "3) If customer wants to choose herself, cashier turns display to customer so she can see the screen plan. Problems: size of screen plan, displays do not rotate.”

Us: “Is that okay?”



Employee, manager and administrator all nod their heads.

Us: “Is there anything else we need to know about making reservations at the ticket counter?”

Employee: “I think we covered everything.”



Manager and administrator nod their heads in agreement. This is our Domain Story: