1 / 42

White Paper Integrated Architecture Framework

White Paper Integrated Architecture Framework. Version 1.0 16-12-99. Author: Hans Goedvolk Editor-in-chief: Daan Rijsenbrij. Why IAF Role, Objectives, Benefits Overview of IAF The Framework The ICT enabled Enterprise Four Architecture Areas Five Design Phases Special Viewpoints

valentine-maldonado
Télécharger la présentation

White Paper Integrated Architecture Framework

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. White PaperIntegrated Architecture Framework Version 1.0 16-12-99 Author: Hans Goedvolk Editor-in-chief: Daan Rijsenbrij

  2. Why IAF Role, Objectives, Benefits Overview of IAF The Framework The ICT enabled Enterprise Four Architecture Areas Five Design Phases Special Viewpoints Alignment and Relations within IAF Existing and New Systems Design Levels Example of Enterprise-level Design Relation of IAF with: Business and ICT Transformation the Spiral Approach Professional Roles Reference Architectures Methods and Tools Current AD* Methods Next Version Contents

  3. Why anIntegrated Architecture Framework?

  4. The ICT enabled Enterprise • Integration of Information and Communication Technology • Business Processes and ICT Systems become strongly Intertwined • New Business Models: E-Business, Customer-oriented, Supply Chain Management • Future is Complex ICT enabled Enterprises with Agile and Adaptive Character

  5. The Role of the Integrated Architecture Framework Business As Is Architectural Design Development,Change Operation, Maintenance Vision, Strategy Business Vision Integrated Architecture Framework Business and ICT Transformation ICT enabled Enterprise ICT Vision ICT As Is

  6. Objectives of IAF andIntegrated Architectural Design • Business and ICT Strategy Enabling • Alignment of Business and ICT regarding • Objectives • Services • Structure and Operation • Qualities • Transformation and Migration Process • Investment • Decision Support for Stakeholders • Communication Tool • Risk Management of Transformation • Mastering of Complexity

  7. The Benefits of IAF andIntegrated Architectural Design Non-Quantified Quantified • Long term Financial Planning • Lower Cost • Risk Reduction • Disaster Avoidance • Efficiency • Increased Revenue • Reduced Time-to-Market • New Business Models Better Alignment Business and ICT Concurrent Transformation Business and ICT Agile and Adaptive Business and ICT Holistic view, no sub-optimisation Provide Framework for Innovation Establish Common Views Consistency Financial Life-cycle Extension Less Failures Reduced Risk (e.g Security) Non-Financial

  8. Overview of the Integrated Architecture Framework

  9. Integrated Architecture Framework (IAF) Special Viewpoints Design Phases Contextual Vision, Scope, Environment Business Information Information Systems Technology Infrastructure Conceptual Products, Services Logical Functions, Co-operation Physical People, Components Transformational Transformation, Evolution Main Architecture Areas

  10. The ICT enabled Enterprise Business Processes Collaboration of Human Beings business products, services Business System information services External Relations Information Provision Collaboration of Human Beings information services IS services Information Systems Co-operation of SW Components ICT System External ICT Systems TI services Technology Infrastructure Co-operation of SW&HW Components

  11. Business Architecture External Stakeholders Business System Governance Roles Management, Control Rules Feedback Customers products, services Core Roles Supply Chain products, services Suppliers resources, services Supportive Roles Resource Management, Development resources, services Suppliers

  12. Information Architecture Roles in Business Architecture Information Provider Information User Information Provision facts, rules, best practices information, knowledge External User External Provider Information Manager Information Memory

  13. Information Systems Architecture Business Roles Information Roles External Relation Information Systems IS services IS services IS services Information System Functions External IS Electronic Data

  14. Technology Infrastructure Architecture Users in Business & Information Roles IS Components External User External IS Technology Infrastructure Human/ Computer Interfaces Control, Processing, Transmission, Storage Capabilities Interface Capabilities Technology Infrastructure Functions External TI

  15. The Design Phases Why? About What? Contextual Mission/Strategy/Scope/ Environment/ Stakeholders/Concerns Conceptual Products/Services/Requirements What does the system produce for Whom? External (Black-box) Viewpoint How does the system work? Logical Roles/Collaboration/Structure Internal (White-box) Viewpoint Who or What performs the roles? Physical Components (People, Software, Hardware) Transformational Development, Implementation, Evolution Life Cycle Viewpoint How to realise and maintain the system?

  16. ContextualPhase Influences Political Social Economic External Relations Other Relations System Customers Suppliers Scope? Mission? Strategy? Stakeholders? Technological Scientific Commercial

  17. ConceptualPhase External Relations Products/ Services/ Channels System Requirements? Constraints?

  18. LogicalPhase External Relations System Human Role/ Information Human Role/ Information IS Function/ Data IS Function/ Data TI Function TI Function Collaboration of Roles, Co-operation of Functions, Structure of Information/Data (Logical Components)

  19. PhysicalPhase External Relations System Human Role/ Information Human Role/ Information IS Function/ Data IS Function/ Data TI Functions TI Functions Assign People to Roles and Software/Hardware to Functions (Physical Components)

  20. Call Centre Package Call Centre Package Process Management IS Back Office Product A IS Distribution Channel Management IS Process Management IS Product A IS Internet Applications (Web-server) CRM IS Product B IS Product B IS Kiosk Application Value Added Services IS Third Party IS ATM Management IS ATM Application ATM Application Call Centre Package Distribution Channel Management IS Process Management IS Product A IS Internet Applications (Web-server) CRM IS Product B IS ATM Application TransformationalPhase Stage 1 Stage 3 Stage 2

  21. Special Viewpoints in IAF Governance Security Business and ICT System Contextual Conceptual Logical Physical Transformational Information Information Systems Technology Infrastructure Business

  22. Strategic Alignment betweenMain Architecture Areas Business Information Information Systems Technology Infrastructure Contextual Strategic Alignment Conceptual Products/ Services Information Services IS Services TI Services Information Enabling IS Enabling TI Enabling Logical Business Roles Information Roles IS Functions TI Functions

  23. Relation between Business and Information Business Information Mission, Strategy, Environment Mission, Strategy, Environment Align Requirements Services & Products Information Services Information Needs? Business Roles & Collaboration Information Roles & Collaboration Enabling People (Competencies) People (Competencies) Constraints Stages in Transformation Stages in Transformation Synchronise

  24. Relation between Business/Informationand ICT Systems Business & Information ICT System Mission, Strategy, Environment Mission, Strategy, Environment Align Requirements Services & Products IS +TI Services Y Roles & Collaboration Functions & Mechanisms Automate? Enabling N People (Competencies) ICT Components (Capabilities) Constraints Stages in Transformation Stages in Implementation Synchronise

  25. Relation between Information Systemsand Technology Infrastructure Information Systems Technology Infrastructure Mission, Strategy, Environment Mission, Strategy, Environment Align Requirements IS Services TI Services TI Capabilities? Functions & Mechanisms Functions & Mechanisms Enabling IS Components (Capabilities) TI Components (Capabilities) Constraints Stages in Implementation Stages in Implementation Synchronise

  26. Existing and New Systems Contextual Mission, Strategy, Environment Conceptual Re-architecting Products/Services Architecting New Products/Services Logical Re-architecting Existing System Architecting New System Physical Existing System Architecting People, Components Transformational Stage 0 Intermediate Stages Final Stage

  27. Design Levels:Enterprise, Project and Detailed City Design Zoning Plan Area Design Area Plan Building Design Exterior Design

  28. Relation betweenSystem and Subsystem Architecture System Architecture Subsystem Architecture Mission, Strategy, Environment Mission, Strategy, Environment Constraints Requirements System Products/Services Subsystem Products/Services Role of Subsystem Roles & Collaboration Roles & Collaboration Realisation Subsystems People, Components Constraints Stages Transformation Time of Implementation Determines

  29. Example of IAFat Enterprise Level Role Models in the Logical Phase

  30. Business Roles in a Virtual Bank General Management Risk Management Co-ordination Production Communication Customers Channels Mid-Office Back-Office/ Third Parties Call Centre Marketing Product Management Back Office Product A Internet Sales Contract Management Back Office Product B ATM Channel Management Customer Management Transaction Management Kiosk Third Party Product Service Desk Third Party Management Branches Human Resource Management ICT Management

  31. Roles in the Provisionof Customer Information General Management User Risk Management User Co-ordination Production Communication Customers Provider Channels Mid-Office Back-Office/ Third Parties Call Centre Provider/User Marketing User Product Management Back Office Product A User Internet Provider/User Sales Provider/User Contract Man User Back Office Product B User ATM User Channel Management User Customer Man Manager Transaction Man User Kiosk Provider/User Third Party Product User Service Desk Provider/User Third Party Man User Branches Provider/User Human Resource Management ICT Management

  32. Information Systems in a Virtual Bank Management Information System Risk Management Information System Co-ordination Production Communication Customers Channels Mid-Office Back-Office/ Third Parties Call Centre IS Marketing IS Product Management IS Back Office IS (Product A) Web-Server Sales IS Contract Management IS Back Office IS (Product B) ATM Application Channel Management IS Authorisation Security Customer Management IS Transaction Management IS Kiosk Applications Third Party IS (TP Product) Service Desk IS Third Party Management IS Branch IS HRM Information System ICT Management Information Systems

  33. Technology Infrastructure in a Virtual Bank Management System Risk Management System Co-ordination Production Communication Customers Channels Mid-Office Back-Office/ Third Parties Call Centre Marketing Product Man. Back Office Web-Server Sales IS Contract Man. Back Office ATM Channel Man. Customer Man. Transaction Man Kiosk Third Party Service Desk Third Party Man. Branch HRM System ICT Management Systems

  34. Relation of IAF withOther Topics

  35. Role of IAF inBusiness and ICT Transformation Business & ICT Vision SCOPE Enterprise Level Architectural Design Transformation Programme Plan Project Level Architectural Design Projects (Design and Development) Change Run Operational Business and ICT System

  36. IAF andthe Spiral Approach 1. Contextual 2. Conceptual Identify next level stakeholders, concerns and requirements 3. Logical 4. Physical 6. Decisions by Stakeholders 5. Transformational

  37. IAF and Professional Roles Business Information Information Systems Technology Infrastructure SCOPE Consultant Architect contextual Architectural Design conceptual logical physical transformational Designer (Engineer) Detailed Design Developer (Builder) Development & Implementation Maintenance People Operation & Maintenance

  38. Reference Architectures in IAF (1) Business RA Information RA IS RA TI RA Contextual Rationale Conceptual Style and Conceptual Patterns Appearance, Behaviour, Products/Services Architectural Patterns Logical Logical Patterns Collaboration/Roles or Mechanism/Functions Physical Physical Patterns Physical Components Engineering, Construction Patterns Transformational Transformational Patterns Development/Migration/Evolution

  39. Reference Architectures in IAF (2) Business RA Information RA IS RA TI RA Business Solution Reference Architecture Contextual Conceptual Business Process Patterns Information Provision Patterns Application or “Business Component” Patterns Technology Platform Logical Physical Software Component Patterns Transformational Application Enabling Reference Architecture

  40. Methods and Tools • IAF is open framework for methods and tools, but they must support the architectural description of: • The four architecture areas • The relations between the areas • Enterprise-level and project-level designs • External, Internal and Life-Cycle Viewpoints • Common Quality Viewpoints such as Cost and Performance • Tools must meet the requirements in the White Paper General Architectural Principles and Concepts • Methods and Tools must be related to the rules and guidelines for architectural design in the reference architectures

  41. IAF and Current AD* Methods AD-GO AD-DSE AD-BEA AD-IS in development AD-DIS AD-TI Contextual Conceptual Logical Physical Transformational Information Information Systems Technology Infrastructure Business

  42. Next Version • Architectural Design Approach • more about the process of architecting • may become a separate white paper • Reference Architectures and Examples • review based on experiences with creating a CRM reference architecture • Comments and Contributions to Hans.Goedvolk@Capgemini.nl

More Related