Compared with Version 3.2, the ArchiMate 4 Specification reduces the number of concepts in the language by 30%, from 60 to 42. The main structural change is the merging of behavior concepts previously divided across the Business, Application, and Technology layers into a single set in the Common Domain. Version 4 also replaces layers with domains, introduces a new depiction of the ArchiMate Framework, generalizes concepts such as Role and Collaboration, removes several specialized concepts, and introduces relationship multiplicity. 

The Open Group introduced the ArchiMate 4 Specification to make the language easier to learn and use while giving practitioners greater modeling freedom. The Specification removes overlapping or rarely used concepts, avoids forcing architects to classify behavior as business, application, or technology too early, and makes it easier to represent processes involving people and machines. 

Yes. The final ArchiMate 4 Specification removes seven concepts from Version 3.2. Business Interaction, Application Interaction, and Technology Interaction can be represented using Process and the relevant participants. Representation can be modeled using Material for paper or Data Object and Artifact for digital representations. Contract can be represented as a Business Object, Constraint as a Requirement, and Gap as an Assessment of the difference between two architecture states represented by Plateaus. For more detail, see the final ArchiMate 4® Specification and the accompanying motivation white paper by Marc Lankhorst and Jean-Baptiste Sarrodie, which explains the rationale and available conversion options.uses the term “removed”. 

The familiar Business, Application, and Technology divisions remain, but the ArchiMate 4 Specification calls them domains rather than layers. Shared concepts that apply across these domains, including Process, are part of the Common Domain. This makes clear that the Business, Application, and Technology Domains represent different parts of the language rather than abstraction levels or a strict hierarchy in which business is served by applications and applications are served by infrastructure.

No. Existing ArchiMate 3.2 practitioners do not need to relearn the language from scratch. They need to understand the streamlined vocabulary of the ArchiMate 4 Specification, the move from layers to domains, and the new modeling options, but Version 4 retains the language’s underlying structure, core purpose, expressive power, and key design principles.