Business Architecture Modeling With ArchiMate

Business Architecture can be modelled with small set of diagrams and subset of ArchiMate elements. Here is introduced some typical diagram types, that can be used for business layer modelling, as well as linking business layer to application layer. Most of the diagram types introduced here are variations of the Layered View diagram type.

Business Services View

This is a simplification of layered view of business services. This view introduces how business services are produced and to which business actors they are provided. ArchiMate elements used in the diagram below are as follows: Business Actor, Business Service and Business Process.

Business Services View.

Note! These variations of Layered View diagrams illustrate how the layers interact. E.g. Customer Groups  and Business Services (both of which belong to the Business Layer). These diagrams are kind of MVP (Minimum Viable Product) simplifications, that can be used for more detailed modelling if necessary. For example, the business services can be directly connected with the customer groups. This can be the case if we’d like to specifically illustrate what business service is serving which customer groups exactly.

Business Channels View

Business services can be provided with certain channels, those of which can be introduced between business services and customers. ArchiMate element Business Interface is used in between Business Actor and Business Service elements. The serving relation from business services to customers is not visible in the figure below, but the relation exists in the repository.

Business Channels View.

Business Service Realization View

This view extends the Business Service View by introducing more detailed how the business services are realized. Business services are typically realized by the business processes. In addition, those business processes use application services that are provided by application components. In the figure below, Application layer elements Application Service and Application Component are added below the Business Process elements.

Business Services Realization View

Business Actor Co-operation View

This view enables business analyst to model interactions between business actors that are relevant in the context. E.g. complex business collaborations or ecosystems.

Business Actor Co-Operation View.

Business Process Co-operation View

Business process integrations can be modelled with this view.

Business Process Co-operation View.

Business Process View

A business process can be modelled more detailed as shown below.

Business Process View.

Business Object View

Business objects (a.k.a. Business concepts) can be linked to processes, by modelling how they access the business objects (figure below).

Business Objects View.

Productized Business Services

Business services can be productized. ArchiMate element Product (link) can be used for composing business services within a product.

Business Services And Products View.

The “Product B” above is composed of business services “B-1” and “B-2”, which are nested inside the “Product B” element (composition relations exists in the repository, even though they are not visible).

Layered View

The most useful diagram type, the Layered View, is illustrated below. The classic Layered View covers all the layers and related elements that are relevant for the case. The Layered View can be applied to what is appropriate depending on the case.

Layered View.

Conclusions

Business Architecture can be modelled with small set of diagram types with subset of ArchiMate elements. ArchiMate is powerful standard notation, which covers several layers with multiple elements. As such, ArchiMate enables a business analyst to model diverse of cases of business architecture, and whenever necessary, all the relations to application- and technology architectures, as well as relations to information architecture.

Business Architecture modelling with ArchiMate can utilize Service-Driven Approach (SDA), which focuses on services rather than projects for example. In SDA, a service is crucial concept, to which a value can be associated and which represents the primary unit of design, development and operation…

 

 

Leave a comment

Your email address will not be published. Required fields are marked *