Presentation is loading. Please wait.

Presentation is loading. Please wait.

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

Similar presentations


Presentation on theme: "Using TOGAF as a pragmatic approach to architecture 15 april 2009 Jaarbeurs, Utrecht KIVI NIRIA, afd. Informatica Danny Greefhorst"— Presentation transcript:

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

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

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) 3

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

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 5

6 What does an organisation without architecture look like? 6

7 Architecture fundamentals Slide 7

8 Slide 8 The origin: Zachman framework

9 ArchiMate Business Application Technology Passieve structuurGedragActieve structuur Device System software Infrastructure service ArtifactNetwork Infrastructure interface Application component Application function Application service Data object Application interface Business actor Business role Business process Business service Business object Event Represen- tation Business interaction Business collaboration 9

10 TOGAF Overview Slide 10 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 12

13 Classes of Enterprise Architecture Engagement Slide 13

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 Slide 14

15 Capability-Based Planning Slide 15

16 Content framework Slide 16

17 Building blocks 17

18 18 Artefacts 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

19 Slide 19 Deliverables 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

20 Enterprise continuum 20

21 Reference architecture classification 21

22 Organisation architecture classification 22

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. 23

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 24

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

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

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

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

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

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

31 “just-enough” architecture 31 Key message: do not overdeliver; focus on the 20% artefacts that deliver 80% of the value 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

32 Focus on knowledge, not on rule enforcement 32 Key message: architects provide value through skills and knowledge, but they don’t know everything 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

33 Where is the essence? 33

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%) 34 Tip: interactively define architecture principles with the stakeholders using powerpoint Tip: reuse existing architecture principles in TOGAF and reference architectures

35 Functional decomposition diagram (business functions) 35

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

37 Impact of drivers/goals/objectives on business functions 37 Impact of new customer group: 1.Introduce new products for that group 2.Change marketing approach 3.Change sales process for new customer group and new products 4.Change policy administration for new products Impact of new customer group: 1.Introduce new products for that group 2.Change marketing approach 3.Change sales process for new customer group and new products 4.Change policy administration for new products 1 1 Tip: determine impact of drivers/goals/objectives on high-level business, application and technology views

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

39 Application portfolio catalog (application components) 39 Project Management Time Registration Data Warehouse B2B Portal Multi Channel Routing Management Asset Management Business Intelligence & Reporting P & C Claims Handling Health Claims Handling Life Claims Handling Facility Administration

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

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

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

43 Questions


Download ppt "Using TOGAF as a pragmatic approach to architecture 15 april 2009 Jaarbeurs, Utrecht KIVI NIRIA, afd. Informatica Danny Greefhorst"

Similar presentations


Ads by Google