ArchiMate offers a visual language to model and capture enterprise architecture. It provides a means to visualize relationships within and between different domains. These domains primarily include products/services, processes, organization, data applications and technical infrastructure.
|May 14, 2014|
|User Rating: / 19|
|PDF Link||Add comments|
|Edition: Enterprise (Edition comparison)|
The domains mentioned above provide contexts for different stakeholders to analyze, design or communicate in order to address their different concerns. For example, a data architect may want to visualize what data are required for which products and services to customers. Perhaps a business analyst is looking to relate logical and physical business processes, which are independent and dependent of implementation, respectively. Or an enterprise architect is working to optimize and best match the applications in use with the existing technical infrastructure.
With 3 types of layers, ArchiMate provides a way to look at service-oriented models. From top to bottom, they are business, application and technology. The further we go down, the more information we get in terms of implementation (sometimes we may use the term "realize" instead).
At the top level, the business layer highlights services provided for customers. In the middle, the application layer focuses on applications that support those services available to customers. At the bottom we can find the technology layer which shows the technical infrastructure offering services to those applications in the application layer.
Below is an ArchiMate diagram example with both the technology and application layer. In it, we can see that the Inpatient care management application is implemented (or realized) by the infrastructure, messaging service and data access service.
In this tutorial, we are going to walk you through how to draw an ArchiMate diagram that looks at the procedures of discharging hospital patients, particularly from a business process viewpoint.
Upon completion of the tutorial, we should end up with a diagram similar to the below.
Note: For simplicity reason, we will limit our discussion to the business layer only in this example.
We'll be using Visual Paradigm Enterprise Edition. You are welcome to download a free evaluation copy.
Some drawing tips
Initially, the process shape is of relatively small size. Here we will make it bigger so that we can draw several processes within it later. To do that, select event Patients' discharge to show the 8 handles in small black squares around it. As an example, place your mouse pointer over the lower right handle. A double-headed arrow will appear on top of the handle. Then pull the arrow to enlarge the shape. Similarly, you can choose to use the other handles to change the size of the shape as you wish.
After you enlarge the shape, it should look something similar to the below (in terms of proportions).
Note: It is not important to get it exact now because you can always resize the shape as you see it fit along the way.
To clear way for us to draw processes within later, let's move the label "Patients' discharge" "up to the top center. To do that, right click on Patients' discharge. From the popup menu, select Presentation Options > Caption Placement > Top Center.
The label should now appear at the top center.
Double click the connector to open the input box. Enter create.
Note: Read access is chosen here (instead of write access) because the invoice is for viewing only as a reference.
Double click the connector to open the input box. Enter read.
Click on one of the stars below to rate this article from 1 (lowest) to 5 (highest).