CapArchimate

8/22/2019 CapArchimate

1/26

Adnaan SikandarCapgemini Canada [email protected]

Enterprise Architecture ModelingWith ArchiMate & Sparx


2/26

AGENDA

ArchiMate Overview

ArchiMate Concepts

Framework & Concept

Layers

Metamodels

ArchiMate Viewpoints

Information Structure Viewpoint

Business Process Viewpoint Layered Viewpoint

Infrastructure Viewpoint

TOGAF ADM Viewpoints


3/26

ARCHIMATE

What is it?

ArchiMate is a modeling language for describing enterprise architectures

Broader scope than UML. UML is for software engineering

Supports EA frameworks like TOGAF & Zachman

Can be used to create IAF views and artifacts

ArchiMate viewpoints are more detailed than TOGAFs architecture

artifacts TOGAF does not provide descriptions and examples


4/26

ARCHIMATE

Which version should I use?

Technical Specification 1.0 (Approved) Technical Specification 2.0 (Under Review)

Is it a standard?

The Open Groups ArchiMate Forum Stewards of the ArchiMatestandard

What about the license?

Capgemini is an ArchiMate Forum member

ArchiMate Forum members have commercial license to use it for

consulting engagements


5/26

ArchiMate Concepts


6/26

ARCHIMATE FRAMEWORK

Technology

Application

Business

Information Behavior Structure

ProcessesInformation

Data

Organisation

Products &

Services

Applications

Technical Infrastructure

BusinessFunctions


7/26

ARCHIMATE CONCEPT


8/26

ArchiMate Structure - Services

External

business service

Internal

business service

Internal

infra. service

External

infra. service Technology

Application

Business

Customer

External

application service

Internal

application service


9/26

ARCHIMATE STRUCTURE - LAYERS

Layers

Business Layer - Offers products and services to external customers, which are realizedin the organization by business processes performed by business actors

Application Layer - Supports the business layer with application services which arerealized by (software) applications.

Technology Layer - offers infrastructure services (e.g., processing, storage, andcommunication services) needed to run applications, realized by computer and

communication hardware and system software.

Generic Metamodel For Each Layer

Internal

External

Information Behavior Structure

Structure

element

Object

Service Interface

Behavior

element


10/26

METAMODEL BUSINESS LAYER


11/26

LANGUAGE NOTATIONS


12/26

BUSINESS LAYER - SPARX EXAMPLE

Actors

IT Help Desk

Exception Management Process

Create Event

(Automatic)

Correlate & Analyze

Event (Automatic)Triage & Resolve

Exception Ti cket

Close Exception

Ticket

SMI Events

Exceptions

Tier 1 Help Desk Agent

Flows Flows Flows

Assigned T o

Triggers

Assigned T o


13/26

METAMODEL APPLICATION LAYER


14/26

METAMODEL TECHNOLOGY LAYER


15/26

ArchiMate Viewpoints


16/26

Basic ArchiMate Viewpoints

Introductory Viewpoint

Organization Viewpoint

Actor Co-operation Viewpoint

Business Function Viewpoint

Business Process Viewpoint

Business Process Co-operation

Viewpoint

Product Viewpoint

Application Behavior Viewpoint

Application Co-operation Viewpoint

Application Structure Viewpoint

Application Usage Viewpoint

Infrastructure Viewpoint

Infrastructure Usage Viewpoint

Implementation and Deployment

Viewpoint

Information Structure Viewpoint

Service Realization Viewpoint

Layered Viewpoint

Landscape Map Viewpoint


17/26

ACTOR CO-OPERATION VIEWPOINT

Layered View Point

Stakeholders Enterprise, process, and domain architects

Concerns Relations of actors with their environment

Purpose Designing, deciding, informing

Abstraction Level Details

Business layer Business layer

Aspects Structure, behavior


18/26

ACTOR CO-OPERATION VIEWPOINT

Service Desk

Service Desk Manager

Tier 1 Service Desk

Tier 2 Applicaiton

Admi nistration

Tier 2 System

Admi nistration

Tier 2 Network

Admi nistration

Operations Optimizati on

Business Actor A

Business Actor B

Business Actor D

Business Actor C

Tickets

Tickets

Tickets

Tickets

TicketsTicketsTickets

Tickets


19/26

LAYERED VIEWPOINT

Layered View Point

Stakeholders Enterprise, process, application, infrastructure, and domain architects

Concerns Consistency, reduction of complexity, impact of change, flexibility

Purpose Designing, deciding, informing

Abstraction Level Overview

Layer Business layer, application layer, technology layer

Aspects Information, behavior, structure


20/26

LAYERED VIEWPOINT SPARX EXAMPLE

Application Services

Application Components

Actors

IT Help Desk

Exception Management Process

Create Event

(Automatic)

Correlate & Analyze

Event (Automatic)

Event Analysis

Service

Triage & Resolve

Exception Ti cket

Close Exception

Ticket

SMI Events

Exceptions

Event

Correlatio n &

Anal ysis

Trouble Ticket

Management

Ticket ServiceEvent Logging

Service

Knowledge

Management

Tier 1 Help Desk Agent

Work Instruction s

ServiceEvent Correlation

Service

Applications

BMC Event Manager BMC Remedy ITSM


21/26

BUSINESS PROCESS VIEW POINT

Business Process View Point

Stakeholders Process and domain architects, operational managers

Concerns Structure of business processes, consistency and completeness, responsibilities

Purpose Designing

Abstraction Level Detail

Layer Business layer

Aspects Behavior


22/26

BUSINESS PROCESS VIEW POINT SPARX EXAMPLEActors

IT Help Desk

Process

Create Event

(Automatic)

Correlate & Analyze

Event (Automatic)

Resolve Exception

Ticket

Close Exception

Ticket

Event

IT Help Desk Tier 1 Agent

Event Exception Ticket

Asset

Device

Network Topology

Rules

Event T hresholds

Network Device

Read

Create / Update

Create / Read

Create

Read

Read

Read

Update Update

Read

Read


23/26

INFRASTRUCTURE VIEW POINT

Business Process View Point

Stakeholders Infrastructure architects, Operational Managers

Concerns Stability, security, dependencies, infrastructure costs

Purpose Designing

Abstraction Level Detail

Layer Technology

Aspects Behavior, Structure


24/26

INFRASTRUCTURE VIEW POINT SPARX EXAMPLE

Mobile Field Force Database

Security Context

Secure Zone

Windows

Corporate LAN

Office Application Internal Firewall

Database

Windows

Internet

Information

Server

Private APN

Mobile Tablets

Mobile Field Force

Application Security Context

HTTPSHTTPS

HTTPS

HTTPSHTTPS

SSL


25/26

APPLICATION LANDSCAPE VIEW POINT

Baseline Application Model

Target Application Model

Level 1 Process

Existing System

A

Existing System

B

Existing System

C

Existing System

D

Existing System

F

Existing System

E

Level 1 Process

Existing System

A

Existing System

B

Existing System

C

Existing System

D

Existing System

F

Existing System

E

New System Y New System ZNew System X


26/26

ARCHIMATE RESOURCES

ArchiMate 1.0 Technical Specification

ArchiMate Good Practices

Sparx Enterprise Architect

ArchiMate Presentations
http://www.opengroup.org/archimate/doc/ts_archimate/http://www.archimate.nl/en/start_using_archimate/good_practices.htmlhttp://www.sparxsystems.com.au/https://doc.telin.nl/dsweb/View/Collection-4768https://doc.telin.nl/dsweb/View/Collection-4768https://doc.telin.nl/dsweb/View/Collection-4768https://doc.telin.nl/dsweb/View/Collection-4768http://www.sparxsystems.com.au/http://www.sparxsystems.com.au/http://www.sparxsystems.com.au/http://www.archimate.nl/en/start_using_archimate/good_practices.htmlhttp://www.archimate.nl/en/start_using_archimate/good_practices.htmlhttp://www.archimate.nl/en/start_using_archimate/good_practices.htmlhttp://www.opengroup.org/archimate/doc/ts_archimate/http://www.opengroup.org/archimate/doc/ts_archimate/http://www.opengroup.org/archimate/doc/ts_archimate/

Date post:	08-Aug-2018
Category:	Documents
Upload:	pablo-ballarin
View:	215 times
Download:	0 times

CapArchimate

Documents