You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-[e.g., a server-side web application, a desktop application, a mobile app]{.text-smaller}
72
+
- shows the high-level shape of the software architecture and how responsibilities are distributed across it
73
+
- also shows the major technology choices
74
+
- and how the containers communicate with one another (interfaces)
75
+
- simple, high-level technology focused diagram that is useful for software developers and support/operations staff alike
76
+
77
+
::: {.wide-quote .mt-2}
78
+
> Zooms into the software system, and shows the containers (applications, data stores, microservices, etc.) that make up that software system. Technology decisions are also a key part of this diagram.
79
+
>
80
+
> Simon Brown - [The C4 Model for Software Architecture](https://www.infoq.com/articles/C4-architecture-model/)
- shows the major structural building blocks of the application (with interfaces)
99
+
- roughly like the UML component diagram
100
+
- but the concept of a component is more relaxed
101
+
- as the implementation is not necessarily OO
102
+
- basically the actual blueprint of the software
103
+
- focus on this level in the project assigment
104
+
105
+
::: {.wide-quote .mt-2}
106
+
> Zooms into an individual container to show the components inside it. These components should map to real abstractions (e.g., a grouping of code) in your codebase.
107
+
>
108
+
> Simon Brown - [The C4 Model for Software Architecture](https://www.infoq.com/articles/C4-architecture-model/)
0 commit comments