schema_version: 1 model: id: cinema-tickets name: Cinema Tickets description: > An arc42 example: online and mobile seat booking for a small cinema chain. This overview is section 3 (business context) with cards for sections 1, 2, 10, 11 and 12. 0300-context holds the technical context (3), 0500-building-blocks the building block view (5), 0600-runtime the runtime view (6), 0700-deployment the deployment view (7), decisions/ the architecture decisions (9). Crosscutting concepts (8) are a card on the level-1 diagram. diagram_type: architecture meta: title: Cinema Tickets - business context output: main.html components: - ref: customer pos: [40, 60] size: [130, 60] - ref: usher pos: [40, 260] size: [130, 60] - ref: tickets pos: [280, 160] size: [150, 60] - ref: psp pos: [540, 60] size: [150, 60] - ref: mail pos: [540, 160] size: [150, 60] - ref: pos pos: [540, 260] size: [150, 60] connections: - { from: customer, to: tickets, label: books seats, variant: emphasis } - { from: usher, to: tickets, label: checks in } - { from: tickets, to: psp, label: payments, variant: security } - { from: tickets, to: mail, label: tickets } - { from: tickets, to: pos, label: seat sales } cards: - dot: cyan title: 1 Quality goals items: - "No seat is ever sold twice" - "Checkout under 2 s at Friday peak" - "Door check-in works offline" - dot: slate title: 2 Constraints items: - "Existing box-office POS stays" - "Card data only at the provider" - "Team of four; hosted in the EU" - dot: emerald title: 10 Quality scenarios items: - "500 holds on one show in 1 min: no double sale" - "Wi-Fi down at the door: scans go on, sync later" - "Payment fails: seats free again within 8 min" - dot: rose title: 11 Risks items: - "POS vendor API is slow and undocumented" - "Forwarded QR e-mails: first scan wins" - dot: violet title: 12 Glossary items: - "Show: one screening of a film in a hall" - "Hold: a seat locked for one customer" - "Check-in: first valid scan of a ticket" - "POS: point-of-sale till at the box office"