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.
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.
The IT4IT standard provides a vendor-neutral, technology-agnostic, and industry-agnostic reference architecture for managing the business of IT, enabling insight for continuous improvement. Together, the IT4IT Value Chain and Reference Architecture deliver value to IT practitioners and executives alike.
By The Open Group
Since its inception more than two decades ago, TOGAF®, an Open Group standard, has grown to become the de facto global framework for creating Enterprise Architectures.
Thousands of companies worldwide have adopted and adapted TOGAF to transform their businesses.
By Stuart Macgregor, CEO, Real IRM and The Open Group South Africa This is Part 2 of a two part series. Part 1 can be
By Iver Band, Enterprise Architect at Cambia Health Solutions and Vice Chair, The Open Group ArchiMate Forum I recently sat down with my Cambia Health