member of
Enterprise Architecture Views and
Viewpoints in ArchiMate - Reference
Source: ArchiMate 2.1 Specification, chapter 8, http://pubs.opengroup.org/architecture/archimate2-doc/chap08.html
Prof. Dr. Knut Hinkelmann
Views and Viewpoints in ArchiMate
■ In ArchiMate, architects and other stakeholders can
define their own views on the enterprise architecture
■ A viewpoint in ArchiMate is a selection of
♦ a relevant subset of the ArchiMate concepts and their
relationships
♦ For each viewpoint one model kind exists
■ A view is (a set of) models
♦ representing a part of an architecture
♦ using the concepts and relationships of the
corresponding viewpoint
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 2
Examples of Stakeholders and Concerns
The following examples of stakeholders and concerns are mentioned in the
ArchiMate specification as a basis for the specification of viewpoints:
End Users
♦ What are the consequences for his workplace?
Architect
♦ What is the consequence for the maintainability of a system?
Upper-level Management
♦ How can we ensure that our policies are followed in the development and operation
of processes and systems?
Operational Manager – responsible for exploitation or maintenance
♦ Is there a need to adapt maintenance processes?
Project Manager – responsible for development of new applications
♦ What is the dependence of business processes on the applications to be built?
Developer
♦ What are the required modification with respect to the current situation?
Prof. Dr. Knut Hinkelmann 3
Two-Dimensional Classification of Enterprise
Architecture Viewpoints
Purpose Dimension
Content Dimension
■ Designing
♦ support design process from
■ Details:
initial sketch to detailed design ♦ one layer and one aspect
■ Deciding: ■ Coherence:
♦ offering insight into cross-domain ♦ multiple layers or multiple aspects
architecture relations ♦ focus on architecture relations
between layers or aspects
■ Informing:
♦ achieve understanding, obtain ■ Overview:
commitment, convince ♦ both multiple layers and aspects
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 4
Viewpoints in ArchiMate
These viewpoints are suggested in ArchiMate based on experience:
1. Introductory Viewpoint 10. Application Behavior Viewpoint
2. Layered Viewpoint 11. Application Co-operation
3. Landscape Map Viewpoint Viewpoint
4. Organization Viewpoint 12. Application Structure Viewpoint
5. Actor Co-operation Viewpoint 13. Application Usage Viewpoint
6. Business Function Viewpoint 14. Infrastructure Viewpoint
7. Business Process Viewpoint 15. Infrastructure Usage Viewpoint
8. Business Process Co-operation 16. Implementation and Deployment
Viewpoint Viewpoint
9. Product Viewpoint 17. Information Structure Viewpoint
18. Service Realization Viewpoint
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 5
Introductory Viewpoint
A subset of the full ArchiMate language using a simplified notation. Typically used at the
start of a design trajectory, when not everything needs to be detailed or to avoid the
impression that the architectural design is already fixed.
Concepts and Relationships:
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 6
Example of a Model from the Introductory
Viewpoint
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 7
Layered Viewpoint
The Layered viewpoint pictures several layers and aspects of an enterprise architecture in
one diagram.
The layers are the result of the use of the “grouping” relation for a natural partitioning of the
entire set of objects and relations that belong to a model.
Each dedicated layer exposes, by means of the “realization” relation a layer of services,
which are further on “used by” the next dedicated layer.
Concepts and Relationships: all
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 8
Example of a Model from
the Layered Viewpoint
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 9
Landscape Map Viewpoint
A landscape map is a matrix that represents a three-dimensional coordinate system that
represents architectural relations. In practice, often dimensions are chosen from different
architectural domains; for instance, business functions, application components, and
products. A landscape map uses the ArchiMate concepts, but not the standard notation
of these concepts..
Concepts and Relationships: all
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 10
Example of a Model from the Landscape Map
Viewpoint
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 11
Organization Viewpoint
■ (Internal) organization of a company, a department, a network of companies. Could
be modeled as nested diagrams or as organizational charts.
■ Useful in identifying competencies, authority, and repsonsibilities
Concepts and Relations:
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 12
Example of a Model from the Organization
Viewpoint
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 13
Actor Co-operation Viewpoint
■ Extending the Organization Viewpoint with a focus on the relations of actors with each
other and their environment
■ Useful in determining external dependencies and collaborations; shows the value chain or
network in which the actor operates.
■ Can show how a number of co-operating business actors and/or application components
together realize a business process
Concepts and Relationships:
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 14
Example of a Model from the Actor Co-operation
Viewpoint
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 15
Business Function Viewpoint
■ Shows the main business functions of an organisation and their relations in terms of flow of
information, value or goods between them.
Concepts and Relationships:
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 16
Example of a Model from the Business Function
Viewpoint
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 17
Business Process Viewpoint
Structure and composition of one or more business processes and directly related
concepts like products, roles, and information
Concepts and Relationships:
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 18
Example of a Model from the Business Process
Viewpoint
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 19
Business Process Co-operation Viewpoint
Relations of one or more business processes with each other and/or the environment.
Concepts and Relationships:
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 20
Example of a Model from the Business Process
Co-operation Viewpoint
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 21
Product Viewpoint
Composition of products, the associated contract(s) or agreements, and the products’
value to customers and other external parties..
Concepts and Relationships:
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 22
Example of a Model from the Product Viewpoint
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 23
Application Behavior Viewpoint
Internal behavior of an application, e.g. as it realizes one or more services
Concepts and Relationships:
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 24
Example of a Model from the Application
Behavior Viewpoint
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 25
Application Cooperation Viewpoint
Relations between applications components in terms of the information flows between
them, or in terms of the services they offer and use.
Concepts and Relationships:
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 26
Example of a Model from the Application
Co-operation Viewpoint
Relations between applications components in terms of the information flows between
them, or in terms of the services they offer and use.
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 27
Application Structure Viewpoint
Structure of one or more applications or components. This viewpoint is useful in
designing or understanding the main structure of applications or components and the
associated data
Concepts and Relationships:
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 28
Example of a Model from the Application
Structure Viewpoint
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 29
Application Usage Viewpoint
Describes how applications are used to support one or more business processes, and
how they are used by other applications
Concepts and Relationships:
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 30
Example of a Model from the Application Usage
Viewpoint
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 31
Infrastructure Viewpoint
Software and hardware infrastructure elements supporting the application layer, such as
physical devices, networks, or system software (e.g., operating systems, databases, and
middleware).
Concepts and Relationships:
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 32
Example of a Model from the Infrastructure
Viewpoint
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 33
Infrastructure Usage Viewpoint
How applications are supported by the software and hardware infrastructure: the
infrastructure services are delivered by the devices; system software and networks are
provided to the applications
Concepts and Relationships:
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 34
Example of a Model from the Infrastructure
Usage Viewpoint
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 35
Implementation and Deployment Viewpoint
How one or more applications are realized on the infrastructure. This comprises the
mapping of (logical) applications onto (physical) artifacts, such as Enterprise Java
Beans, and the mapping of the information used by these applications onto the
underlying storage infrastructure; e.g., database tables or other files.
Concepts and Relationships:
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 36
Example of a Model from the Implementation and
Deployment Viewpoint
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 37
Information Structure Viewpoint
It shows the structure of the information used in the enterprise or in a specific business
process or application, in terms of data types or (object-oriented) class structures. It is
comparable to the traditional information models created in the development of almost
any information system.
Concepts and Relationships:
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 38
Example of a Model from the Information
Structure Viewpoint
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 39
Service Realization Viewpoint
How one or more business services are realized by the underlying processes (and
sometimes by application components). Thus, it forms the bridge between the business
products viewpoint and the business process view.
Concepts and Relationships:
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 40
Example of a Model from the Service Realization
Viewpoint
Prof. Dr. Knut Hinkelmann ArchiMate - Views and Viewpoints 41
Creating Views
■ A view can be created by
♦ selecting part of a larger model
♦ creating a model which can be added to a larger
model
Prof. Dr. Knut Hinkelmann h dhfs dfs dfsh 42
