enterprise architecture modelling with archimate marc lankhorst principal researcher enterprise...
TRANSCRIPT
Enterprise Architecture
Modelling with ArchiMateMarc LankhorstPrincipal Researcher Enterprise Architecture
Utrecht University, January 11, 2010
Overview
• Introduction• Enterprise architecture• The ArchiMate modelling language
• Integration of business, applications, and technology
• Role of service orientation
• Example: ArchiSurance, merger of an insurance company• Relation with other developments
• UML, BPMN
• Zachman Framework
• TOGAF
Novay
• Independent, non-profit research institute
• Founded & funded by companies, the Dutch government,
and universities
• To create impact with ICT innovation
• In projects together with industry and academia
Enterprise Architecture
Context
• Business and ICT become closer
• Ever higher demands on ICT: complexity, flexibility
• Many changes, rapid time-to-market required
• Management & control difficult
• Architecture as a tool
• for communication
• for governance
• for innovation
ArchitectureIEEE Std 1471:
Architecture = structure(s) of a
system in terms of
• components,
• their externally visible properties,
• their relations,
• and the underlying principles
“Structure with a vision”
Mission
Strategy
Actions
Vision
Goalsas is to be
enterprise architecture
domain/aspectarchitectures
culture
people
leadership
Operations…
peopleprocesses ITproducts
Role of Enterprise Architecture
Enterprise Architecture: Describing Coherence
Process architecture
Application architecture Technical architecture
Information architecture Product architecture
?
?
?
?
?
Better Support for the Enterprise Architect
• Increasing need for precise documentation on the enterprise
architecture level
• Integrating various aspect models in many languages (UML, IDEF,
BPMN, ARIS, ...)
• Communicating about architecture with others
• Get away from the “fuzzy pictures” image
• Analysis of architectures before their implementation
• Needed: well-founded, practical, and vendor-independent
standard for enterprise architecture modelling
The ArchiMate Research Project
• 2½ years, July 2002 - December 2004• approx. 35 man-years, 4 million euro • Consortium of companies and knowledge institutes• Directed by Novay (then still Telematica Instituut)
Analysis
ArchiMate Focus
Integration
Visualisation
Idea
Design
Use
Management
Formal modelsAnalysis
NapkinWhiteboardPowerpoint
Link with implementation
MaintenanceVersion control
Communication with stakeholdersVisualisation
Architecture process
ArchiMate Scope
Main Benefits of ArchiMate
• Lean and mean language:• just enough concepts, not bloated to include everything possible
• Well-founded concepts & models give precision • clear communication about architectures
• get away from the ‘fuzzy pictures’ image
• Links to existing approaches• UML, BPMN, TOGAF
• International vendor-independent standard• The Open Group
• Tool support• several tools available
Service Orientation
Design Paradigms
Increased focus on the ‘outside’:• Structured programming• Object orientation• Component-based development• Service-oriented architecture (SOA)• (Event-driven architecture?)
Service Orientation
Service• Unit of externally available functionality• Offered via clear interfaces• Relevant for the environment
Web services as a prominent technological example
Service-Oriented Architecture
Is• A way of thinking• A bridge between business and IT
Is not • Web services• Asynchronous communication• A software artefact (an ESB)
Services are Central to ArchiMate
Externalbusiness service
Internalbusiness service
Internalinfra. service
Externalinfra. service Technology
Application
Business
Customer
Externalapplication service
Internalapplication service
Integrated Modelling
Integration
An architecture might encompass for example:
• products & services
• organisation
• processes
• information
• applications
• systems
• networks
This requires concepts for domains and relations, linked with existing techniques
The ArchiMate Language
ArchiMate languageHigh-level modelling
within a domain
Modelling relations between domains
Basis forvisualisations
Basis foranalysesRelate to
standards
Company-specific concepts, standards, e.g. UML, BPMN
Enterprise architecture concepts
Generic concepts
mor
e ge
neric
mor
e sp
ecifi
c
ProcessApplication
Object
Relation
Abstraction Levels
Layers and Aspects
Technology
Application
Business
Passivestructure
“object”
Behaviour
“verb”
Activestructure
“subject”
ProcessesInformation
Data
Organisation
Products & Services
Applications
Technical Infrastructure
BusinessFunctions
Generic Structure at Each Layer
Internal
External
Passivestructure
Behaviour Activestructure
Structureelement
Object
Service Interface
Behaviourelement
Similar concepts at each layer make the language easier to learn and more consistent in use
(cf. Fred Brooks’ “conceptual integrity”)
Notation
• Most concepts have two notations:
• Icon
• Box with icon
• Sharp corners = structure• Rounded corners = behaviour
• Notation resembles UML and BPMN
• to stay close to what architects already know
• Relations (arrows etc.) are also mostly taken from existing languages, with a few exceptions
Business Functions and Actors
business function
Insurance policies
flow
Contracting ClaimHandling
ArchiSurance
business actor
assignment
product
Travel Insurance
Policy
contract
Product and Services
Security
value
Customerinformation
service
Insuranceapplication
service
Claimregistration
service
Claimregistration
service
Claimpaymentservice
business service
Customerbusiness actor
Insurant
business roleassignment
Business Process
Handle Claim
PayValuateAcceptRegisterDamageoccurred
event
Customer business actor
used by
Insurant business role
business process triggering
Reject
junction
Notification
access
business object
Claim registration
service
Customer Information
service
Claimpaymentservice
business service
realisation
Interfaces & Services
Sellproduct
Buyproduct
Seller Buyer
Selling
business interface
business service
Interacties & Collaborations
Sellproduct
Buyproduct
Completetransaction
Seller Buyer
business collaboration
business interaction
Information
specialisation
Car insurance policy
Home insurance policy
Travel insurance policy
Liability insurance policy
Legal aid insurance policy
aggregation
Customer file
Customer
composition
Damage claimInsurance policyInsurance request
realisation
Claimform
representation
application interface
Application Concepts
Policy administration
application component
Policycreation
application function
Financial administration
Premiumcollection
Customer file
data
Policydata
data object
Policy creationservice
applicationservice
Policyaccessservice
Application Usage by BusinessProcesses
Handle claim
Register PayValuateAcceptNotifi-cation
Financial application
Policy administration
administrationCustomer
service
Paymentservice
CRM system
Claim
serviceadministration
Notifi-cationdata
Technology Concepts
IBM System z Sun Blade
device
Databaseaccessservice
infrastructure service
DB2Database
iPlanetApp. server
system software
LAN
network
association
artifact
Databasetables
Fin.application
EJBs
Deployment
Financial application
CRM system
Customerdata
IBM System z
DB2Database
Sun Blade
iPlanetApp. server
Databaseaccessservice
LANFin.
applicationEJBs
Databasetables
Derived Relations
Client Insurant
Damage claiming process
Registration
Claimregistration
service
administrationCustomer
service
CRM system
?
Weakest link determinescomposition:
association 1
access 2
use 3
realisation 4
assignment 5
aggregation 6
composition 7
LayeredArchitecture
Business layer
Application layer
Technology layer
Internal processes, roles and actors
Infrastructure
External infrastructure services
Application components and services
External processes, roles and actors
External application services
External business services
Handle claim
CustomerInsurant
Registration PaymentValuationAcceptance
Customer information
service
Claimspaymentservice
Customer administration
service
Paymentservice
CRM system
Financial application
Customerinformation
service
Claimregistration
service
Claims administration
service
Policy administration
Claimfiles
service
IBM System z
DB2Financial
applicationEJBs
Customerfiles
service
Blade
Applicationserver
Claiminformation
service
Customerdata
ArchiSurance
Insurer
Customer db-tables
LAN
Submitclaim
Overview of Core Concepts
Business object
Data object
ArtifactSystemsoftware
Device Network
Infrastructureinterface
Applicationcomponent
Businessrole
Businessprocess
EventBusiness service
Applicationservice
Applicationfunction
Infrastructureservice
Applicationinterface
Businessinterface
Business
Application
Technology
Passivestructure
Behaviour Activestructure
triggering
flow
aggregation
assignment
access
realization
association
composition
ValueMeaning
use
Businessactor
Services as Binding Concept
Externalbusiness service
Internalbusiness service
Internalinfra. service
Externalinfra. service Technology
Application
Business
Customer
Externalapplication service
Internalapplication service
Example
ArchiSurance – Integrating an Insurance Company after a Merger
Business Functions
Insurer
MaintainingIntermediary
Relations
Contracting
FinancialHandling
ClaimsHandling
Claims
Insurancepolicies
Customer information
Money
MaintainingCustomerRelations
AssetManagement
Contracts
Productinformation
Customerinformation
Claims
Insuranceinformation
Insurancepremiums
Claimpayments
Insurancepolicies
Customerinformation
Productinformation
Claims
Money
Claiminformation
Intermediary
Customer
Customer’sBank
Product
Travel Insurance
Claimregistration
service
Customerinformation
service
Claimspaymentservice
Travel insurance policy
Insuranceapplication
service
Premiumpaymentservice
Customer data mutation
service
"be insured"(security)
Customer
Organisation
ArchiSurance
Back Office
Front Office
Home&
AwayCar
LegalAid
CustomerRelations
HRMProduct
DevelopmentFinance
IntermediaryRelations
Document Processing
SSC
Organisation & Business Functions
Finance
Home&
Away
Car LegalAid
Customer RelationsIntermediary Relations
MaintainingIntermediary
Relations
Contracting
FinancialHandling
Claims Handling
MaintainingCustomerRelations
AssetManagement
ApplicationsFront office
Legal Aid
CarHome & Away
Home & AwayPolicy
administration
Home & AwayFinancial
application
Car Insuranceapplication
Legal Aidbackoffice
system
Webportal
Call centerapplication
CRM application Legal AidCRM
MaintainingCustomer &
IntermediaryRelations
ClaimHandling
Contracting
DocumentProcessing
LiabilityInsurance
CarInsurance
TravelInsurance
HomeInsurance
Legal AidInsurance
Web portal
Call center application
Customer relationship management system
Home & AwayPolicy administration
Legal Aid back office
system
Legal AidCRM
Document management system
Home & AwayFinancial application
BusinessFunctions
Products
FinancialHandling
Car insurance application
Landscape map
Business Processes & Services
Claimregistration
service
Customerinformation
service
Claimspaymentservice
Customer
Handle ClaimClose Contract Collect PremiumInform Customer
Insuranceapplication
service
Premiumpaymentservice
Application Usage Handle Claim
Register PayValuateAccept
Home & AwayPolicy
administration
CRMapplication
Home & AwayFinancial
application
Customeradministration
service
Claimsadministration
service
Paymentservice
Printingservice
Scanningservice
Document management
system
Application Structure
Home & Away Policy administration
Risk Assessment
Policy data management
Customerdata access
Damage claim data Customer file dataInsurance policy data
Claim data management
Insurance requestdata
Infrastructure
ArchiSurance
Unix server farm
Mainframe
Intermediary
Adminserver
LAN
NAS File server
LANTCP/IPNetwork
Firewall Firewall
Unixserver
Unixserver
DBMS
MessageQueing
CICS
Deployment
Unix server farm
Home & AwayPolicy
administration
CRMapplication
Home & AwayFinancial
application
Document management
system
Mainframe
NASFile server
LAN
Firewall
Network
Call centerapplication
Web portalCar Insurance
application
Legal Aidbackoffice
system
Relation to Other Developments
Boundaries
Metadata
Method
Change
Principles
Realisation
Semantics
Strategy
Location
Businessdomains
Physicalresources
Time
ArchiMate
ArchiMate and UML/BPMN/…
• ArchiMate connects architectural domains
• Broader scope, but less detail than e.g. UML (software),
BPMN (processes)
• No replacement for these, but an ‘umbrella’ on top
• Several ArchiMate concepts derived from BPMN (esp.
business processes) and UML (esp. for application and
infrastructure)
• Easy to link to e.g. UML descriptions of detailed design or
BPMN process models
ArchiMate and Zachman
Scope = Planner’s view
Enterprise Model = Owner’s view
System Model= Designer’s view
Technology Model= Builder’s view
Detailed representation= Subcontractor’s view
Functioning Enterprise= User's view
WhyWho WhenWhereWhat How
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Business
Application
Technology
Str
uc
ture
Be
hav
iou
r
Info
rma
tio
n
Att
rib
ute
s
Na
tura
lla
ng
ua
ge
ArchiMate and The Open Group
ArchiMate and The Open Group
• ArchiMate now under the aegis of The Open Group
• Official ArchiMate 1.0 standard
• Original goal, a vendor-independent standard for
enterprise architecture modelling, is now a reality!• ArchiMate Forum within The Open Group
• responsible for standardisation, further development of the
language, PR, etc.
ArchiMate and TOGAF
• TOGAF: The Open Group Architecture Framework• Architecture Development Method (ADM) provides a way of
working
• Methodical support, but no description technique
• ArchiMate:• a description language
• but no prescribed way of working
• A perfect match!• People: ITAC• Delivery method: TOGAF• Description language: ArchiMate
TOGAF and ArchiMatePreliminary
DTechnologyArchitecture
RequirementsManagement
AArchitecture
VisionB
BusinessArchitecture
CInformation
SystemsArchitectures
HArchitecture
ChangeManagement
GImplementation
Governance
FMigrationPlanning E
Opportunitiesand
Solutions
Business
Application
Technology
TOGAF ADM ArchiMate
BusinessArchitecture
ApplicationArchitecture
DataArchitecture
TechnologyArchitecture
ArchiMate Usage in Practice
ArchiMate in Practice
• Applications at many organisations
• Banks, insurance companies,
government, etc.
• Consultants
• Ordina, Logica, Capgemini, Sogeti, Getronics, etc.
• Tools
• 5 certified tools, and some others
• Education
• Used by several universities and other educational institutes
• Active user group
• ArchiMate Forum of The Open Group
USERS
CONSULTING
& TOOLS
EDUCATION
Tool Support for ArchiMate
• Toolvendors:• BiZZdesign: Architect• IDS Scheer: ARIS ArchiMate Modeler• Casewise: Corporate Modeler• Telelogic (IBM): System Architect• Troux: Metis• (Agilense: EA Web Modeler)• (Avolution: Abacus)• (Promis: EVA Netmodeler)
• Microsoft Visio, Omnigraffle templates• downloadable from www.archimate.org • suitable for a first try, but no substitute for a ‘real’ tool
• Open source• Bolton University: http://archi.cetis.ac.uk/ (work in progress)
?
More Information?
Most ArchiMate results are available through the website:
www.archimate.org
See also The Open Group’s ArchiMate Forum:
www.opengroup.org/archimate
Marc Lankhorst
Novay
P.O. Box 589
7500 AN Enschede
The Netherlands
Marc [email protected]
053-4850456