Wednesday, November 12, 2014

Do we really need ArchiMate? UML vs BPMN vs ArchiMate

UML and BPMN are two well known modelling languages that when used in combination in software solution delivery project, they can cover a very wide spectrum ranging from cross-organizational business processes to classes that can be used to generate executable code.
The question I am facing now is the necessity of utilizing the ArchiMate modelling language.
While I realize that some elements in ArchiMate do not have direct equivalents in BPMN or UML, but do they actually create enough value to justify introduction of another modelling language?
Some googling shows that the language is used with a vast level of divergence by system architects which questions the clarity and usefulness of the language. After all, for a modelling language to be more effective than natural language, it is expected to provide a consistent and normative way of describing the idea or the physical reality.
Almost every ArchiMate diagram that I've seen, although not being wrong, has been a surprise and difficult to verify and understand.
The current guidelines in ArchiMate about defining the system in three layers are too vague to actually produce good quality design artifacts by system architects.

I have provided an example in a later post
Homepage
Homepage