The Present and Future of the ArchiMate® Language – Part 2

The ArchiMate language should address only what is necessary to model architecture and leave the other areas to appropriate modeling languages, such as BPMN™ for business process models and UML® for software models. Each profession has its own optimal terminology, languages, and tools. The ArchiMate language should not challenge languages designed for disciplines beyond architecture. It is better to ensure traceability between different model types to maintain consistency. If there is a desire for a modeling language for other areas, do not just add them to the ArchiMate language but make a related new language.

The Present and Future of the ArchiMate® Language – Part 1

With the release of the ArchiMate 3.0 Specification in 2016, we now have a complete enterprise description language that has been adopted by architects worldwide in a wide range of organizations. It is now time for the ArchiMate Forum to reach out to users and better understand how the language is being used and how it should evolve. The ArchiMate modeling language supports architects in creating straightforward and understandable diagrams. Use of the ArchiMate notation helps architects understand each other’s architectures.

1 2 3 14