Illustrating abstract architectural concepts using real world processes is actually a very powerful teaching tool; for example, illustrating the concept of a correlation identifier by reference to Starbucks' practice of writing your name on the cup when you order.
It's a simple and effective solution, but I did have a little trouble with it when I was working regularly in the Philippines a few years ago. Filipinos are mostly accustomed to American accents; when I gave my name as Dan almost anything would end up on the cup. So I experimented for a bit until I found a name that the staff would always get right despite my Australian accent; at Starbucks Philippines I am therefore known as "Freddie".
It also reminded me of the Order Cappuccino Use Case that I used to teach how to write Use Cases; that was in South Africa where the "cappuccino with foam or cream" heresy originates.
Order Cappuccino Use Case
- The Customer asks for a cappuccino; the Waiter prompts for Foam or Cream
- The Customer requests foam; the Waiter submits the order
- The Barista makes the cappuccino
- The Waiter collects the order from the Barista and delivers it to the customer
- The Customer drinks the cappuccino
- The Customer requests the bill; the Waiter delivers the bill
- The Customer pays; the Waiter collects the payment
- The Waiter returns with the change
- The Customer collects the change and the Use Case ends
Alternate Flow (branch at Basic Flow Step 2)
- A South African Customer requests Cream; the Use Case ends because that’s not a Cappuccino!