Your SlideShare is downloading. ×
  • Like
  • Save
Delivering enterprise architecture
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Delivering enterprise architecture


This is the deck of a webinar that I presented at the OpenGroup. The focus of this webinar is on the challenge of using these standards in practice to build a strong architecture capability in …

This is the deck of a webinar that I presented at the OpenGroup. The focus of this webinar is on the challenge of using these standards in practice to build a strong architecture capability in organizations.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads


Total Views
On SlideShare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide
  • Stress the integrated part of the service offering: because we excel in the different service offerings AND because we understand our customers so well, we can give them what they need. Always. Also stress the brand story: building your business is our business. This links to tooling, but also consulting and training.
  • This slide sets the scene for the next two. When presenting this, stress the fact that there are many different definitions for both the “E” and the “A” part, that we (BiZZdesign) follow open standards and go from there.
  • Comes directly from the OG standard where “enterprise” is defined as “a collection of organizations with a common goal”.
  • Toronto (or any city in north America) illustrates the ISO/IEC definition nicely:Fundamental organization: gridPrinciple: easy navigation, easy to sell lots of ground (in the old days) because they are rectangularContrast that with a maze like Amsterdam where we all get lost. Is also a city (or: big village) but structure is very different, partly because of different design principles
  • This one comes from the handbook and has the advantage of combining “EA as product”, and “EA as something we do to get results”. Put this slide on, talk for a while and see how the audience reacts. It is less “technocratic” than the ANSI/ISO definition
  • The ArchiMate Framework is built on three layers: the business layer, the application layer, and the technology layer. This means that concepts of the language sit nicely in each of the layers. More structure is added by distinguishing between concepts that represent “things that show behavior” (active structure), behavior itself, and things that undergo behavior (passive structure). Lets look at some real concepts:In the business layer we see how actors perform roles in processes. Processes realize business services, which are the services we offer to our environment. Typical examples are the fact that customers can buy a bike, or insurance on that bike. The business object is the unit of information in this layer.In the application layer we see a similar structure. In the active sturcture column there are applications and interfaces, which model how to gain access to the behavior of these applications. Application functions whereas services are the behavior that applications offer to their environment: either other applications or to the business layer.The same pattern can also be observed in the infrastructure layer where logical nodes have both internal behavior, modelled by functions, and external behavior, modeled by services.All in all there is a lot of symmetry between the layers, as can be seen by looking at the relations. A full explanation is beyond the scope of this presentation, but at least note that the same relation type is used each time when crossing from active structure to behavior and to passive structure.


  • 1. Delivering Enterprise Architecture with TOGAF® and ArchiMate® Dr. Bas van Gils
  • 2. Bas van Gils +31-(0)6-484 320 88 2
  • 3. Integrated service offering Enterprise Business Business Business Architecture Modeling Process Requirements Management Management ManagementConsulting servicesToolingTrainingBest practices 3
  • 4. Clients and offices worldwide• Netherlands: Amersfoort, Enschede• North America: Toronto, Boston• Belgium: Leuven• UK: London• Germany: Dusseldorf• France: Paris
  • 5. Agenda Introduction: TOGAF and ArchiMate The challenge for EA Tips and best practices for success More information 5
  • 6. Introducing EA 6
  • 7. Enterprise definition © OpenGroup 7
  • 8. Architecture definitonThe Architecture (of a system) is the fundamental organizationof that system embodied in its components, their relationships to each other, and to the environment, and the principles guiding its design and evolution. ISO/IEC 42010:2007 More simply put: structure with a vision 8
  • 9. Enterprise Architecture EA is a conceptual tool that helps organizations get a deeper understanding of their own structure and of the way they work. It provides a map of the enterprise and it is a “route planner” for business and technology change. Important uses of it are in systematic IT planning/ architecting and in enhanced analysis and support for decision-making. handbook enterprise architecture, BiZZdesign, 2012 9
  • 10. Ingredients of an EA frameworkTOGAF ArchiMate View- Process points Language Repository, Reference Models 10
  • 11. The TOGAF components 11
  • 12. ArchiMate core 12
  • 13. ArchiMate + TOGAF 13
  • 14. In many organizations, EA is still considered to bean IT discipline rather than a strategic partner todeliver business value 14
  • 15. Online trends 15
  • 16. Keywords for “enterprise architecture” 16
  • 17. The good news There appears to be increased attention for EA at the strategic / business level of organizations. This will have a positive effect on EA investment over the next few years 17
  • 18. Implications• Rule #1 for EA: focus on adding value• Rule #2 for EA: be prepared• Fact: not following #1 and #2 will crush your reputation• Corollary: work with the business, not for the business 18
  • 19. The next step to success (see also: for our blogpost series on this topic) 19
  • 20. Where to start, what to do • Establish an AB with business executives that sets goals and KPI’s for the architecture capability. Be accountable! Aim • Make sure the goals for EA align with corporate goals and embed in e.g. project management, governance etc. • Build a mixed team in terms of background (business /Establish IT), experience (senior / junior) and focus (strategy / execution) • Plan to get your hands dirty! • The proof of the pudding is in the eating: focus on execution • Mind your communication and balance principles, models, andExecute other visuals • Claim your successes, and grow the EA practice 20
  • 21. Setting• IT department of a large telecom organization in North America• TOGAF’s ADM is to support the solution process• The solution process is mostly based on waterfall principles• Key question: how do we add value to this process with TOGAF? 21
  • 22. Design the interaction 22
  • 23. … and at the same time …While designing the “service oriented engagement model”:• We worked with the team to specify what type of models would best support the organization I with respect to each of the services• These functional questions were translated to ArchiMate models (viewpoints)• A customized metamodel was built, tailored to the specific needs of this organization 23
  • 24. Setting• Large (Dutch) organization in the social security sector• A few years ago: on the verge of large enterprise transformation• Use ArchiMate to investigate the impact of this transformation• Challenge: simplify the metamodel for use in the architecture team and improve enterprise-wide communication about architecture 24
  • 25. Product Value Contract Business Business BusinessRepresentation service interface collaboration Event Business object Business process / Business Business function / role actor interactionBusinessApplication Application Application Application service interface collaboration Data object Application Application function / component interactionApplicationInfrastructure Infrastructure Infrastructure service interface Communication Artifact Node path System Device Network software 25
  • 26. Simplified metamodel 26
  • 27. Added value of TOGAF and ArchiMate• TOGAF is designed to be used in many different situations: – Tailor it to your needs – Major focus on getting results – Many guidelines and techniques that will help you be successful• ArchiMate has built-in capabilities for cross-domain modeling, analysis as well as advanced visualizations for various stakeholders• Both open standards: – Work well for incremental adoption – Are supported with tools, including BiZZdesign Architect – Have an extensive track record in practice 27
  • 28. More information LinkedIn groups• Anything Enterprise Architecture • TOGAF series• ArchiMate • Architecture standards• TOGAF for Architecture • ArchiMate series• Global Enterprise Architecture Forum • Roadmap to success• Downloadable versions of the full • specifications of ArchiMate and TOGAF •• Many whitepapers, and recorded • webinars 28
  • 29. Interested in the slides?Go to and select “webinars" 29
  • 30. © 2012, BiZZdesign. All rights reserved.BiZZdesign and BiZZdesign logos are registered trademarks of BiZZdesign Company. 30