Enterprise Architecture Views and Viewpoints in ArchiMate - Reference

Similar documents
Enterprise Architecture Views and Viewpoints in ArchiMate

Alignment of Business and IT - ArchiMate. Dr. Barbara Re

ArchiMate 2.0. Structural Concepts Behavioral Concepts Informational Concepts. Business. Application. Technology


Enterprise Architecture

The three element types, connected by relations, can form sentences of sorts.

HPE Enterprise Maps Data Model, ArchiMate, TOGAF. HPE Software, Cloud and Automation

ArchiMate Trick or Treat?

Conceptual Framework

Enterprise Architecture Frameworks

Avancier Methods (AM) Software Architecture Diagrams

INF5120 and INF9120 Modelbased System development

Enterprise Architecture Modelling with ArchiMate 3 - Overview

ArchiMate

Brief introduction of WG 3

TOGAF 9 Foundation v9.1 Level 1 Level 1: An Introduction to TOGAF

ArchiMate symbols for relating system elements

ArchiMate 2.0. A Step Towards A Common Language. Michelle van den Berg EA Consultant. 44 Montgomery Street Suite 960 San Francisco, CA USA

TOGAF The Open Group Architecture Framework

OG The Open Group OG TOGAF 9 Combined Part 1 and Part 2

Unit Wise Questions. Unit-1 Concepts

The ERA of Enterprise Architecture 2.0

OG0-091 Q&As TOGAF 9 Part 1

Strategy & Architecture Framework. Modeling Language Alain De Preter - All rights reserved - Tous droits réservés

Generic vs. Domain-specific Modeling Languages

Copyright protected. Use is for Single Users only via a VHP Approved License. For information and printed versions please see

Enterprise Architecture Frameworks

Avancier Methods (AM) CONCEPTS

Module E1 TOGAF 9.1 Changes Overview

<<Subsystem>> Software Architecture Document

Vendor: The Open Group. Exam Code: OG Exam Name: TOGAF 9 Part 1. Version: Demo

WHAT IS SOFTWARE ARCHITECTURE?

1 Executive Overview The Benefits and Objectives of BPDM

Requirements Validation and Negotiation (cont d)

Enterprise Architect. User Guide Series. UML Models. Author: Sparx Systems. Date: 30/06/2017. Version: 1.0 CREATED WITH

Introduction in the Dragon1 open EA Method

Visualizing IT at the Department of Homeland Security with the ArchiMate Visual Modeling Language

TOWARDS A META-MODEL FOR COLLABORATIVE CONSTRUCTION PROJECT MANAGEMENT

Business Architecture in Healthcare

ArchiMate 2.0 Standard Courseware. Course Introduction

Design of Embedded Systems

S1 Informatic Engineering

SOFTWARE DESIGN COSC 4353 / Dr. Raj Singh

ArchiMate Language Primer. Introduction to the ArchiMate Modelling Language for Enterprise Architecture

The Role of the Chief Information Security Officer

European Component Oriented Architecture (ECOA ) Collaboration Programme: Architecture Specification Part 2: Definitions

KillTest *KIJGT 3WCNKV[ $GVVGT 5GTXKEG Q&A NZZV ]]] QORRZKYZ IUS =K ULLKX LXKK [VJGZK YKX\OIK LUX UTK _KGX

An informal discussion Life Cycle Interaction & Control Points for Enterprise ~ Solution Architecture.

BSIF. A Freeware Framework for. Integrated Business Solutions Modeling. Using. Sparx Systems. Enterprise Architect

Enterprise Architecture Method

PASS4TEST. IT Certification Guaranteed, The Easy Way! We offer free update service for one year

Solution Architecture Template (SAT) Design Guidelines

Software Service Engineering

The Open Group SOA Ontology Technical Standard. Clive Hatton

Unified Modeling Language (UML)

Model Driven Development of Component Centric Applications

Business Architecture concepts and components: BA Process Flow

Enterprise Architect for an Enterprise Architecture. The combination of Sparx EA and ArchiMate 2.0

SOFTWARE ARCHITECTURE & DESIGN INTRODUCTION

Chapter : Analysis Modeling

Designing Component-Based Architectures with Rational Rose RealTime

Concepts for Modelling Enterprise Architectures

Getting Hybrid IT Right. A Softchoice Guide to Hybrid Cloud Adoption

The Great TOGAF Scavenger Hunt. Enterprise Architecture Using TOGAF 9 Course Preparation Guide

Enterprise Architect. User Guide Series. Perspectives

for TOGAF Practitioners Hands-on training to deliver an Architecture Project using the TOGAF Architecture Development Method

IT Expert (Enterprise Network and Infrastructure Architect)

The South African EA Forum

bahmanzamani.com Computer Engineering i Dept. University of Isfahan

Introduction to the RAMI 4.0 Toolbox

Object-Oriented Analysis and Design Using UML (OO-226)

EUROPEAN ICT PROFESSIONAL ROLE PROFILES VERSION 2 CWA 16458:2018 LOGFILE

Passport Automation System

1. You should attempt all 40 questions. Each question is worth one mark.

Calgary: 10th Floor Bankers Hall, West Tower 888-3rd Street SW, Calgary, AB T2P 5C5 p: f:

BUSINESS REQUIREMENTS SPECIFICATION (BRS) Documentation Template

Enterprise Architect. User Guide Series. Domain Models

IBM Industry Model support for a data lake architecture

Models and Frameworks

Final Project Report. Abstract. Document information

1. What is the relationship between non-functional requirements and technology architecture?

Software Life-Cycle Management

2 The BEinGRID Project

Objectives. Explain the purpose and objectives of objectoriented. Develop design class diagrams

Delivering Enterprise Architecture with TOGAF and ArchiMate

Enterprise Architect Training Courses

WebSphere Commerce Developer Professional 9.0

Orthographic Software Modeling A Practical Approach to View Based Development

LOG8430: Architecture logicielle et conception avancée

Requirements Validation and Negotiation

Meta-Modeling and Modeling Languages

UNIT II. Syllabus. a. An Overview of the UML: Visualizing, Specifying, Constructing, Documenting

ArchiMate Certification for People Conformance Requirements

The Unified Modeling Language (UML ) Using Enterprise Architect 13.x or 14.x

Why do architects need more than TOGAF?

Computational thinking, problem-solving and programming:

Cloud solution consultant

Module B1 An Introduction to TOGAF 9.1 for those familiar with TOGAF 8

Enterprise Architecture Model Transformation

Information sharing in the EU policy on NIS & CIIP. Andrea Servida European Commission DG INFSO-A3

Transcription:

Enterprise Architecture Views and Viewpoints in ArchiMate - Reference Source: ArchiMate 2.0 Specification, chapter 8, http://pubs.opengroup.org/architecture/archimate2-doc/chap08.html

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 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? 3

Two-Dimensional Classification of Enterprise Architecture Viewpoints Purpose Dimension Designing support design process from initial sketch to detailed design Deciding: offering insight into cross-domain architecture relations Informing: achieve understanding, obtain commitment, convince Content Dimension Details: one layer and one aspect Coherence: multiple layers or multiple aspects focus on architecture relations between layers or aspects Overview: both multiple layers and aspects ArchiMate - Views and Viewpoints 4

Viewpoints in ArchiMate These viewpoints are suggested in ArchiMate based on experience: 1. Introductory Viewpoint 2. Organization Viewpoint 3. Actor Co-operation Viewpoint 4. Business Function Viewpoint 5. Business Process Viewpoint 6. Business Process Co-operation Viewpoint 7. Product Viewpoint 8. Application Behavior Viewpoint 9. Application Co-operation Viewpoint 10. Application Structure Viewpoint 11. Application Usage Viewpoint 12. Infrastructure Viewpoint 13. Infrastructure Usage Viewpoint 14. Implementation and Deployment Viewpoint 15. Information Structure Viewpoint 16. Service Realization Viewpoint 17. Layered Viewpoint 18. Landscape Map Viewpoint 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: ArchiMate - Views and Viewpoints 6

Example of a Model from the Introductory Viewpoint ArchiMate - Views and Viewpoints 7

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: ArchiMate - Views and Viewpoints 8

Example of a Model from the Organization Viewpoint ArchiMate - Views and Viewpoints 9

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: ArchiMate - Views and Viewpoints 10

Example of a Model from the Actor Co-operation Viewpoint ArchiMate - Views and Viewpoints 11

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: ArchiMate - Views and Viewpoints 12

Example of a Model from the Business Function Viewpoint ArchiMate - Views and Viewpoints 13

Business Process Viewpoint Structure and composition of one or more business processes and directly related concepts like products, roles, and information Concepts and Relationships: ArchiMate - Views and Viewpoints 14

Example of a Model from the Business Process Viewpoint ArchiMate - Views and Viewpoints 15

Business Process Co-operation Viewpoint Relations of one or more business processes with each other and/or the environment. Concepts and Relationships: ArchiMate - Views and Viewpoints 16

Example of a Model from the Business Process Cooperation Viewpoint ArchiMate - Views and Viewpoints 17

Product Viewpoint Composition of products, the associated contract(s) or agreements, and the products value to customers and other external parties.. Concepts and Relationships: ArchiMate - Views and Viewpoints 18

Example of a Model from the Product Viewpoint ArchiMate - Views and Viewpoints 19

Application Behavior Viewpoint Internal behavior of an application, e.g. as it realizes one or more services Concepts and Relationships: ArchiMate - Views and Viewpoints 20

Example of a Model from the Application Behavior Viewpoint ArchiMate - Views and Viewpoints 21

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: ArchiMate - Views and Viewpoints 22

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. ArchiMate - Views and Viewpoints 23

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: ArchiMate - Views and Viewpoints 24

Example of a Model from the Application Structure Viewpoint ArchiMate - Views and Viewpoints 25

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: ArchiMate - Views and Viewpoints 26

Example of a Model from the Application Usage Viewpoint ArchiMate - Views and Viewpoints 27

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: ArchiMate - Views and Viewpoints 28

Example of a Model from the Infrastructure Viewpoint ArchiMate - Views and Viewpoints 29

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: ArchiMate - Views and Viewpoints 30

Example of a Model from the Infrastructure Usage Viewpoint ArchiMate - Views and Viewpoints 31

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: ArchiMate - Views and Viewpoints 32

Example of a Model from the Implementation and Deployment Viewpoint ArchiMate - Views and Viewpoints 33

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: ArchiMate - Views and Viewpoints 34

Example of a Model from the Information Structure Viewpoint ArchiMate - Views and Viewpoints 35

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: ArchiMate - Views and Viewpoints 36

Example of a Model from the Service Realization Viewpoint ArchiMate - Views and Viewpoints 37

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 ArchiMate - Views and Viewpoints 38

Example of a Model from the Layered Viewpoint ArchiMate - Views and Viewpoints 39

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 ArchiMate - Views and Viewpoints 40

Example of a Model from the Landscape Map Viewpoint ArchiMate - Views and Viewpoints 41