Published on

Published in: Technology, Education
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • ABN AMRO en B/AC hebben aangegeven geinteresseerd te zijn. ABP is sceptisch maar wel geinteresseerd. RWS is al wel gecontact maar ArchiMate is nog niet gepresenteerd. UWV gaat per 1 januari van start, er zijn contacten mee.
  • bedoeld voor architecten modelleren van architecturen ICT en haar omgeving requirements ontwerpprincipes integratie van architecturen ihb tussen business- en ICT-architecturen consistentie van architecturen visualisatie van architecturen potentie van architecturen uitbuiten ontwerp en planning van nieuwbouw en veranderingen preventie en herstellen van systeemuitval communicatie ICT en business faciliteren what-if analyses mogelijk maken
  • To illustrate the value of the workbench an example is presented: An existing UML model and an existing Testbed model (Eertink et al., 1999) are integrated in an ArchiMate model. The UML model depicts a number of application components that are used by the imaginary insurance company ArchiSurance. The UML components are translated to ArchiMate components in a straightforward way. The Testbed model represents a number of process blocks that realise claim handling from registration to payment. This model is translated to ArchiMate concepts as well. Now, the workbench can be used to order the objects and define relations between them. In this case a layered architecture is created with services that are realised by components and provided to business processes. This results in a view relating business processes to IT components by means of service concepts. The following operations are applied in the creation of the integrated model: Translation: The interface offered by the Claims administration component is translated to the Claim information service. UML dependency relations are translated to ArchiMate use relations. Selection: Mainly processes and components are selected. Most interfaces, data items, business activities are left out. The Central administration component is left out. Extension: services offered by components to processes are added; concepts are grouped using ArchiMate grouping constructs.
  • To fully integrate a specific modelling language with the workbench, both a bottom-up and a top-down transformation are required between that language and the ArchiMate language. Due to the potentially different abstraction levels between a specific language and the ArchiMate language, a bottom-up transformation is likely to loose details and a top-down transformation is likely to be incomplete. In extreme cases a top-down transformation may only produce a template.
  • PPT

    1. 1. A Tool Integration Workbench for Enterprise Architecture Marc Lankhorst Open Group APC Conference Brussels, April 22, 2004
    2. 2. The ArchiMate project <ul><li>2 ½ years, July 2002 - December 2004 </li></ul><ul><li>approx. 35 man-years, 4 million euro </li></ul><ul><li>Consortium of Dutch companies and research institutes </li></ul><ul><ul><li>Telematica Instituut leads the project </li></ul></ul><ul><ul><li>Ideas also originated from Ordina </li></ul></ul><ul><ul><li>ABN AMRO, Dutch Tax Administration, ABP pension fund </li></ul></ul><ul><ul><li>Nijmegen University, CWI, Leiden University </li></ul></ul>
    3. 3. ArchiMate goals <ul><li>To describe architectures and their relations </li></ul><ul><li>Communicate architectures with all stakeholders </li></ul><ul><li>Judge the impact of changes </li></ul><ul><li>Realise architecture by relating to existing standards, techniques and tools </li></ul>
    4. 4. ArchiMate focus Analysis Integration Visualisation
    5. 5. Enterprise architecture: describing coherence Process architecture Application architecture Technical architecture Information architecture Product architecture ? ? ? ? ?
    6. 6. Current situation <ul><li>Large number of domain-specific modelling languages and tools in use (e.g. UML, workflow, BPMN, …) </li></ul><ul><li>Modelling languages not compatible: no relations between models from different domains </li></ul><ul><li>Modelling tools hardly integrated </li></ul><ul><li>Small number of tools available for enterprise architecture </li></ul><ul><li>Tools for enterprise architecture do not integrate well with existing languages and tools </li></ul>
    7. 7. ArchiMate Workbench goals <ul><li>A single infrastructure for </li></ul><ul><ul><li>creating multiple cross-domain views on an enterprise architecture by </li></ul></ul><ul><ul><li>integrating existing domain-specific models into the enterprise-level abstraction level </li></ul></ul>views models
    8. 8. Approach <ul><li>Starting point : reuse of existing models </li></ul><ul><li>Model integration : define relations between models in domain-specific languages, using the ArchiMate enterprise modelling language as an “umbrella” </li></ul><ul><li>Tool integration : develop a tool integration environment to link existing modelling tools </li></ul>
    9. 9. Model integration example Claims administration service Customer administration service Risk assessment service Payment service External application services Valuation Acceptance Registration Payment Formal claim Policy (contract) Claims administration Customer administ ration Risk assessment Financial application Central administration Registration Acceptance Valuation Payment Damage claiming process adapter Claims administr ation Customer adminstration Risk assessment Financial application Claim information service Application components and internal services adapter
    10. 10. Model integration options Direct relations: Via intermediate language:
    11. 11. Model integration architecture Tool/language-specific version of ArchiMate language
    12. 12. Tool integration options Direct: Tool bus:
    13. 13. Tool integration architecture
    14. 14. Use of the Workbench <ul><li>Select your viewpoint </li></ul><ul><li>Load domain-specific models </li></ul><ul><li>Integrate these models using ArchiMate concepts and relations </li></ul><ul><li>Open object in domain-specific tool </li></ul><ul><li>Refine object in domain-specific language </li></ul>
    15. 15. Load domain-specific model
    16. 16. Demo ArchiMate Workbench
    17. 23. Practical value (1) <ul><li>Case at Dutch Financial Institute (DFI) </li></ul>
    18. 24. Practical value (2)
    19. 25. Demo Visio View Explorer
    20. 44. What’s next? <ul><li>Integration of ArchiMate with other languages and tools </li></ul><ul><li>Using a MOF-repository for both the domain-specific models and the ArchiMate models </li></ul><ul><li>Development of an analysis prototype </li></ul><ul><li>Bringing together all prototypes in one environment </li></ul><ul><li>ArchiMate as a ‘top level’ for the Model Driven Architecture </li></ul>
    21. 45. Tool architecture
    22. 46. Introduction & adoption <ul><li>Validation in practice with ArchiMate business partners </li></ul><ul><li>Contacts with tool vendors on implementation in commercial tools </li></ul><ul><ul><li>IBM Rational, Select, Popkin, BiZZdesign, ASG, Adaptive </li></ul></ul><ul><li>Contacts with standardisation bodies </li></ul><ul><ul><li>Open Group </li></ul></ul><ul><ul><li>OMG </li></ul></ul>
    23. 47. More information? <ul><li>http://archimate.telin.nl </li></ul><ul><li>Marc Lankhorst </li></ul><ul><li>project manager ArchiMate </li></ul><ul><li>Telematica Instituut </li></ul><ul><li>Postbus 589 </li></ul><ul><li>7500 AN Enschede </li></ul><ul><li>The Netherlands </li></ul><ul><li>[email_address] </li></ul><ul><li>053-4850485 </li></ul>