Enterprise Architecture Modeling

With ArchiMate & Sparx

Adnaan Sikandar
Capgemini Canada Inc.
[email protected]
AGENDA
 ArchiMate Overview

 ArchiMate Concepts
• Framework & Concept
• Layers
• Metamodels

 ArchiMate Viewpoints
• Information Structure Viewpoint
• Business Process Viewpoint
• Layered Viewpoint
• Infrastructure Viewpoint
• TOGAF ADM Viewpoints
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 TOGAF’s architecture

artifacts – TOGAF does not provide descriptions and examples
ARCHIMATE
 Which version should I use?
• Technical Specification 1.0 (Approved)
• Technical Specification 2.0 (Under Review)

 Is it a standard?
• The Open Group’s ArchiMate Forum – Stewards of the ArchiMate
standard

 What about the license?

• Capgemini is an ArchiMate Forum member
• ArchiMate Forum members have commercial license to use it for
consulting engagements
ArchiMate – Concepts
ARCHIMATE FRAMEWORK

Products &
Services Business
Business Functions Organisation
Information Processes

Application Data Applications

Technology Technical Infrastructure

Information Behavior Structure

ARCHIMATE CONCEPT
ArchiMate Structure - Services
Customer

External
business service Business

Internal
business service

External
application service Application

Internal
application service

External
infra. service Technology

Internal
infra. service
ARCHIMATE STRUCTURE - LAYERS
 Layers
• Business Layer - Offers products and services to external customers, which are realized
in the organization by business processes performed by business actors
• Application Layer - Supports the business layer with application services which are
realized by (software) applications.
• Technology Layer - offers infrastructure services (e.g., processing, storage, and
communication services) needed to run applications, realized by computer and
communication hardware and system software.

 Generic Metamodel For Each Layer

External Service Interface

Object Behavior Structure

Internal element element

Information Behavior Structure

METAMODEL – BUSINESS LAYER
LANGUAGE NOTATIONS
BUSINESS LAYER - SPARX EXAMPLE

Actors
Tier 1 Help Desk Agent

IT Help Desk

Assigned To Assigned To
Exception Management Process

Triggers Flows Flows Flows

SMI Events Create Event Correlate & Analyze Triage & Resolve Close Exception
Exceptions (Automatic) Event (Automatic) Exception Ticket Ticket
METAMODEL – APPLICATION LAYER
METAMODEL – TECHNOLOGY LAYER
ArchiMate – Viewpoints
Basic ArchiMate Viewpoints
 Introductory Viewpoint  Infrastructure Viewpoint
 Organization Viewpoint  Infrastructure Usage Viewpoint
 Actor Co-operation Viewpoint  Implementation and Deployment
 Business Function Viewpoint Viewpoint
 Business Process Viewpoint  Information Structure Viewpoint
 Business Process Co-operation
 Service Realization Viewpoint
Viewpoint
 Product Viewpoint  Layered Viewpoint
 Application Behavior Viewpoint  Landscape Map Viewpoint
 Application Co-operation Viewpoint
 Application Structure Viewpoint
 Application Usage Viewpoint
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

ACTOR CO-OPERATION VIEWPOINT

Service Desk Business Actor A

Service Desk Manager Operations Optimization

Business Actor B

«Tickets»
«Tickets»

«Tickets»
Tier 1 Service Desk Business Actor C

«Tickets»

«Tickets»
Business Actor D
«Tickets» «Tickets» «Tickets»

Tier 2 Applicaiton Tier 2 System Tier 2 Network

Administration Administration Administration
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

LAYERED VIEWPOINT – SPARX EXAMPLE
Actors
Tier 1 Help Desk Agent

IT Help Desk

Exception Management Process

SMI Events Create Event Correlate & Analyze Triage & Resolve Close Exception
Exceptions (Automatic) Event (Automatic) Exception Ticket Ticket

Application Services

Event Logging Event Correlation Event Analysis Ticket Service Work Instructions
Service Service Service Service

Application Components

Event Trouble Ticket Knowledge

Correlation & Management Management
Analysis

Applications

BMC Event Manager BMC Remedy ITSM

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
BUSINESS PROCESS VIEW POINT – SPARX EXAMPLE
Actors
IT Help Desk Tier 1 Agent

IT Help Desk

Process

Event Create Event Correlate & Analyze Resolve Exception Close Exception
(Automatic) Event (Automatic) Ticket Ticket

Create / Read
Read Update Update
Create / Update Create
Read Read

Read Read
Network Topology
Event Exception Ticket
Read

Asset Network Device

Rules Device

Event Thresholds
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

INFRASTRUCTURE VIEW POINT – SPARX EXAMPLE

Mobile Field Force Database Mobile Field Force

Security Context Application Security Context

Database SSL Internet

Information
Server

Windows Windows

HTTPS

Secure Zone

Corporate LAN HTTPS HTTPS Private APN HTTPS

HTTPS

Office Application Internal Firewall Mobile Tablets

APPLICATION LANDSCAPE VIEW POINT
Baseline Application Model
Level 1 Process

Existing System Existing System Existing System Existing System Existing System Existing System
A B C D E F

Target Application Model

Level 1 Process

Existing System Existing System Existing System Existing System Existing System Existing System
A B C D E F

New System X New System Y New System Z

ARCHIMATE RESOURCES
 ArchiMate 1.0 Technical Specification

 ArchiMate Good Practices

 Sparx Enterprise Architect

 ArchiMate Presentations