TOGAF MODULES. 1) Introduction. High level introduction, concepts, version

Transcription

1 TOGAF MODULES 1) Introduction High level introduction, concepts, version 2) ADM Development Method, step by step approach for developing an EA (heart of TOGAF) 3) ADM Guidelines and Techniques Collection of Guidelines and Techniques for applying TOGAF and TOGAF ADM (example GAP analysis or guideline for applying ADM/ iterations) 4) Content Framework Work products/ all content used and produced by architecture Meta-model, for artifacts, use of re-usable building blocks, overview architecture deliverables 5) Enterprise Continuum & Tools Classification of artifacts/ work products/ VIEW of repository Model structure repository Overview,Taxonomies (clasification and structure) and tools à categorize and store the outputs of architecture activities (you can see this as a big bucket where you store and classify architecture content Enterprise: / Solution continuum (foundation, common, Industry, org.specific architectures) ABB, SBB: Foundation, common systems, industry, org.specific architectures (building blocks) Solution implementation of the architectures! 6) TOGAF Refernce Models Selection of architecture ref. models (TOGAF foundation arch.and III-RM) 7) Capability Framework Organization, processes, skilss, roles and responsibilities to establish and operatte architecture Resources, guidelines, templates to perform architecture

2 ARCHITECTURE DEVELOPMENT METHOD (ADM) Iterations: One of the main Goals first cycle: Information transfer context creation/ business case development planning governance Requirements Engineering Req. Are identified, stored and fed into and out of ADM stages - creating and mainting requirements - Overview of relationships of arch. Artifacts. - Monitor/ compliance/ regulations Request for Architcture Work Project organization vs organization/ hand over Arch. Plan to project team (create contract) Projects are undertaken as a planned program of work and managed so they deliver the agreed arch. (compliant). Manage Monitor - Contract (sponser/ developent organization) - Arch. Compliant implemented system solution G. Implementation Governance F. Migration planning H. Change Management - Take a harder look at priority order of projects - Perform cost/benefit analysis and Risk Analysis - Transition State Evolution Table - Business Value Assessment Technique - Detailed Impact Analysis report (detailed implementation and migration plan) - Finilized ADD Mini ADM à Prelim. Framework and principles A. Vision (PID/Bus.case) Requirements Managment E. Opportunities and Solutions B. Business D. Technology C. Information systems vision and scope are established - effort (who, what, why, when and where = footprint) Tailer framework/ business principles goals - Meet mayor players - comfortable with proces - modify togaf proces to organization - governance system for future - architecture Capability (select tools, skills, principles) The preliminary phase is not part of the cycle. Only perform once to set up architecture organization. Phase A Input: - Request for Work document (business reason, budget, personell, constraints) -Statement of Work (defines work to be done) Approved by stake holders/ obtain approval) Define scope of project/ Risk assessment Identifiy stake holders, document business req. (business scenario technique) Develop s in 4 domains (BDAT: High level baseline and target architecture - ADD - Building and maintaining Business - Define baseline and Target - Target: formulate viewpoints (ex. Financial Services) - Select bus. Arch. Resources from Arch. Continuum -Decide what notations, methods and tools to use - Build to be model for each viewpoint - Perform Gap analysis where arch. Falls short of stakeholders concern Methods and notations Org. Structure/organigram/bus.goals and objective/ Bus.function/Bus. Services/Bus. Processes/Roles of workers/ Org. And functions matrix/create ABB (gather models to define what functionality will be implemented/abb s are technology aware Data : - specify major types and sources of data necessary to support the business (you do not do database design of your physical database) - modelling principles/ viewpoints and tools - relating data entities to bus. Functions (CRUD) - ABB used in data architecture Application Specify major kinds of applications to process the data and support the business - create matrices of current apps and target apps - Baseline, target, gap analysis - correlate business functions agianst target apps - Focuses on technology aspects (hardware, netwerk) - Repository (TRM) resource - Define technology building blocks (exisiting and new ones) - create baseline tech arch, consider views, and for each viewpoints you create the model for the specific view required, using selected tools and models. ABB -First stage concerned with implementation (Road map/ SBB) - Eveluate models current and target architecture - Identify major work packages or projects (activities/ delivery vehicals) - classify projects as new development, purchase opportunity or reuse of existing system - Review GAP analysis/ Risk analysis - Identify transition / Implementation Factor Assessment & Deduction Matrix/ Consolidated Gaps, Solutions, & Dependencies Matrix - High level implementation plan/ technology and vendor aware - General migration Strategy - Impact Analysis (project priority list) impact of implementing target arch. On the working resources that will carry it out Phase B, C, D Arch. Building Blocks Identified (techn. Aware)

3 Techniques to support Migration planning Phases E and F 1) Implementation Factor Assessment & Deduction (action) Matrix (document factors impacting the architecture Implementation and Migration Plan) 2) Consolidated Gaps, Solutions & Dependencies Matrix (group gaps per domain and assess potential solutions. Planning tool for work packages) 3) Definition Increments table (plan a series of transition architectures outlining the status of the enterprise arch. At specified times. Tabel met projecten en incrementen in tijd) 4) Transition State Evolution Table (TRM model services per transitie weergeven -> show proposed state at varios levels) 5) Business Value Assessment Technique (matrix to assess business value dimension and risk (bollen in matrix) In the phases E and F, the capability should be broken down into a set of increments that are sequenced into Transition s that will lead to the realization of the target architecture. The resulting SBB will then provide the basis for the capability increments solutions. ADM Guidelines: - applying iteration to the ADM process (bijv. baseline of target first) - applying ADM across architecture landscapes - Security architecture and the ADM - Define & Govern SOA s

4 Unfortunately, the Open Group study guide for the part 2 does not provide enough explanation of the different viewpoints. You need to fall back on the TOGAF version 9 documentation and read chapter 35. Phase F: Migration Planning - prioritize implementation projects - detail implementaion plan - Gap analysis of migration - Update project list - detail implementation plan - Blue print to impl. team Phase G: Implementation Governance - connection between governing architecture and development organization is established - selected projects are implemented - Deliverable: Contracts (accepted by developing party) - -compliant solutions Phase H: Change Management (governance) - changes in architecture baseline - Request for work Enterprise Continuum resources: models, solutions patterns, assets (BB) - Continuum - Solution Continuum Governance re SOA - Services (granular) - Functional capabilities - Service oriented (diensten) Risk Management - Initial risk assessment - Residual risk assessment Migration planning phases: - Transition s - Increments - Capability & Gaps project dependencies - Work packages (activities) - Roadmap

5 Artifacts overview (chapter 35) Vision (phase A) Solution Concept Diagram Value Chain Stake holder map matrix High Level Orientation of the solution (key objectives) High Level Orientation of the Enterprise and the outside world Business (phase B) Business Footprint Diagrams Map technical component -to- Business goals Describes links between business goals and services to technical components Event diagram Show relationships between events and business processes Functional decomposition diagram Goal/objective/service diagrams Organization decomposition diagram Process Flow Diagrams Show capabilities of an organization (not a sequence or events) (example: course administration à enrollment à completion etc..) How services contribute to business vision and strategy Example: service = order management and strategy/goal = book via internet Organigram/ organization Overview of units, roles, actors and locations Sequential flows of control between activities Service/ Information diagrams Shows information needed to support on or more business services (basis voor phase C: data arch.) Information Systems - Application (phase C) Application and User Location diagrams Shows where applications are used by end-users Shows where applications are hosted Application communication diagram (interfaces) Application Migration Diagram Enterprise Manageability diagrams Process/system realization diagrams Shows communication between application Shows the interfaces between applications (SOA) Application migration from baseline to target Component deployment technique/ migration steps Shows how one or more applications interact with Application and Technology components à duplications and gaps identification Shows sequence of events when multiple applications are involved (batch/real-time) System Use Case diagram Interactie actor/systeem (functions) Information Systems - Data (phase C) Class diagrams Relatie tussen data entiteiten (ERD) Data dissemination diagrams (data à services) Data Life Cycle diagram Data Migration Diagram Data Security Diagram Logical entities à Application components Relatie tussen data entiteiten en Services weergeven Statussen data rekening houdend met business process. Bijv. bus.proces aanvraag visum, status data: waiting, in progress, accepted (state model) Shows flow of data from baseline to target applications Destination (was string) à becomes entity in data model Data Access à CRUD diagram Technology (phase D) Environment and Location diagrams Shows which location hosts which applications Network computing hardware diagrams 3-tier layer (prsentation-rules-data) overview (network computing) Processing diagrams Deployment of applications/code over different application services Opportunities & Solutions (phase E) Project Context Diagrams Shows the scope of a work package (org, functions, processes, application etc.) Project Portfolio