Archimate

Last semester is participated in an enterprise architecture in practice course which contained some lessons on Archimate. Archimate is an modeling language for enterprise architecture. The power of Archimate is that it can combine the different layers in an architecture (eg. Business, application and technology), so you can see which business process relies on which application and on which technical stuff the application relies. Between the layers services are defined to interface between the layer, this comes in handy in service oriented architectures we all want now a day’s ;-). Archimate is partly based on UML so some notations should look for familiar (uses, realizes arrows).


One thing is miss in Archimate is the integration with models that can be interpreted by applications, such as BPMN for process flows, and UML class diagram for application code. If that will be possible it would provide an great opportunities (application generation or reengineering models form code), but enlarges another problem: information overload. There will be an overload in information even to the dirty details (eg. Database fields), this requires a good tool which gives a clear oversight of the available data and can generate many views on that data. The trick will be to define good views for the different stakeholders.

Concluding

Pro’s

Cons

J showing relations between layers

L just handy to get some understanding, not for realizing it (integration to code)

J Joined the open group and is an standard

LNo integration with

   
  1. No comments yet.
  1. No trackbacks yet.