MODELIO ORGANIZAING YOUR DIAGRMS HOW TO

The reason for this has to do with how to organize the elements. ” (use as many levels as make sense) before the element name. I took the idea a little further by using prefixes in multiple levels, e.g.

The prefix makes it explicit which of the application processes we are talking about. For instance, many applications might have a “Change Address” application process. I chose not to fill in the type – it can easily be added later by means of a script (even without spelling errors), if the customer prefers so.īut I fully appreciate Gerben Wierda’s idea of having grouping information in square brackets as a kind of name spacing prefix. He may very well be right, but on the other hand it takes a lot of typing and makes the diagrams more crowded. Gerben Wierda argues that the element type – although redundant – makes the models more readable for those who do not model ArchiMate every day. “ Change Address (Application Process)” or “ Claim Handling (Business Service)”.

in the third line put the element type in brackets.Į.g.

in the second line put the element name.

device name in the technology layer, application name in the application layer or business unit in the business layer

in the first line put some grouping information in square brackets, e.g.

In my “bible” (Gerben Wierda: “Mastering ArchiMate”), I found some very useful guidance on how to label elements. Other tools might support my ideas better.

MODELIO ORGANIZAING YOUR DIAGRMS MANUAL

However, I did a little scripting to save myself for some cumbersome manual work. It has some minor flaws regarding ArchiMate, but it is a cheap and richly featured tool, which supports modeling in ArchiMate (sufficiently enough). The customer uses Sparx Enterprise Architect, v.

How do you organize your views (diagrams) – especially integration details?.

How do you organize your elements to ensure reuse? The whole point of traceability in the model is gone if you create the same element multiple times.

How do you name your elements to avoid creating multiple elements with identical names (but with different semantics)?.

If you have better ideas, please comment.Īmong other things, I saw the following challenges when a model grows: With this article I want to share my thoughts and experiences regarding large models. So, I wanted to think big and start small.

MODELIO ORGANIZAING YOUR DIAGRMS FULL

I wanted to take this opportunity to demonstrate to the customer how to develop a model that could be further developed in many directions and eventually become a full enterprise architecture model. As the customer had no preferred way to do this – and as this customer lacks overview over the enterprise architecture in general – I suggested using ArchiMate. A customer recently asked me to produce high-level documentation of a pretty large application complex.

Modelio organizaing your diagrms