Enterprise Architecture Modeling With ArchiMate & Sparx

Adnaan Sikandar Capgemini Canada Inc.

Adnaan.Sikandar@capgemini.com

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 TOGAFs 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 Groups 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 Functions Organisation

Business

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 Internal application service

Application

External infra. service Internal infra. service

Technology

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

Internal

Object

Behavior element

Structure 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

SMI Events Exceptions

Triggers Create Event (Automatic)

Flows Correlate & Analyze Event (Automatic)

Flows Triage & Resolve Exception Ticket

Flows Close Exception Ticket

METAMODEL APPLICATION LAYER

METAMODEL TECHNOLOGY LAYER

ArchiMate Viewpoints

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

ACTOR CO-OPERATION VIEWPOINT

Layered View Point Stakeholders Concerns Purpose Abstraction Level Business layer Aspects Enterprise, process, and domain architects Relations of actors with their environment Designing, deciding, informing Details Business layer 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 Tickets Business Actor C

Tickets Tickets Tickets Tickets Business Actor D

Tier 2 Applicaiton Administration

Tier 2 System Administration

Tier 2 Network Administration

LAYERED VIEWPOINT
Layered View Point Stakeholders Concerns Purpose Abstraction Level Layer Aspects Enterprise, process, application, infrastructure, and domain architects Consistency, reduction of complexity, impact of change, flexibility Designing, deciding, informing Overview Business layer, application layer, technology layer Information, behavior, structure

LAYERED VIEWPOINT SPARX EXAMPLE

Actors
Tier 1 Help Desk Agent IT Help Desk

Exception Management Process

SMI Events Exceptions

Create Event (Automatic)

Correlate & Analyze Event (Automatic)

Triage & Resolve Exception Ticket

Close Exception Ticket

Application Services

Event Logging Service

Event Correlation Service

Event Analysis Service

Ticket Service

Work Instructions Service

Application Components

Event Correlation & Analysis

Trouble Ticket Management

Knowledge Management

Applications

BMC Event Manager

BMC Remedy ITSM

BUSINESS PROCESS VIEW POINT

Business Process View Point Stakeholders Concerns Purpose Abstraction Level Layer Aspects Process and domain architects, operational managers Structure of business processes, consistency and completeness, responsibilities Designing Detail Business layer Behavior

BUSINESS PROCESS VIEW POINT SPARX EXAMPLE

Actors
IT Help Desk Tier 1 Agent IT Help Desk

Process

Event

Create Event (Automatic)

Correlate & Analyze Event (Automatic)

Resolve Exception Ticket

Close Exception Ticket

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

Read Create

Update

Update

Network Topology

Exception Ticket

Asset

Network Device

Rules

Device

Event Thresholds

INFRASTRUCTURE VIEW POINT

Business Process View Point Stakeholders Concerns Purpose Abstraction Level Layer Aspects Infrastructure architects, Operational Managers Stability, security, dependencies, infrastructure costs Designing Detail Technology Behavior, Structure

INFRASTRUCTURE VIEW POINT SPARX EXAMPLE

Mobile Field Force Database Security Context Mobile Field Force Application Security Context

Database

SSL

Internet Information Server Windows HTTPS

Windows

Secure Zone

Corporate LAN HTTPS

HTTPS

HTTPS

Private APN

HTTPS

Office Application

Internal Firewall

Mobile Tablets

APPLICATION LANDSCAPE VIEW POINT

Baseline Application Model
Level 1 Process

Existing System A

Existing System B

Existing System C

Existing System D

Existing System E

Existing System F

Target Application Model

Level 1 Process

Existing System A

Existing System B

Existing System C

Existing System D

Existing System E

Existing System 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