Diagram
Content may include inaccuracies, outdated information, or technical errors. Users are advised to cross-check critical information before implementation.
An ArchiMate diagram is an object of the model: it is stored in the Views folder and created like any other object.
Create a diagram
- Right-click the Views folder and choose New object.
- Pick ArchiMate View in Object type.
- Click Create.
The view appears in the folder and opens in the editing area, empty.
A model may hold as many views as you need, and they all draw on the same concepts. An element shown on three views is one element: rename it on one and the other two follow.
Viewpoint
Select the view and look at the details panel. Besides Name and Documentation it has Viewpoint.
A viewpoint narrows the view to one subject. Assign Application Cooperation, and the palette offers application-layer concepts and Location, nothing else. What is already on the view stays there and stays editable - the restriction applies to what you add next. Clear the viewpoint and the full ArchiMate set returns.
| Viewpoint | The subject it serves |
|---|---|
| Organization | Who works in the enterprise and in which roles |
| Business Process Cooperation | How processes depend on each other and on applications |
| Product | What a product consists of |
| Application Cooperation | Which components talk to each other and about what |
| Application Structure | The inside of one application and the data it owns |
| Application Usage | Which parts of the business consume which application services |
| Technology | Nodes, devices, system software, networks |
| Technology Usage | How applications depend on the technology beneath them |
| Implementation and Deployment | How applications are deployed onto infrastructure |
| Physical | Equipment, facilities and the movement of materials |
| Information Structure | Which information the enterprise owns |
| Service Realization | How a business service is delivered |
| Stakeholder | Interests, drivers and assessments |
| Goal Realization | A goal broken down into outcomes and requirements |
| Requirements Realization | Which parts of the architecture answer each requirement |
| Motivation | The motivation model on its own |
| Strategy | Capabilities, resources, value streams, courses of action |
| Capability Map | The capability landscape as a whole |
| Value Stream | The stages of value creation |
| Resource Map | Which resources support which capabilities |
| Outcome Realization | The path from an outcome to the architecture behind it |
| Project | Who delivers which work package |
| Migration | Plateaus and gaps between two architectures |
| Implementation and Migration | What each plateau delivers |
| Layered | No restriction: the whole language |
Now put something on the view, see Place elements and draw relationships.