ArchiMate architecture diagrams

Start with a service and its consumer

1. Create an ArchiMate model.
2. Add the application concept providing a student service, an Application Service, and a Business Process that uses the service.
3. Use Realization from an implementing concept to what it realises, and Serving from the service to its consumer.
4. Add ownership or lifecycle properties, then create a view for the audience you want to address.
5. Save the view and model, and reopen the result.

Read relationship direction

Serving runs provider to consumer. Assignment runs an actor/role/component/node to the behaviour it performs. Triggering runs preceding behaviour to subsequent behaviour. Flow runs sender to receiver; label what flows. Access runs active behaviour/structure to the passive object accessed. Composition and Aggregation run whole to part, with the diamond at the whole.

Build views across layers

Start with a business-service discussion, then show the applications and technology that support it. Use explicit membership to focus each view while keeping common elements shared. Colour by Owner or Lifecycle when that answers a different question from the notation's default colours.

Supported scope

The available element types include business, application, technology, strategy, motivation and implementation/migration concepts. The current relationship choices are listed below. Influence, Specialization and junctions are not included in that set; the app does not enforce the complete ArchiMate metamodel relationship matrix.

PlantUML ArchiMate is a supported text route. For file compatibility, see the import guide.

Download the architecture service example (JSON)

Try this with Rovo in Confluence

Choose the matching Revelation agent. Supply the destination page and review the result before sharing. Follow the Rovo guide to attach the created model to a macro.

Create an ArchiMate model showing a student self-service application service and the business process it serves. Use provider-to-consumer Serving direction and keep the model small.

Supported element types

Supported relationship types