Using TOGAF as a pragmatic approach to architecture 15 april 2009 Jaarbeurs, Utrecht KIVI NIRIA, afd. Informatica

1. Using TOGAF as a pragmatic approach to architecture15 april 2009Jaarbeurs, UtrechtKIVI NIRIA, afd. Informatica Danny Greefhorst dgreefhorst@archixl.nl

2. Contents • Introducing ArchiXL • Introducing architecture • Introducing TOGAF • Principles for pragmatic architecture • Essential TOGAF viewpoints

3. ArchiXL • IT-architecture consulting firm, founded in 2008 • Based in Amersfoort, the Netherlands • Focus on financial and public sector • Knowledge areas: • IT architecture (BPM, EAI/SOA, ECM, IDM, BI, Portals) • Enterprise architecture methods and techniques (TOGAF, ArchiMate) • Sector knowledge (insurance, municipalities, education)

4. What is architecture? “The fundamental organization of a system embodied in its components, their relationships to each other, and to the environment, and the principles guiding its design and evolution” IEEE 1471

5. Why practice architecture? • Architecture helps in optimising the service portfolio of an organisation, aligning IT supply to business demand • Architecture contributes to a healthy project portfolio, ensuring that projects that contibute most to the long term vision will be realised • Architecture improves the quality of individual solutions, simplifying their development and maintenance en prolonging their life time

6. Purchased Packages Legacy Applications E-Marketplaces HTTP/XML Autonomous Divisions Message queue Down- load file FTP Screen scrape Screen scrape Down- load file Trans- action file Trans- action file CICS gateway Sockets RPC ORB Gateway E-mail Message queue Applications in Trading Partners SMTP Trans- action file Trans- action file Message queue CICS gateway XML/ HTTP Browser Down- load file End-User Development Outsourced and ASP Applications Message APPC Applications From Mergers and Acquisitions What does an organisation without architecture look like?

7. Architecture fundamentals

8. abstractions DATA What FUNCTION How NETWORK Where PEOPLE Who MOTIVATION Why TIME When perspectives List of Things - Important to the Business List of Processes - the Business Performs List of Organizations - Important to the Business List of Events - Significant to the Business List of Business Goals and Strategies List of Locations - in which the Business Operates SCOPE Planner contextual Entity = Class of Business Thing Function = Class of Business Process Node = Major Business Location People = Class of People and Major Organizations Ends/Means=Major Business Goal/Critical Success Factor Time = Major Business Event e.g., Logistics Network e.g., Semantic Model e.g., Business Process Model e.g., Work Flow Model e.g., Master Schedule e.g., Business Plan ENTERPRISE MODEL Owner Process = Business Process I/O = Business Resources conceptual Entity = Business Entity Rel. = Business Relationship Node = Business Location Link = Business Linkage People = Organization Unit Work = Work Product Time = Business Event Cycle = Business Cycle End = Business Objective Means = Business Strategy e.g., Application Architecture e.g., Logical Data Model e.g., Distributed System Architecture e.g., Human Interface Architecture e.g., Processing Structure e.g., Business Rule Model SYSTEM MODEL Designer logical Time = System Event Cycle = Processing Cycle Entity = Data Entity Rel. = Data Relationship Process.= Application Function I/O = User Views Node = IS Function Link = Line Characteristics People = Role Work = Deliverable End = Structural Assertion Means =Action Assertion e.g., Physical Data Model e.g., System Design e.g., Technical Architecture e.g., Presentation Architecture e.g., Control Structure e.g., Rule Design TECHNOLOGY CONSTRAINED MODEL Builder Node = Hardware/System Software Link = Line Specifications physical Time = Execute Cycle = Component Cycle People = User Work = Screen/Device Format End = Condition Means = Action Entity = Tables/Segments/etc. Rel. = Key/Pointer/etc. Process= Computer Function I/O =Data Elements/Sets e.g. Network Architecture e.g. Security Architecture e.g. Timing Definition e.g. Rule Specification e.g. Data Definition e.g. Program DETAILED REPRESEN- TATIONS Subcontractor out-of-context Node = Addresses Link = Protocols People = Identity Work = Job Time = Interrupt Cycle = Machine Cycle End = Sub-condition Means = Step Entity = Field Rel. = Address Process= Language Statement I/O = Control Block FUNCTIONING ENTERPRISE DATA Implementation FUNCTION Implementation NETWORK Implementation ORGANIZATION Implementation SCHEDULE Implementation STRATEGY Implementation The origin: Zachman framework

9. Represen - Business Business tation service collaboration Business interaction Event Business Business Business Business object process role actor Application Application interface service Data Application Application object component function Infrastructure Infrastructure service interface System Artifact Device Network software ArchiMate Business Application Technology Passieve structuur Gedrag Actieve structuur

10. TOGAF Overview PART I: Introduction PART II: Architecture Development Method PART III: ADM Guidelines and Techniques PART IV: Architecture Content Framework PART V: Enterprise Continuum & Tools PART VI: TOGAF Reference Models PART VII: Architecture Capability Framework

11. What’s new in TOGAF 9? • Modular Structure - The specification content is structured in a modular way, which allows for the concepts in each part to be developed with limited impacts on other parts. • Content Framework - Provides a detailed model of architectural work products, including deliverables, artifacts within deliverables, and the architectural building blocks that artifacts represent. • Extended Guidance on Adopting TOGAF within an Enterprise - An extended set of concepts and guidelines to support the establishment of an integrated hierarchy of architectures • ADM Guidelines & Techniques - Show in more detail how the ADM can be applied to specific situations. • Additional ADM Detail - More detailed information supporting the execution of the ADM. • TOGAF Document Categorization Model - Structures the release management of the TOGAF specification. • .

12. Architecture Development Method

13. Classes of Enterprise Architecture Engagement

14. Business Transformation Readiness Assessment Steps • Determine the readiness factors that will impact the organization • Present the readiness factors using maturity models • Assess the readiness factors, including determination of readiness factor ratings • Assess the risks for each readiness factor and identify improvement actions to mitigate the risk • Work these actions into Phase E and F Implementation and Migration Plan Factors • Vision • Desire, Willingness, and Resolve • Need • Business Case • Funding • Sponsorship and Leadership • Governance • Accountability • Workable Approach and Execution Model • IT Capacity to Execute • Enterprise Capacity to Execute • Enterprise Ability to Implement and Operate

15. Capability-Based Planning

16. Content framework

17. Building blocks

18. Preliminary Principles Catalog Architecture Vision Stakeholder Map Matrix Value Chain Diagram Solution Concept Diagram Business Architecture Organization/Actor Catalog Role Catalog Business Service/Function Catalog Business Interaction Matrix Actor/Role Matrix Business Footpr int Diagram Business Service/Infor mation Diagram Functional Decomposition Diagram Product Lifecycle Diagram Data Architecture Data Entity/Data Component Catalog Data Entity/Business Function Matrix System/Data Matrix Class Diagram Data Dissemination Diagram Application Architecture Application Portfolio Catalog Interface Catalog System/Organization Matrix Role/System Matrix System/Function Matrix Application Interaction Matrix Application Communication Diagram Application and User Location Diagram System Use-Case Diagram Technology Architecture Technology Standards Catalog Technology Por tfolio Catalog System/Technology Matrix Environments and Locations Diagram Platform Decomposition Diagram Opportunities and Solutions Project Context Diagram Benefits Diagram Requirements Management Requirements Catalog Artefacts

19. Architecture Building Blocks Architecture Contract Architecture Definition Document Architecture Principles Architecture Repository Architecture Requirements Architecture Roadmap Architecture Vision Business Principles, Business Preliminary Goals, and Business Drivers Capability Assessment Change Request Communications Plan Compliance Assessment Implementation and Migration Plan Implementation Governance Model Organizational Model for Enterprise Architecture Request for Architecture Work Requirements Impact Assessment Solution Building Blocks Statement of Architecture Work Tailored Architecture Framework Transition Architecture Deliverables

20. Enterprise continuum

21. Reference architecture classification

22. Organisation architecture classification

23. TOGAF 9 Certification • TOGAF 9 Foundation (level 1) • To provide validation that the Candidate has gained knowledge of the terminology, structure, and basic concepts of TOGAF 9, and understands the core principles of Enterprise Architecture and TOGAF. The learning objectives at this level focus on knowledge and comprehension. • TOGAF 9 Certified (level 2) • To provide validation that in addition to the knowledge and comprehension of TOGAF 9 Foundation, the Candidate is able to analyze and apply this knowledge. The learning objectives at this level therefore focus on application and analysis in addition to knowledge and comprehension. • Bridge from TOGAF 8 to TOGAF 9 Certified • To enable individuals who are TOGAF 8 Certified to obtain TOGAF 9 Certified (level 2) certification. The bridging option exists to recognize the existing investment in TOGAF certification for individuals who have achieved the TOGAF 8 Certified qualification.

24. Principles for pragmatic architecture • Use of open standards • Reusing best-practices • Iterative approach • Concrete and usable results • Responsibility for result • Close interaction with stakeholders • “just-enough” architecture • Focus on knowledge, not on rule enforcement

25. Use of open standards Tip: use formalised models for architects and engineers, use simple powerpoint models for management and users Key message: standards are a good starting point, but use them wisely TOGAF ArchiMate

26. Tip: separate your architecture into an organisation-specific an a generic part; the latter can be stored in the reference library Reusing best practices Key message: reuse reference architectures in the market, and make your own

27. Iterative approach Tip: make a plan for defining your architecture with clear milestones and a deadline Key message: deliver fast, deliver often and make sure every delivery provides added value

28. Concrete and usable results Tip: show your sponsor examples of previous architecture deliverables to let him understand what he will get Key message: be clear on what you deliver, and focus on the goals and requirements

29. Responsibility for result The Lead Enterprise Architect is responsible for ensuring that the architecture is technically coherent and future-proof. Tip: plan your involvement in the implementation for at least one day in the week Key message: do not run away after creating the architecture, guide the implementation

30. Close interaction with stakeholders Tip: don’t forget to have your architecture reviewed by other architects Tip: reserve time with the people that have the knowledge; they can provide you with the information you really need Key message: talk to all key stakeholders, bring them together in workshops to get consensus

31. “just-enough” architecture Tip: first deliver a high-level architecture with only the goals, guiding architecture principles, high-level diagrams, and major changes Tip: deliver more detailed architectures for specific themes that require business attention Key message: do not overdeliver; focus on the 20% artefacts that deliver 80% of the value

32. Focus on knowledge, not on rule enforcement Tip: look at the intent of principles and guidelines and not so much at their formulation Tip: deviating from principles and guidelines can be justified if there is a really good motivation Key message: architects provide value through skills and knowledge, but they don’t know everything

33. Where is the essence?

34. Principle: corporate information is stored only once and retrieved from the source when needed Motivation • Duplication of information leads to inconsistencies • Inconsistencies lead to errors in business processes and/or additional effort in reconciling these inconsistencies Implications • Information that is needed throughout the enterprise is stored in a single information providing application • Information providing applications expose their information through a number of generic application services • Information providing applications are high available (>99,9%) Tip: reuse existing architecture principles in TOGAF and reference architectures Tip: interactively define architecture principles with the stakeholders using powerpoint 34

35. Controlling business functions Enterprise Quality Internal External Strategic Control Architecture Management Reporting Reporting Primary business functions Product Policy Marketing Sales Claims Handling Development Administration Maintain Maintain Maintain Financial Asset Customer Intermediary Provider Handling Manegement Relations Relations Relations Secondary business functions Human IT Development Financial Facility Resource Communications & Management Management Management Management Business Legal Procurement Improvement Functional decomposition diagram (business functions)

36. System/function matrix Primary business functions Product Marketing Sales Policy Claims Handling Administration Development Financial Maintain Maintain Maintain Asset Handling Customer Intermediary Provider Management Relations Relations Relations DataWarehouse P & C Claims Sales Process Contact Administration Handling Support Business Health Claims Contract P & C Policy Intelligence & Handling Administration Administration Reporting Integrated Life Claims Health Policy Customer View Administration Handling Life Policy Administration Asset B2B B2B Customer Financial Management Portal Portal Portal Administration Party Information Management Party Information Management Call Center Desktop Party Information Management 36

37. Controlling business functions Enterprise Quality Internal External Strategic Control Architecture Management Reporting Reporting Primary business functions Product Policy Marketing Sales Claims Handling Development Administration Maintain Maintain Maintain Financial Asset Customer Intermediary Provider Handling Manegement Relations Relations Relations Secondary business functions Human IT Development Financial Facility Resource Communications & Management Management Management Management Business Legal Procurement Improvement Impact of drivers/goals/objectives on business functions • Impact of new customer group: • Introduce new products for that group • Change marketing approach • Change sales process for new customer group and new products • Change policy administration for new products 1 2 3 4 Tip: determine impact of drivers/goals/objectives on high-level business, application and technology views

38. Customer/ Intermediary Value chain diagram (roles and information flows) Request for information, policy acceptance, policy changes Request for indemnification Indemnification Foundation Product information, policy, invoice Indemnification approval or rejection Claim Request for legal report Customer/ Legal Report Intermediary Center Claim rejection, claim acceptance Legal report Damage assessment order Request information, report fraud Insurance Fraud Damage Expert Insurer Registration Damage report Fraud information Indemnation payments, premium collections Repair order Damage Repair Bank Invoice Account statements Car information request Regulatory report Central Bank Car Registration Center Car information

39. Channels Front Office Back Office Customer Sales Process Party Information P & C Policy Portal Support Management Administration Contact Contract Health Policy Administration Administration Administration Call Center Interactive Voice Electronic Integrated Life Policy Desktop Recognition Archive Customer View Administration Input Output Management Management Supporting Personnel Financial Administration Administration Application portfolio catalog (application components) B2B P & C Claims Portal Handling Multi Channel E-mail Health Claims Routing Management Handling Life Claims Handling Business Asset Intelligence & Data Warehouse Management Reporting Facility Time Project E-mail Administration Registration Management

40. Issues in application portfolio • Security in customer portal is not in line with security policy • Prolonging of policies does not fit into batch window • Integrated customer view does not include life information • Maintenance costs of personnel administration are too high Channels Front Office Back Office 1 2 PartyInformationManagement Customer B2B Sales Process P & C Policy P & C Claims Portal Portal Support Administration Handling Multi Channel E-mail Contact Contract Health Policy Health Claims Routing Management Administration Administration Administration Handling 3 InteractiveVoiceRecognition Integrated Call Center Electronic Life Policy Life Claims CustomerView Desktop Archive Administration Handling Business DataWarehouse Input Output Asset Intelligence & Management Management Management Reporting Supporting 4 Personnel Financial Facility Time Project E-mail Administration Administration Administration Registration Management Tip: plot issues on high-level business, application and technology views

41. Application communication diagram Business Intelligence & Data Warehouse Reporting Customer Party Information P & C Policy P & C Claims Portal Management Administration Handling Customer/ Intermediary Customer/ Intermediary CentralBank Bank Contact Administration Financial Administration Output Management Tip: draw application communication diagrams for specific change areas regulatoryreport financial transactions policy customer financial transaction indemnification claim indemnification claim document financial transaction contact contact Electronic Archive financial transaction 41

42. Technology standards catalog (system software) Office Productivity Collaboration Communication Microsoft Office Microsoft Exchange Microsoft Office Communications Server Adobe Reader Microsoft Office Sharepoint Server Microsoft Windows Live Messenger User Interface Business Process Management Content Management Microsoft Office Sharepoint Server K2.NET Microsoft Office Sharepoint Server Microsoft Search Server Microsoft BizTalk Server Kofax Ascent Capture Oracle Portal Oracle Workflow Transaction Processing Data Interchange Data Management Microsoft .NET Microsoft BizTalk Server Microsoft SQL Server Microsoft Commerce Server Microsoft MSMQ Oracle DB Oracle Application Server Oracle Advanced Queueing System and Network Management Security Software Engineering Microsoft System Center Microsoft Active Directory Microsoft Visual Studio Oracle Grid Control Microsoft ISA Server Oracle Developer Oracle Internet Directory Operating System Microsoft Windows Vista Microsoft Windows Server

43. Questions