craftvorti.blogg.se - Archimate vs modelio

#ARCHIMATE VS MODELIO DRIVER#
#ARCHIMATE VS MODELIO FULL#

HOW To…Īfter analyzing why something is important and essential, then the necessary steps to be taken can be analyzed with the rest of ArchiMate Motivation concepts. The ArchiMate Stakeholder-concept can be used fore identifying the interest groups that have some concerns related to this specific development target.

#ARCHIMATE VS MODELIO DRIVER#

With ArchiMate concepts such as Driver and Assesment, it is possible to identify the relevant elements for analyzing WHY something really important. The left side of the metamodel covers the WHY and HOW parts. ArchiMate provides elements for each of those steps for thinking & modelling what is essential. This approach is inspired by Simon Sinek’s “start with why” -concept (see introduction here). This metamodel encourages analyzing first the WHY question, then HOW, and finally WHAT. ArchiMate Metamodel Use Cases Analysing & Planning WHY, HOW, WHAT 1. Relationships are introduced more detailed in the ArchiMate specification ( link). (“Product” is slightly problematic concept in this diagram, as it is placed on implementation view, for the sake of agile development approach.) Two roles of “Product”: 1) composition of Business/Application/Technology Services and 2) implementation construct, which consists of behavioral and structural elements.Business Process -> Business Function, Application Process -> Application Function, Technology Process -> Technology Function). “Process” element can be replaced with “Function” (e.g.Some relations are not visible on the diagram above (for the sake of simplicity), but those can be derived from the other relations – according to the ArchiMate derivation rules ( link).Motivation elements (on the left) can be realized by Strategy and/or Implementation elements (bottom left), those of which can be aggregated from core structural and behavioral elements (on the right).

#ARCHIMATE VS MODELIO FULL#

ArchiMate 3.1 Full Metamodel (with simplified relations). This meta-model (with simplified relations) below introduces also Motivation- and Strategy-elements (on the left side).

These elements can be applied to most of the modelling cases (80%), added with relation type “Flow” (between actors, processes and applications).

The relation from “Node” to “Application Component” can be either “serving” or “realization” (according to derivation rules).

ArchiMate Core Meta-model ArchiMate Metamodel (3.1) – core. Idea behind a metamodel is to introduce those elements that are relevant, with which most of the cases can be modelled. Here is introduced 1) Core Meta-model, 2) Full Meta-model. The most relevant elements and relation types are illustrated in the meta-model diagrams below.Īn ArchiMate meta-model can be applied to fit for purpose, to be aligned to what is appropriate. However, only a subset of ArchiMate elements can be used for most of the cases – according to Pareto’s law (80/20 rule). ArchiMate can be used for holistic enterprise development purposes, as ArchiMate provides concepts that cover all the most relevant aspects of overall modelling. ArchiMate contains lots of elements, what makes it very powerful notation.