A Tool Integration Workbench for Enterprise Architecture

1
A Tool Integration Workbench for Enterprise
Architecture

• Marc Lankhorst
• Open Group APC Conference
• Brussels, April 22, 2004

2
The ArchiMate project

• 2½ years, July 2002 - December 2004
• approx. 35 man-years, 4 million euro
• Consortium of Dutch companies and research
  institutes
• Telematica Instituut leads the project
• Ideas also originated from Ordina
• ABN AMRO, Dutch Tax Administration, ABP pension
  fund
• Nijmegen University, CWI, Leiden University

3
ArchiMate goals

• To describe architectures and their relations
• Communicate architectures with all stakeholders
• Judge the impact of changes
• Realise architecture by relating to existing
  standards, techniques and tools

4
ArchiMate focus
5
Enterprise architecture describing coherence
6
Current situation

• Large number of domain-specific modelling
  languages and tools in use (e.g. UML, workflow,
  BPMN, )
• Modelling languages not compatible no relations
  between models from different domains
• Modelling tools hardly integrated
• Small number of tools available for enterprise
  architecture
• Tools for enterprise architecture do not
  integrate well with existing languages and tools

7
ArchiMate Workbench goals
views

• A single infrastructure for
• creating multiple cross-domain views on an
  enterprise architecture by
• integrating existing domain-specific models into
  the enterprise-level abstraction level

models
8
Approach

• Starting point reuse of existing models
• Model integration define relations between
  models in domain-specific languages, using the
  ArchiMate enterprise modelling language as an
  umbrella
• Tool integration develop a tool integration
  environment to link existing modelling tools

9
Model integration example



10
Model integration options
Direct relations
11
Model integration architecture
Tool/language-specific version of ArchiMate
language
12
Tool integration options
13
Tool integration architecture
14
Use of the Workbench

1. Select your viewpoint
2. Load domain-specific models
3. Integrate these models using ArchiMate concepts
   and relations
4. Open object in domain-specific tool
5. Refine object in domain-specific language

15
Load domain-specific model
16
Demo

• ArchiMate Workbench

17
(No Transcript)
18
(No Transcript)
19
(No Transcript)
20
(No Transcript)
21
(No Transcript)
22
(No Transcript)
23
Practical value (1)

• Case at Dutch Financial Institute (DFI)

24
Practical value (2)
25
Demo

• Visio View Explorer

26
(No Transcript)
27
(No Transcript)
28
(No Transcript)
29
(No Transcript)
30
(No Transcript)
31
(No Transcript)
32
(No Transcript)
33
(No Transcript)
34
(No Transcript)
35
(No Transcript)
36
(No Transcript)
37
(No Transcript)
38
(No Transcript)
39
(No Transcript)
40
(No Transcript)
41
(No Transcript)
42
(No Transcript)
43
(No Transcript)
44
Whats next?

• Integration of ArchiMate with other languages and
  tools
• Using a MOF-repository for both the
  domain-specific models and the ArchiMate models
• Development of an analysis prototype
• Bringing together all prototypes in one
  environment
• ArchiMate as a top level for the Model Driven
  Architecture

45
Tool architecture
46
Introduction adoption

• Validation in practice with ArchiMate business
  partners
• Contacts with tool vendors on implementation in
  commercial tools
• IBM Rational, Select, Popkin, BiZZdesign, ASG,
  Adaptive
• Contacts with standardisation bodies
• Open Group
• OMG

47
More information?

• http//archimate.telin.nl
• Marc Lankhorst
• project manager ArchiMate
• Telematica Instituut
• Postbus 589
• 7500 AN Enschede
• The Netherlands
• Marc.Lankhorst_at_telin.nl
• 053-4850485