![]() This improved understanding of the system design across success and error use cases. This post started with a high-level architecture diagram and ended with an additional Sequence Diagram that captures multiple usage scenarios. ![]() Up-to-date documentation is important for operationally supporting production deployments, and these diagrams quickly provide a visual understanding of system component interactions. Then as application code is updated, team members can revise both the ADR narrative and the text-based diagram source. Also consider an architectural decision record (ADR) process to document and communicate architecturally significant decisions. Because diagrams-as-code use text-based files, they can be stored and versioned in the same source control system as application code. Header-based API Gateway versioning with CloudFront Diagrams as codeĪfter diagrams are created, the next question is where to save them and how to keep them updated. The rectangle with the bent upper-right corner is a note containing additional useful information.įigure 5. The text inside guillemets («like this») indicate a stereotype, which refines the meaning of a model element. The dashed lines represent reply messages. Messages are arranged in time sequence from top to bottom. The horizontal arrows between participants are messages, with the arrowhead indicating message direction. The parallel vertical lines underneath these participants are lifelines. In Figure 2, User, Web Distribution, and Origin Request are each actors or system participants. Let’s investigate the system use case where the API is called without a header indicating the requested version using a Sequence Diagram. I use this diagram type for analysis and design purposes and to validate my assumptions about data flows in distributed architectures. Sequence Diagrams model the ordered logic of usage scenarios in a consistent visual manner and capture detailed behaviors. Sequence Diagrams are part of a subset of behavior diagrams known as interaction diagrams, which emphasis control and data flow. High-level architecture diagram Sequence Diagrams It also demonstrates behavioral aspects from a Communication Diagram, which uses messages represented by arrows labeled with chronological numbers.įigure 1. It includes structural aspects from a high-level Deployment Diagram, which depicts network connections between AWS services.
0 Comments
Leave a Reply. |