An architecturally significant scenario either captures an application's essential behavior or imposes technical requirements that shape its architecture. Scenarios describe how architectural elements collaborate to implement an operation or user story. section 3.2.5
Select scenarios that reveal the application's core behavior or important technical forces:
- For a food-ordering application, ordering, preparation, and delivery express the essential flow. section 3.2.5
- For other systems, prioritize scenarios involving large data volumes or stringent performance requirements. section 3.2.5
- Choose collaborating elements according to the view: classes or subdomains, components, or infrastructure elements. Scenarios can span views. section 3.2.5
Figure 3.12 A sequence diagram for the createOrder() operation that shows how the API Gateway, Order Service, Consumer Service, and Kitchen Service collaborate to implement the operation
A sequence diagram traces how the API Gateway, Order Service, Consumer Service, and Kitchen Service collaborate on createOrder(). section 3.2.5
