Not Docker! In the C4 model, a container represents an application or a data store. In many cases, a software system is "owned by" a single software development team. This includes the software system you are modelling, and the other software systems upon which your software system depends (or vice versa). actors, roles, personas, etc).Ī software system is the highest level of abstraction and describes something that delivers value to its users, whether they are human or not. Which in turn are implemented by one or more code elements (classes, interfaces, objects, functions, etc).Īnd people may use the software systems that we build.Ī person represents one of the human users of your software system (e.g. If the relationship between the diagram elements is one-to-one, then simply leave it blank.In order to create these maps of your code, we first need a common set of abstractions to create a ubiquitous language that we can use to describe the static structure of a software system.Ī software system is made up of one or more containers (applications and data stores),Įach of which contains one or more components, It’s optional, but sometimes useful to add the standard UML notation for multiplicity: 1, 1.n, or *. You can also show inheritance on both actions and actors with the standard UML notation of a connector with an open arrowhead. In my example, you can Mark a habit as done, or Mark a habit as done AND add a comment in the same action.
For example when you Add a comment in the habit tracker app, you must Update the habit history. When one action is dependent on another action, use an include relationship.
You can show specific relationships between the actions (or classes and methods) with include and extend. Use case diagrams can show information that makes it easier to program
0 kommentar(er)
