Presentation is loading. Please wait.

Presentation is loading. Please wait.

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

Similar presentations

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

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

2 Contents Introducing ArchiXL Introducing architecture
Introducing TOGAF Principles for pragmatic architecture Essential TOGAF viewpoints Voor NIVI/KIRIA

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

7 Architecture fundamentals

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

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

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 Artefacts Preliminary Architecture Vision Business Architecture
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 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

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 TOGAF ArchiMate
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

26 Reusing best practices
Tip: separate your architecture into an organisation-specific an a generic part; the latter can be stored in the reference library 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 Functional decomposition diagram (business functions)
Primary business functions Maintain Provider Relations Customer Sales Claims Handling Asset Manegement Financial Handling Secondary business functions IT Development & Management Human Resource Management Facility Communications Controlling business functions Strategic Control Enterprise Architecture Quality Internal Reporting Product Development Marketing External Intermediary Legal Procurement Policy Administration Business Improvement

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

37 Impact of drivers/goals/objectives on business functions
Primary business functions Maintain Provider Relations Customer Sales Claims Handling Asset Manegement Financial Handling Secondary business functions IT Development & Management Human Resource Management Facility Communications Controlling business functions Strategic Control Enterprise Architecture Quality Internal Reporting Product Development Marketing External Intermediary Legal Procurement Policy Administration Business Improvement 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 Value chain diagram (roles and information flows)
Request for information, Customer/ Intermediary 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 Car Registration Central Bank Center Car information

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

40 Issues in application portfolio
Channels Front Office Back Office 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 1 2 Party Information Management Customer B2B Sales Process P & C Policy P & C Claims Portal Portal Support Administration Handling Multi Channel Contact Contract Health Policy Health Claims Routing Management Administration Administration Administration Handling 3 Interactive Voice Recognition Integrated Call Center Electronic Life Policy Life Claims Customer View Desktop Archive Administration Handling Business Input Output Data Warehouse Asset Intelligence & Management Management Management Reporting Supporting 4 Personnel Financial Facility Time Project Administration Administration Administration Registration Management Tip: plot issues on high-level business, application and technology views

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

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

Similar presentations

Ads by Google