Can you decompose a process, browse to it and return back to the parent process in Archimate? The same way as in BPMN? Thanks
Hi,
Quote from: cibret24 on December 07, 2020, 09:18:02 AM
Can you decompose a process [...]
Yes, in ArchiMate standard, any type of element can be decomposed into elements of the same type, so you can decompose a process into other processes.
Quote from: cibret24 on December 07, 2020, 09:18:02 AM
[...] browse to it and return back to the parent process in Archimate? The same way as in BPMN?
This is not related to the standard but to tools (ArchiMate is tool agnostic and you can model things in ArchiMate using pen an paper). In Archi, you can drag and drop a view into another view, making it possible to navigate. So if you have a detailed process in "View A", and an overview in "View B", you can drag and drop "View A" into "View B" and put it inside the process being detailed (usually users then make this view reference small so that only the icon is visible.
Note that there is no underlying relation between the process and the view detailing it. In ArchiMate such link at model level doesn't make sens as, depending on the context, the "target" view will be different.
Regards,
JB
Thanks a lot for your answer. It was super helpful. Can i further use a relation such as trigerring relation between the View that was dragged and dropped and another process?
Best regards,
Ana
Hi,
Quote from: cibret24 on December 08, 2020, 09:44:27 AM
Thanks a lot for your answer. It was super helpful.
You're welcome
Quote from: cibret24 on December 08, 2020, 09:44:27 AM
Can i further use a relation such as trigerring relation between the View that was dragged and dropped and another process?
No because in ArchiMate a relation must target a concept (a view is not). Remember that in ArchiMate there's a clear distinction between the model content (elements and relationships) and views based on the model. Strictly speaking, the views are not event seen as part of the model in the official specifications (see https://pubs.opengroup.org/architecture/archimate3-doc/chap03.html#_Toc10045291).
The usual workaround is to simply put the view reference inside a process element (the one which is further detailed into the target view). It is this process which is the source or target of triggering relationships.
Regards,
JB
Thanks a lot for your quick reply. It makes now sense.
Best regards,
Ana
Hi,
again, quite inspired today (;D),
Quote from: Jean-Baptiste Sarrodie on December 08, 2020, 10:23:01 AM
The usual workaround is to simply put the view reference inside a process element (the one which is further detailed into the target view). It is this process which is the source or target of triggering relationships.
Not beautiful writing, more an illustration (see attachment) of what could be managed through scripting: https://gist.github.com/projetnumero9/3301cfb99d8747c79a8bd6e0edcec32e (https://gist.github.com/projetnumero9/3301cfb99d8747c79a8bd6e0edcec32e)
Best regards,