{"id":2739,"date":"2019-04-29T10:15:28","date_gmt":"2019-04-29T08:15:28","guid":{"rendered":"http:\/\/www.hosiaisluoma.fi\/blog\/?p=2739"},"modified":"2021-08-04T20:30:56","modified_gmt":"2021-08-04T18:30:56","slug":"architectural-thinking-with-archimate","status":"publish","type":"post","link":"https:\/\/www.hosiaisluoma.fi\/blog\/architectural-thinking-with-archimate\/","title":{"rendered":"Architectural Thinking with ArchiMate"},"content":{"rendered":"

Architectural Thinking Association (AT)<\/strong> \u00ae is an interesting initiative in order to make the architecture easier for everybody (link<\/a>). AT core model is relatively simple, it consists of few elements only as follows: Capability<\/em>, Value Stream (Process)<\/em>, Business Object<\/em>, Application<\/em> and Technology Component<\/em>. The AT core meta-model is illustrated in the diagram below (figure 1).<\/p>\n

\"\"<\/a>
Figure 1<\/strong>: Architectural Thinking core meta-model.<\/figcaption><\/figure>\n

These AT core elements can be visualized with any tool, such as drawing tools like MS Powerpoint or MS Visio.<\/p>\n

Formal architecture modelling can be used for complementary practice for AT approach. Formal modelling with an appropriate modelling tool (such as BIZZdesign, Orbus iServer, Mavim, Sparx EA or open-source Archi<\/a>) and a standard notation (such as ArchiMate, BPMN, UML) can be valuable for many architectural use cases. Utilizing a standard notation with a professional modelling tool can be beneficial in many organizations for systematic architecture management, where architecture descriptions are designed more detailed level, and shared & published for every stakeholders. In such organizations, a comprehensive architecture repository can be used for to enable coherent and cohesive overall architecture landscape, for every development target (e.g. a new service or product, a new digital strategy, whole business domain etc.).<\/p>\n

ArchiMate -standard (link<\/a>) can be used for creating diagrams according to AT approach. Here is couple of examples of the AT core meta-model, modelled with ArchiMate.<\/p>\n

1) Architectural Thinking core meta-model with the ArchiMate “Process” -element<\/h3>\n

This version (figure 2) is using the ArchiMate Process -element to depict the value stream.<\/p>\n

\"\"
Figure 2<\/strong>: Architectural Thinking (core) meta-model (with Process -element).<\/figcaption><\/figure>\n

2) Architectural Thinking core meta-model with the ArchiMate “Value Stream” -element<\/h3>\n

This version (figure 3) is using the Value Stream -element, which is available in the ArchiMate 3.1 version of the standard (link<\/a><\/span>).<\/p>\n

\"\"
Figure 3<\/strong>: Architectural Thinking (core) meta-model (with Value Stream -element).<\/figcaption><\/figure>\n

This version (figure 4) is using the ArchiMate relationship types “serving” and “access” to indicate how these elements can be connected with each other. By using these few ArchiMate elements, it is possible to model architectural aspects of an organization. This simplified modelling approach of the “architectural thinking” aims to focus on simplicity rather than complexity..<\/p>\n

\"\"
Figure 4<\/strong>: Architectural Thinking core meta-model in ArchiMate.<\/figcaption><\/figure>\n

This version of AT core meta-model with ArchiMate (figure 4) is included in Lean EA Framework (LEAF), which can be found via this link<\/a>. Navigate to “Principles”, “Development Methods”, “Architectural Thinking approach”. The LEAF is supporting a “value chain based method” that is described here (link<\/a>) and also here (link<\/a>).<\/p>\n

\n

For more ArchiMate examples see:<\/p>\n