Togaf® version 9.1 / (Registro nro. 18002)
[ vista simple ]
| 000 -CABECERA | |
|---|---|
| Campo de control de longitud fija | 45948nam a2200277Ma 4500 |
| 001 - NÚMERO DE CONTROL | |
| Campo de control | ocn915909848 |
| 003 - IDENTIFICADOR DE NÚMERO DE CONTROL | |
| Campo de control | OCoLC |
| 007 - CAMPO FIJO DE DESCRIPCIÓN FÍSICA | |
| DESCRIPCIÓN FÍSICA | ta |
| 008 - CAMPO FIJO DE DESCRIPCIÓN FIJA--INFORMACIÓN GENERAL | |
| Campo de control de longitud fija | 120301s2011 ne a g 001 0 eng d |
| 020 ## - ISBN (INTERNATIONAL STANDARD BOOK NUMBER) | |
| ISBN | 9789087536794 |
| 020 ## - ISBN (INTERNATIONAL STANDARD BOOK NUMBER) | |
| ISBN | 9087536798 |
| 040 ## - FUENTE DE CATALOGACIÓN | |
| Agencia de catalogación original | ZZAND |
| Idioma de catalogación | spa |
| Agencia que realiza la transcripción | ZZAND |
| 082 04 - NÚMERO DE LA CLASIFICACIÓN DECIMAL DEWEY | |
| Número de clasificación Decimal | 004.22 |
| Número de documento (Cutter) | T374t |
| Número de edición DEWEY | 21 |
| 110 ## - ENCABEZAMIENTO PRINCIPAL--NOMBRE CORPORATIVO | |
| Nombre corporativo o de jurisdicción como elemento de entrada | The Open Group. |
| 9 (RLIN) | 26079 |
| 245 10 - TÍTULO PROPIAMENTE DICHO | |
| Título | Togaf® version 9.1 / |
| Mención de responsabilidad, etc. | The Open Group. |
| 260 ## - PUBLICACIÓN, DISTRIBUCIÓN, ETC (PIE DE IMPRENTA) | |
| Lugar de publicación, distribución, etc. | Zaltbommel (Holanda) : |
| Nombre del editor, distribuidor, etc. | Van haren Publishing, |
| Fecha de publicación, distribución, etc. | 2011. |
| 300 ## - DESCRIPCIÓN FÍSICA | |
| Extensión | xl, 654 p. : |
| Otros detalles físicos | il. ; |
| Dimensiones | 23 cm. |
| 490 1# - MENCIÓN DE SERIE | |
| Mención de serie | Togaf series |
| 500 ## - NOTA GENERAL | |
| Nota general | Incluye índice. |
| 505 ## - NOTA DE CONTENIDO FORMATEADA | |
| Nota de contenido con formato preestablecido | Frontmatter<br/>Preface<br/>This Document<br/>Intended Audience<br/>Keywords<br/>About The Open Group<br/>Participants<br/>Architecture Forum Technical Reviewers<br/>Architecture Forum Members<br/>Trademarks<br/>Acknowledgements<br/>Referenced Documents<br/>1. Introduction<br/>1.1 Structure of the TOGAF Document<br/>1.2 Executive Overview<br/>What is an enterprise?<br/>Why do I need an enterprise architecture?<br/>What specifically would prompt me to develop an enterprise architecture?<br/>What is an architecture framework?<br/>Why do I need TOGAF as a framework for enterprise architecture?<br/>Who would benefit from using TOGAF?<br/>2. Core Concepts<br/>2.1 What is TOGAF?<br/>2.2 What is Architecture in the Context of TOGAF?<br/>2.3 What Kind of Architecture Does TOGAF Deal With?<br/>2.4 Architecture Development Method<br/>2.5 Deliverables, Artifacts, and Building Blocks<br/>2.6 Enterprise Continuum<br/>2.7 Architecture Repository<br/>2.8 Establishing and Maintaining an Enterprise Architecture Capability<br/>2.9 Establishing the Architecture Capability as an Operational Entity<br/>2.10 Using TOGAF with Other Frameworks<br/>3. Definitions<br/>3.1 Abstraction<br/>3.2 Actor<br/>3.3 Application<br/>3.4 Application Architecture<br/>3.5 Application Platform<br/>3.6 Application Platform Interface (API)<br/>3.7 Architectural Style<br/>3.8 Architecture<br/>3.9 Architecture Building Block (ABB)<br/>3.10 Architecture Continuum<br/>3.11 Architecture Development Method (ADM)<br/>3.12 Architecture Domain<br/>3.13 Architecture Framework<br/>3.14 Architecture Governance<br/>3.15 Architecture Landscape<br/>3.16 Architecture Principles<br/>3.17 Architecture Vision<br/>3.18 Artifact<br/>3.19 Baseline<br/>3.20 Boundaryless Information Flow<br/>3.21 Building Block<br/>3.22 Business Architecture<br/>3.23 Business Function<br/>3.24 Business Governance<br/>3.25 Business Service<br/>3.26 Capability<br/>3.27 Capability Architecture<br/>3.28 Capability Increment<br/>3.29 Communications and Stakeholder Management<br/>3.30 Concerns<br/>3.31 Constraint<br/>3.32 Data Architecture<br/>3.33 Deliverable<br/>3.34 Enterprise<br/>3.35 Enterprise Continuum<br/>3.36 Foundation Architecture<br/>3.37 Framework<br/>3.38 Gap<br/>3.39 Governance<br/>3.40 Information<br/>3.41 Information Technology (IT)<br/>3.42 Interoperability<br/>3.43 Logical<br/>3.44 Metadata<br/>3.45 Metamodel<br/>3.46 Method<br/>3.47 Methodology<br/>3.48 Model<br/>3.49 Modeling<br/>3.50 Objective<br/>3.51 Patterns<br/>3.52 Performance Management<br/>3.53 Physical<br/>3.54 Platform<br/>3.55 Platform Service<br/>3.56 Principle<br/>3.57 Reference Model (RM)<br/>3.58 Repository<br/>3.59 Requirement<br/>3.60 Roadmap<br/>3.61 Role<br/>3.62 Segment Architecture<br/>3.63 Service Orientation<br/>3.64 Service Oriented Architecture (SOA)<br/>3.65 Solution Architecture<br/>3.66 Solution Building Block (SBB)<br/>3.67 Solutions Continuum<br/>3.68 Stakeholder<br/>3.69 Standards Information Base (SIB)<br/>3.70 Strategic Architecture<br/>3.71 Target Architecture<br/>3.72 Taxonomy of Architecture Views<br/>3.73 Technology Architecture<br/>3.74 Transition Architecture<br/>3.75 View<br/>3.76 Viewpoint<br/>3.77 Work Package<br/>4. Release Notes<br/>4.1 What's New in TOGAF 9?<br/>Modular Structure<br/>Content Framework<br/>Extended Guidance on Adopting TOGAF within an Enterprise<br/>Explicit Consideration of Architectural Styles, Including SOA and Security Architecture<br/>Additional ADM Detail<br/>4.1.1 Changes Applied in this Edition<br/>4.2 The Benefits of TOGAF 9<br/>Greater Usability<br/>More Focus on Holistic Enterprise Change<br/>More Consistency of Output<br/>4.3 Mapping of the TOGAF 8.1.1 Structure to TOGAF 9<br/>Part I: Introduction<br/>Part II: Architecture Development Method<br/>Part III: Enterprise Continuum<br/>Part IV: Resource Base<br/>4.4 Mapping of TOGAF 9 Structure to TOGAF 8.1.1<br/>4.5 Using TOGAF<br/>4.5.1 Conditions of Use<br/>4.5.2 How Much Does TOGAF Cost?<br/>4.5.3 Downloads<br/>4.6 Why Join The Open Group?<br/>5. Introduction<br/>5.1 ADM Overview<br/>5.1.1 The ADM, Enterprise Continuum, and Architecture Repository<br/>5.1.2 The ADM and the Foundation Architecture<br/>5.1.3 ADM and Supporting Guidelines and Techniques<br/>5.2 Architecture Development Cycle<br/>5.2.1 Key Points<br/>5.2.2 Basic Structure<br/>5.3 Adapting the ADM<br/>5.4 Architecture Governance<br/>5.5 Scoping the Architecture<br/>5.5.1 Breadth<br/>5.5.2 Depth<br/>5.5.3 Time Period<br/>5.5.4 Architecture Domains<br/>5.6 Architecture Integration<br/>5.7 Summary<br/>6. Preliminary Phase<br/>6.1 Objectives<br/>6.2 Approach<br/>6.2.1 Enterprise<br/>6.2.2 Organizational Context<br/>6.2.3 Requirements for Architecture Work<br/>6.2.4 Principles<br/>6.2.5 Management Frameworks<br/>6.2.6 Relating the Management Frameworks<br/>6.2.7 Planning for Enterprise Architecture/Business Change Maturity Evaluation<br/>6.3 Inputs<br/>6.3.1 Reference Materials External to the Enterprise<br/>6.3.2 Non-Architectural Inputs<br/>6.3.3 Architectural Inputs<br/>6.4 Steps<br/>6.4.1 Scope the Enterprise Organizations Impacted<br/>6.4.2 Confirm Governance and Support Frameworks<br/>6.4.3 Define and Establish Enterprise Architecture Team and Organization<br/>6.4.4 Identify and Establish Architecture Principles<br/>6.4.5 Tailor TOGAF and, if any, Other Selected Architecture Framework(s)<br/>6.4.6 Implement Architecture Tools<br/>6.5 Outputs<br/>7. Phase A: Architecture Vision<br/>7.1 Objectives<br/>7.2 Approach<br/>7.2.1 General<br/>7.2.2 Creating the Architecture Vision<br/>7.2.3 Business Scenarios<br/>7.3 Inputs<br/>7.3.1 Reference Materials External to the Enterprise<br/>7.3.2 Non-Architectural Inputs<br/>7.3.3 Architectural Inputs<br/>7.4 Steps<br/>7.4.1 Establish the Architecture Project<br/>7.4.2 Identify Stakeholders, Concerns, and Business Requirements<br/>7.4.3 Confirm and Elaborate Business Goals, Business Drivers, and Constraints<br/>7.4.4 Evaluate Business Capabilities<br/>7.4.5 Assess Readiness for Business Transformation<br/>7.4.6 Define Scope<br/>7.4.7 Confirm and Elaborate Architecture Principles, including Business Principles<br/>7.4.8 Develop Architecture Vision<br/>7.4.9 Define the Target Architecture Value Propositions and KPIs<br/>7.4.10 Identify the Business Transformation Risks and Mitigation Activities<br/>7.4.11 Develop Statement of Architecture Work; Secure Approval<br/>7.5 Outputs<br/>8. Phase B: Business Architecture<br/>8.1 Objectives<br/>8.2 Approach<br/>8.2.1 General<br/>8.2.2 Developing the Baseline Description<br/>8.2.3 Business Modeling<br/>8.2.4 Architecture Repository<br/>8.3 Inputs<br/>8.3.1 Reference Materials External to the Enterprise<br/>8.3.2 Non-Architectural Inputs<br/>8.3.3 Architectural Inputs<br/>8.4 Steps<br/>8.4.1 Select Reference Models, Viewpoints, and Tools<br/>8.4.1.1 Determine Overall Modeling Process<br/>8.4.1.2 Identify Required Service Granularity Level, Boundaries, and Contracts<br/>8.4.1.3 Identify Required Catalogs of Business Building Blocks<br/>8.4.1.4 Identify Required Matrices<br/>8.4.1.5 Identify Required Diagrams<br/>8.4.1.6 Identify Types of Requirement to be Collected<br/>8.4.2 Develop Baseline Business Architecture Description<br/>8.4.3 Develop Target Business Architecture Description<br/>8.4.4 Perform Gap Analysis<br/>8.4.5 Define Candidate Roadmap Components<br/>8.4.6 Resolve Impacts Across the Architecture Landscape<br/>8.4.7 Conduct Formal Stakeholder Review<br/>8.4.8 Finalize the Business Architecture<br/>8.4.9 Create Architecture Definition Document<br/>8.5 Outputs<br/>9. Phase C: Information Systems Architectures<br/>9.1 Objectives<br/>9.2 Approach<br/>9.3 Inputs<br/>9.3.1 Reference Materials External to the Enterprise<br/>9.3.2 Non-Architectural Inputs<br/>9.3.3 Architectural Inputs<br/>9.4 Steps<br/>9.5 Outputs<br/>10. Phase C: Information Systems Architectures - Data Architecture<br/>10.1 Objectives<br/>10.2 Approach<br/>10.2.1 Key Considerations for Data Architecture<br/>10.2.1.1 Data Management<br/>10.2.1.2 Data Migration<br/>10.2.1.3 Data Governance<br/>10.2.2 Architecture Repository<br/>10.3 Inputs<br/>10.3.1 Reference Materials External to the Enterprise<br/>10.3.2 Non-Architectural Inputs<br/>10.3.3 Architectural Inputs<br/>10.4 Steps<br/>10.4.1 Select Reference Models, Viewpoints, and Tools<br/>10.4.1.1 Determine Overall Modeling Process<br/>10.4.1.2 Identify Required Catalogs of Data Building Blocks<br/>10.4.1.3 Identify Required Matrices<br/>10.4.1.4 Identify Required Diagrams<br/>10.4.1.5 Identify Types of Requirement to be Collected<br/>10.4.2 Develop Baseline Data Architecture Description<br/>10.4.3 Develop Target Data Architecture Description<br/>10.4.4 Perform Gap Analysis<br/>10.4.5 Define Candidate Roadmap Components<br/>10.4.6 Resolve Impacts Across the Architecture Landscape<br/>10.4.7 Conduct Formal Stakeholder Review<br/>10.4.8 Finalize the Data Architecture<br/>10.4.9 Create Architecture Definition Document<br/>10.5 Outputs<br/>11. Phase C: Information Systems Architectures - Application Architecture<br/>11.1 Objectives<br/>11.2 Approach<br/>11.2.1 Architecture Repository<br/>11.3 Inputs<br/>11.3.1 Reference Materials External to the Enterprise<br/>11.3.2 Non-Architectural Inputs<br/>11.3.3 Architectural Inputs<br/>11.4 Steps<br/>11.4.1 Select Reference Models, Viewpoints, and Tools<br/>11.4.1.1 Determine Overall Modeling Process<br/>11.4.1.2 Identify Required Catalogs of Application Building Blocks<br/>11.4.1.3 Identify Required Matrices<br/>11.4.1.4 Identify Required Diagrams<br/>11.4.1.5 Identify Types of Requirement to be Collected<br/>11.4.2 Develop Baseline Application Architecture Description<br/>11.4.3 Develop Target Application Architecture Description<br/>11.4.4 Perform Gap Analysis<br/>11.4.5 Define Candidate Roadmap Components<br/>11.4.6 Resolve Impacts Across the Architecture Landscape<br/>11.4.7 Conduct Formal Stakeholder Review<br/>11.4.8 Finalize the Application Architecture<br/>11.4.9 Create Architecture Definition Document<br/>11.5 Outputs<br/>12. Phase D: Technology Architecture<br/>12.1 Objectives<br/>12.2 Approach<br/>12.2.1 Architecture Repository<br/>12.3 Inputs<br/>12.3.1 Reference Materials External to the Enterprise<br/>12.3.2 Non-Architectural Inputs<br/>12.3.3 Architectural Inputs<br/>12.4 Steps<br/>12.4.1 Select Reference Models, Viewpoints, and Tools<br/>12.4.1.1 Determine Overall Modeling Process<br/>12.4.1.2 Identify Required Catalogs of Technology Building Blocks<br/>12.4.1.3 Identify Required Matrices<br/>12.4.1.4 Identify Required Diagrams<br/>12.4.1.5 Identify Types of Requirement to be Collected<br/>12.4.1.6 Select Services<br/>12.4.2 Develop Baseline Technology Architecture Description<br/>12.4.3 Develop Target Technology Architecture Description<br/>12.4.4 Perform Gap Analysis<br/>12.4.5 Define Candidate Roadmap Components<br/>12.4.6 Resolve Impacts Across the Architecture Landscape<br/>12.4.7 Conduct Formal Stakeholder Review<br/>12.4.8 Finalize the Technology Architecture<br/>12.4.9 Create Architecture Definition Document<br/>12.5 Outputs<br/>12.6 Postscript<br/>13. Phase E: Opportunities & Solutions<br/>13.1 Objectives<br/>13.2 Approach<br/>13.3 Inputs<br/>13.3.1 Reference Materials External to the Enterprise<br/>13.3.2 Non-Architectural Inputs<br/>13.3.3 Architectural Inputs<br/>13.4 Steps<br/>13.4.1 Determine/Confirm Key Corporate Change Attributes<br/>13.4.2 Determine Business Constraints for Implementation<br/>13.4.3 Review and Consolidate Gap Analysis Results from Phases B to D<br/>13.4.4 Review Consolidated Requirements Across Related Business Functions<br/>13.4.5 Consolidate and Reconcile Interoperability Requirements<br/>13.4.6 Refine and Validate Dependencies<br/>13.4.7 Confirm Readiness and Risk for Business Transformation<br/>13.4.8 Formulate Implementation and Migration Strategy<br/>13.4.9 Identify and Group Major Work Packages<br/>13.4.10 Identify Transition Architectures<br/>13.4.11 Create the Architecture Roadmap & Implementation and Migration Plan<br/>13.5 Outputs<br/>14. Phase F: Migration Planning<br/>14.1 Objectives<br/>14.2 Approach<br/>14.3 Inputs<br/>14.3.1 Reference Materials External to the Enterprise<br/>14.3.2 Non-Architectural Inputs<br/>14.3.3 Architectural Inputs<br/>14.4 Steps<br/>14.4.1 Confirm Management Framework Interactions for the Implementation and Migration Plan<br/>14.4.2 Assign a Business Value to Each Work Package<br/>14.4.3 Estimate Resource Requirements, Project Timings, and Availability/Delivery Vehicle<br/>14.4.4 Prioritize the Migration Projects through the Conduct of a Cost/Benefit Assessment and Risk Validation<br/>14.4.5 Confirm Architecture Roadmap and Update Architecture Definition Document<br/>14.4.6 Generate the Implementation and Migration Plan<br/>14.4.7 Complete the Architecture Development Cycle and Document Lessons Learned<br/>14.5 Outputs<br/>15. Phase G: Implementation Governance<br/>15.1 Objectives<br/>15.2 Approach<br/>15.3 Inputs<br/>15.3.1 Reference Materials External to the Enterprise<br/>15.3.2 Non-Architectural Inputs<br/>15.3.3 Architectural Inputs<br/>15.4 Steps<br/>15.4.1 Confirm Scope and Priorities for Deployment with Development Management<br/>15.4.2 Identify Deployment Resources and Skills<br/>15.4.3 Guide Development of Solutions Deployment<br/>15.4.4 Perform Enterprise Architecture Compliance Reviews<br/>15.4.5 Implement Business and IT Operations<br/>15.4.6 Perform Post-Implementation Review and Close the Implementation<br/>15.5 Outputs<br/>16. Phase H: Architecture Change Management<br/>16.1 Objectives<br/>16.2 Approach<br/>16.2.1 Drivers for Change<br/>16.2.2 Enterprise Architecture Change Management Process<br/>16.2.3 Guidelines for Maintenance versus Architecture Redesign<br/>16.3 Inputs<br/>16.3.1 Reference Materials External to the Enterprise<br/>16.3.2 Non-Architectural Inputs<br/>16.3.3 Architectural Inputs<br/>16.4 Steps<br/>16.4.1 Establish Value Realization Process<br/>16.4.2 Deploy Monitoring Tools<br/>16.4.3 Manage Risks<br/>16.4.4 Provide Analysis for Architecture Change Management<br/>16.4.5 Develop Change Requirements to Meet Performance Targets<br/>16.4.6 Manage Governance Process<br/>16.4.7 Activate the Process to Implement Change<br/>16.5 Outputs<br/>17. ADM Architecture Requirements Management<br/>17.1 Objectives<br/>17.2 Approach<br/>17.2.1 General<br/>17.2.2 Requirements Development<br/>17.2.3 Resources<br/>17.2.3.1 Business Scenarios<br/>17.2.3.2 Requirements Tools<br/>17.3 Inputs<br/>17.4 Steps<br/>17.5 Outputs<br/>18. Introduction<br/>18.1 Guidelines for Adapting the ADM Process<br/>18.2 Techniques for Architecture Development<br/>18.3 Using TOGAF with Different Architectural Styles<br/>19. Applying Iteration to the ADM<br/>19.1 Overview<br/>19.2 Iteration Cycles<br/>19.3 Classes of Architecture Engagement<br/>19.4 Approaches to Architecture Development<br/>19.5 Iteration Considerations<br/>19.5.1 Iteration between ADM Cycles<br/>19.5.2 Iteration within an ADM Cycle<br/>19.6 Conclusions<br/>Footnotes<br/>20. Applying the ADM across the Architecture Landscape<br/>20.1 Overview<br/>20.2 Architecture Landscape<br/>20.3 Organizing the Architecture Landscape to Understand the State of the Enterprise<br/>20.4 Developing Architectures at Different Levels<br/>21. Security Architecture and the ADM<br/>21.1 Overview<br/>21.2 Introduction<br/>21.3 Guidance on Security for the Architecture Domains<br/>21.4 ADM Architecture Requirements Management<br/>Is our security good?<br/>Nothing useful can be said about a security measure outside the context of an application, or a system and its environment<br/>21.5 Preliminary Phase<br/>Scope the enterprise organizations impacted by the security architecture<br/>Define and document applicable regulatory and security policy requirements<br/>Define the required security capability as part of Architecture Capability<br/>Implement security architecture tools<br/>21.5.1 Security Inputs<br/>21.5.2 Security Outputs<br/>21.6 Phase A: Architecture Vision<br/>Obtain management support for security measures<br/>Define necessary security-related management sign-off milestones of this architecture development cycle<br/>Determine and document applicable disaster recovery or business continuity plans/requirements<br/>Identify and document the anticipated physical/business/regulatory environment(s) in which the system(s) will be deployed<br/>Determine and document the criticality of the system: safety-critical/mission-critical/non-critical<br/>21.6.1 Security Inputs<br/>21.6.2 Security Outputs<br/>21.7 Phase B: Business Architecture<br/>Determine who are the legitimate actors who will interact with the product/service/process<br/>Assess and baseline current security-specific business processes (enhancement of existing objective)<br/>Determine whom/how much it is acceptable to inconvenience in utilizing security measures<br/>Identify and document interconnecting systems beyond project control<br/>Determine the assets at risk if something goes wrong - "What are we trying to protect?"<br/>Determine the cost (both qualitative and quantitative) of asset loss/impact in failure cases<br/>Identify and document the ownership of assets<br/>Determine and document appropriate security forensic processes<br/>Identify the criticality of the availability and correct operation of the overall service<br/>Determine and document how much security (cost) is justified by the threats and the value of the assets at risk<br/>Reassess and confirm Architecture Vision decisions<br/>Assess alignment or conflict of identified security policies with business goals<br/>Determine "what can go wrong?"<br/>21.7.1 Security Inputs<br/>21.7.2 Security Outputs<br/>21.8 Phase C: Information Systems Architectures<br/>Assess and baseline current security-specific architecture elements (enhancement of existing objective)<br/>Identify safe default actions and failure states<br/>Identify and evaluate applicable recognized guidelines and standards<br/>Revisit assumptions regarding interconnecting systems beyond project control<br/>Determine and document the sensitivity or classification level of information stored/created/used<br/>Identify and document custody of assets<br/>Identify the criticality of the availability and correct operation of each function<br/>Determine the relationship of the system under design with existing business disaster/continuity plans<br/>Identify what aspects of the system must be configurable to reflect changes in policy/business environment/access control<br/>Identify lifespan of information used as defined by business needs and regulatory requirements<br/>Determine approaches to address identified risks:<br/>Identify actions/events that warrant logging for later review or triggering forensic processes<br/>Identify and document requirements for rigor in proving accuracy of logged events (non-repudiation)<br/>Identify potential/likely avenues of attack<br/>Determine "what can go wrong?"<br/>21.8.1 Security Inputs<br/>21.8.2 Security Outputs<br/>21.9 Phase D: Technology Architecture<br/>Assess and baseline current security-specific technologies (enhancement of existing objective)<br/>Revisit assumptions regarding interconnecting systems beyond project control<br/>Identify and evaluate applicable recognized guidelines and standards<br/>Identify methods to regulate consumption of resources<br/>Engineer a method by which the efficacy of security measures will be measured and communicated on an ongoing basis<br/>Identify the trust (clearance) level of:<br/>Identify minimal privileges required for any entity to achieve a technical or business objective<br/>Identify mitigating security measures, where justified by risk assessment<br/>Determine "what can go wrong?"<br/>21.9.1 Security Inputs<br/>21.9.2 Security Outputs<br/>21.10 Phase E: Opportunities & Solutions<br/>Identify existing security services available for re-use<br/>Engineer mitigation measures addressing identified risks<br/>Evaluate tested and re-usable security software and security system resources<br/>Identify new code/resources/assets that are appropriate for re-use<br/>Determine "what can go wrong?"<br/>21.11 Phase F: Migration Planning<br/>Assess the impact of new security measures upon other new components or existing leveraged systems<br/>Implement assurance methods by which the efficacy of security measures will be measured and communicated on an ongoing basis<br/>Identify correct secure installation parameters, initial conditions, and configurations<br/>Implement disaster recovery and business continuity plans or modifications<br/>Determine "what can go wrong?"<br/>21.12 Phase G: Implementation Governance<br/>Establish architecture artifact, design, and code reviews and define acceptance criteria for the successful implementation of the findings<br/>Implement methods and procedures to review evidence produced by the system that reflects operational stability and adherence to security policies<br/>Implement necessary training to ensure correct deployment, configuration, and operations of security-relevant subsystems and components; ensure awareness training of all users and non-privileged operators of the system and/or its components<br/>Determine "what has gone wrong?"<br/>21.13 Phase H: Architecture Change Management<br/>Determine "what has gone wrong?"<br/>Incorporate security-relevant changes to the environment into the requirements for future enhancement (enhancement of existing objective)<br/>21.14 References<br/>22. Using TOGAF to Define & Govern SOAs<br/>22.1 Overview<br/>22.2 Introduction<br/>22.3 SOA Definition<br/>22.4 SOA Features<br/>22.5 Enterprise Architecture and SOA<br/>22.6 SOA and Levels<br/>22.6.1 Level of Detail of Implementation Specification<br/>22.6.2 SOA Activities at Different Levels<br/>22.7 Using TOGAF for SOA<br/>22.7.1 Preliminary Phase<br/>22.7.1.1 Principle of Service-Orientation<br/>22.7.1.2 Governance and Support Strategy<br/>22.7.1.3 Partitions and Centers of Excellence<br/>22.7.1.4 Architecture Repository<br/>22.7.2 Phase A: Architecture Vision<br/>22.7.2.1 Stakeholders, Concerns, and Business Requirements<br/>22.7.3 Architecture Development: Phases B, C, and D<br/>Phase B: Business Architecture<br/>Phase C: Information Systems Architectures<br/>SOA-Specific Phase C Artifacts<br/>Phase D: Technology Architecture<br/>SOA-Specific Phase D Artifacts<br/>Phase E: Opportunities and Solutions<br/>SOA-Specific Phase E Artifacts<br/>Phase F: Migration Planning<br/>Phase G: Implementation Governance<br/>Phase H: Architecture Change Management<br/>22.8 Summary<br/>23. Architecture Principles<br/>23.1 Introduction<br/>23.2 Characteristics of Architecture Principles<br/>23.3 Components of Architecture Principles<br/>23.4 Developing Architecture Principles<br/>23.4.1 Qualities of Principles<br/>23.5 Applying Architecture Principles<br/>23.6 Example Set of Architecture Principles<br/>23.6.1 Business Principles<br/>Principle 1: Primary of Principles<br/>Principle 2: Maximize Benefit to the Enterprise<br/>Principle 3: Information Management is Everybody's Business<br/>Principle 4: Business Continuity<br/>Principle 5: Common Use Applications<br/>Principle 6: Service Orientation<br/>Principle 7: Compliance with Law<br/>Principle 8: IT Responsibility<br/>Principle 9: Protection of Intellectual Property<br/>23.6.2 Data Principles<br/>Principle 10: Data is an Asset<br/>Principle 11: Data is Shared<br/>Principle 12: Data is Accessible<br/>Principle 13: Data Trustee<br/>Principle 14: Common Vocabulary and Data Definitions<br/>Principle 15: Data Security<br/>23.6.3 Application Principles<br/>Principle 16: Technology Independence<br/>Principle 17: Ease-of-Use<br/>23.6.4 Technology Principles<br/>Principle 18: Requirements-Based Change<br/>Principle 19: Responsive Change Management<br/>Principle 20: Control Technical Diversity<br/>Principle 21: Interoperability<br/>24. Stakeholder Management<br/>24.1 Introduction<br/>24.2 Approach to Stakeholder Management<br/>24.3 Steps in the Stakeholder Management Process<br/>24.3.1 Identify Stakeholders<br/>24.3.1.1 Sample Stakeholder Analysis<br/>24.3.2 Classify Stakeholder Positions<br/>24.3.3 Determine Stakeholder Management Approach<br/>24.3.4 Tailor Engagement Deliverables<br/>24.4 Template Stakeholder Map<br/>25. Architecture Patterns<br/>25.1 Introduction<br/>25.1.1 Background<br/>25.1.2 Content of a Pattern<br/>25.1.3 Terminology<br/>25.1.3.1 Architecture Patterns and Design Patterns<br/>25.1.3.2 Patterns and the Architecture Continuum<br/>25.1.3.3 Patterns and Views<br/>25.1.3.4 Patterns and Business Scenarios<br/>25.1.4 Architecture Patterns in Use<br/>25.2 US Treasury Architecture Development Guidance (TADG)<br/>25.2.1 TADG Pattern Content<br/>25.2.2 TADG Architecture Patterns<br/>25.3 IBM Patterns for e-Business<br/>25.4 Some Pattern Resources<br/>26. Business Scenarios and Business Goals<br/>26.1 Introduction<br/>26.2 Benefits of Business Scenarios<br/>26.3 Creating the Business Scenario<br/>26.3.1 Overall Process<br/>26.3.2 Gathering<br/>26.3.3 Analyzing<br/>26.3.4 Reviewing<br/>26.4 Contents of a Business Scenario<br/>26.5 Contributions to the Business Scenario<br/>26.6 Business Scenarios and the TOGAF ADM<br/>26.7 Developing Business Scenarios<br/>26.7.1 General Guidelines<br/>26.7.2 Questions to Ask for Each Area<br/>Identifying, Documenting, and Ranking the Problem<br/>Identifying the Business & Technical Environment, and Documenting in Models<br/>Identifying and Documenting Objectives<br/>Identifying Human Actors and their Place in the Business Model<br/>Identifying Computer Actors and their Place in the Technology Model<br/>Documenting Roles, Responsibilities, Measures of Success, Required Scripts<br/>Checking for Fitness-for-Purpose, and refining if necessary<br/>26.8 Business Scenario Documentation<br/>26.8.1 Textual Documentation<br/>26.8.2 Business Scenario Models<br/>26.9 Guidelines on Goals and Objectives<br/>26.9.1 Importance of Goals<br/>26.9.2 Importance of SMART Objectives<br/>Example of Making Objectives SMART<br/>26.9.3 Categories of Goals and Objectives<br/>Goal: Improve Business Process Performance<br/>Goal: Decrease Costs<br/>Goal: Improve Business Operations<br/>Goal: Improve Management Efficacy<br/>Goal: Reduce Risk<br/>Goal: Improve Effectiveness of IT Organization<br/>Goal: Improve User Productivity<br/>Goal: Improve Portability and Scalability<br/>Goal: Improve Interoperability<br/>Goal: Increase Vendor Independence<br/>Goal: Reduce Lifecycle Costs<br/>Goal: Improve Security<br/>Goal: Improve Manageability<br/>26.10 Summary<br/>27. Gap Analysis<br/>27.1 Introduction<br/>27.2 Suggested Steps<br/>27.3 Example<br/>28. Migration Planning Techniques<br/>28.1 Implementation Factor Assessment & Deduction Matrix<br/>28.2 Consolidated Gaps, Solutions, & Dependencies Matrix<br/>28.3 Architecture Definition Increments Table<br/>28.4 Transition Architecture State Evolution Table<br/>28.5 Business Value Assessment Technique<br/>29. Interoperability Requirements<br/>29.1 Overview<br/>29.2 Defining Interoperability<br/>29.3 Enterprise Operating Model<br/>29.4 Refining Interoperability<br/>29.5 Determining Interoperability Requirements<br/>29.6 Reconciling Interoperability Requirements with Potential Solutions<br/>29.7 Summary<br/>Footnotes<br/>30. Business Transformation Readiness Assessment<br/>30.1 Introduction<br/>30.1.1 Business Transformation Enablement Program (BTEP)<br/>30.2 Determine Readiness Factors<br/>30.3 Present Readiness Factors<br/>30.4 Assess Readiness Factors<br/>30.4.1 Readiness Factor Vision<br/>30.4.2 Readiness Factor Rating<br/>30.4.3 Readiness Factor Risks & Actions<br/>30.5 Readiness and Migration Planning<br/>30.6 Marketing the Implementation Plan<br/>30.7 Conclusion<br/>Footnotes<br/>31. Risk Management<br/>31.1 Introduction<br/>31.2 Risk Classification<br/>31.3 Risk Identification<br/>31.4 Initial Risk Assessment<br/>31.5 Risk Mitigation and Residual Risk Assessment<br/>31.6 Conduct Residual Risk Assessment<br/>31.7 Risk Monitoring and Governance (Phase G)<br/>31.8 Summary<br/>32. Capability-Based Planning<br/>32.1 Overview<br/>32.2 Capability-Based Planning Paradigm<br/>32.3 Concept of Capability-Based Planning<br/>32.3.1 Capability Dimensions<br/>32.3.2 Capability Increments<br/>32.4 Capabilities in an Enterprise Architecture Context<br/>32.5 Summary<br/>33. Introduction<br/>33.1 Overview<br/>33.2 Content Metamodel<br/>33.3 Content Framework and the TOGAF ADM<br/>33.4 Structure of Part IV<br/>34. Content Metamodel<br/>34.1 Overview<br/>34.2 Content Metamodel Vision and Concepts<br/>34.2.1 Core Content Metamodel Concepts<br/>Core and Extension Content<br/>Core Metamodel Entities<br/>Catalog, Matrix, and Diagram Concept<br/>34.2.2 Overview of the Content Metamodel<br/>34.3 Content Metamodel in Detail<br/>34.3.1 Core Content Metamodel<br/>34.3.2 Core Architecture Artifacts<br/>34.3.3 Full Content Metamodel<br/>34.4 Content Metamodel Extensions<br/>34.4.1 Governance Extensions<br/>Purpose<br/>Required Changes to the Metamodel<br/>34.4.2 Services Extensions<br/>Purpose<br/>Required Changes to the Metamodel<br/>34.4.3 Process Modeling Extensions<br/>Purpose<br/>Required Changes to the Metamodel<br/>34.4.4 Data Extensions<br/>Purpose<br/>Required Changes to the Metamodel<br/>34.4.5 Infrastructure Consolidation Extensions<br/>Purpose<br/>Required Changes to the Metamodel<br/>34.4.6 Motivation Extensions<br/>Purpose<br/>Required Changes to the Metamodel<br/>34.5 Content Metamodel Entities<br/>34.6 Content Metamodel Attributes<br/>34.7 Metamodel Relationships<br/>Footnotes<br/>35. Architectural Artifacts<br/>35.1 Basic Concepts<br/>35.1.1 Simple Example of a Viewpoint and View<br/>35.2 Developing Views in the ADM<br/>35.2.1 General Guidelines<br/>35.2.2 View Creation Process<br/>35.3 Views, Tools, and Languages<br/>35.3.1 Overview<br/>35.4 Views and Viewpoints<br/>35.4.1 Example of Views and Viewpoints<br/>35.4.2 Views and Viewpoints in Enterprise Architecture<br/>35.4.3 Need for a Common Language and Interoperable Tools for Architecture Description<br/>35.5 Conclusions<br/>35.6 Architectural Artifacts by ADM Phase<br/>35.6.1 Preliminary Phase<br/>Principles Catalog<br/>35.6.2 Phase A: Architecture Vision<br/>Stakeholder Map Matrix<br/>Value Chain Diagram<br/>Solution Concept Diagram<br/>35.6.3 Phase B: Business Architecture<br/>Organization/Actor Catalog<br/>Driver/Goal/Objective Catalog<br/>Role Catalog<br/>Business Service/Function Catalog<br/>Location Catalog<br/>Process/Event/Control/Product Catalog<br/>Contract/Measure Catalog<br/>Business Interaction Matrix<br/>Actor/Role Matrix<br/>Business Footprint Diagram<br/>Business Service/Information Diagram<br/>Functional Decomposition Diagram<br/>Product Lifecycle Diagram<br/>Goal/Objective/Service Diagram<br/>Business Use-Case Diagram<br/>Organization Decomposition Diagram<br/>Process Flow Diagram<br/>Event Diagram<br/>35.6.4 Phase C: Data Architecture<br/>Data Entity/Data Component Catalog<br/>Data Entity/Business Function Matrix<br/>Application/Data Matrix<br/>Conceptual Data Diagram<br/>Logical Data Diagram<br/>Data Dissemination Diagram<br/>Data Security Diagram<br/>Data Migration Diagram<br/>Data Lifecycle Diagram<br/>35.6.5 Phase C: Application Architecture<br/>Application Portfolio Catalog<br/>Interface Catalog<br/>Application/Organization Matrix<br/>Role/Application Matrix<br/>Application/Function Matrix<br/>Application Interaction Matrix<br/>Application Communication Diagram<br/>Application and User Location Diagram<br/>Application Use-Case Diagram<br/>Enterprise Manageability Diagram<br/>Process/Application Realization Diagram<br/>Software Engineering Diagram<br/>Application Migration Diagram<br/>Software Distribution Diagram<br/>35.6.6 Phase D: Technology Architecture<br/>Technology Standards Catalog<br/>Technology Portfolio Catalog<br/>Application/Technology Matrix<br/>Environments and Locations Diagram<br/>Platform Decomposition Diagram<br/>Processing Diagram<br/>Networked Computing/Hardware Diagram<br/>Communications Engineering Diagram<br/>35.6.7 Phase E: Opportunities and Solutions<br/>Project Context Diagram<br/>Benefits Diagram<br/>35.6.8 Requirements Management<br/>Requirements Catalog<br/>35.7 Recommended Architecture Views to be Developed<br/>35.7.1 Developing a Business Architecture View<br/>35.7.1.1 Stakeholders and Concerns<br/>35.7.1.2 Developing the View<br/>35.7.1.3 Key Issues<br/>35.7.2 Developing an Enterprise Security View<br/>35.7.2.1 Stakeholders and Concerns<br/>35.7.2.2 Developing the View<br/>35.7.2.3 Basic Concepts<br/>Information Domains<br/>Strict Isolation<br/>Absolute Protection<br/>35.7.2.4 Security Generic Architecture View<br/>35.7.2.5 Security Services Allocation<br/>Operating System Services<br/>Network Services<br/>System Security Management Services<br/>35.7.3 Developing a Software Engineering View<br/>35.7.3.1 Stakeholders and Concerns<br/>Development Approach<br/>Software Modularity and Re-Use<br/>Portability<br/>Migration and Interoperability<br/>35.7.3.2 Key Issues<br/>Data-Intensive versus Information-Intensive Software Systems<br/>Achieving Interoperability<br/>Software Tiers<br/>Two-Tier<br/>Three-Tier<br/>Five-Tier<br/>Some Uses of a Data Access Tier<br/>One Possible Instantiation of a DAI<br/>DAIs Enable Flexibility<br/>Distribution<br/>Infrastructure Bus<br/>35.7.3.3 Conclusion<br/>35.7.4 Developing a System Engineering View<br/>35.7.4.1 Stakeholders and Concerns<br/>35.7.4.2 Key Issues<br/>Client/Server Model<br/>Master/Slave and Hierarchic Models<br/>Peer-to-Peer Model<br/>Distributed Object Management Model<br/>35.7.5 Developing a Communications Engineering View<br/>35.7.5.1 Stakeholders and Concerns<br/>35.7.5.2 Key Issues<br/>Communications Infrastructure<br/>Communications Models<br/>The OSI Reference Model<br/>Communications Framework<br/>Allocation of Services to Components<br/>35.7.6 Developing a Data Flow View<br/>35.7.6.1 Stakeholders and Concerns<br/>35.7.6.2 Developing the View<br/>35.7.6.3 Key Issues<br/>Database Management Systems<br/>Database Models<br/>Distributed DBMSs<br/>Distributed Heterogeneous DBMSs<br/>Data Dictionary/Directory Systems<br/>Data Administration<br/>Repository<br/>Database Administration<br/>Data Security<br/>35.7.7 Developing an Enterprise Manageability View<br/>35.7.7.1 Stakeholders and Concerns<br/>35.7.7.2 Developing the View<br/>35.7.7.3 Key Issues<br/>35.7.8 Developing an Acquirer View<br/>35.7.8.1 Stakeholders and Concerns<br/>35.7.8.2 Developing the View<br/>35.7.8.3 Key Issues<br/>Footnotes<br/>36. Architecture Deliverables<br/>36.1 Introduction<br/>36.2 Deliverable Descriptions<br/>36.2.1 Architecture Building Blocks<br/>36.2.2 Architecture Contract<br/>Purpose<br/>Content<br/>36.2.3 Architecture Definition Document<br/>Purpose<br/>Content<br/>36.2.4 Architecture Principles<br/>Purpose<br/>Content<br/>36.2.5 Architecture Repository<br/>Purpose<br/>Content<br/>36.2.6 Architecture Requirements Specification<br/>Purpose<br/>Content<br/>36.2.7 Architecture Roadmap<br/>Purpose<br/>Content<br/>36.2.8 Architecture Vision<br/>Purpose<br/>Content<br/>36.2.9 Business Principles, Business Goals, and Business Drivers<br/>Purpose<br/>Content<br/>36.2.10 Capability Assessment<br/>Purpose<br/>Content<br/>36.2.11 Change Request<br/>Purpose<br/>Content<br/>36.2.12 Communications Plan<br/>Purpose<br/>Content<br/>36.2.13 Compliance Assessment<br/>Purpose<br/>Content<br/>36.2.14 Implementation and Migration Plan<br/>Purpose<br/>Content<br/>36.2.15 Implementation Governance Model<br/>Purpose<br/>Content<br/>36.2.16 Organizational Model for Enterprise Architecture<br/>Purpose<br/>Content<br/>36.2.17 Request for Architecture Work<br/>Purpose<br/>Content<br/>36.2.18 Requirements Impact Assessment<br/>Purpose<br/>Content<br/>36.2.19 Solution Building Blocks<br/>36.2.20 Statement of Architecture Work<br/>Purpose<br/>Content<br/>36.2.21 Tailored Architecture Framework<br/>Purpose<br/>Content<br/>37. Building Blocks<br/>37.1 Overview<br/>37.2 Introduction to Building Blocks<br/>37.2.1 Overview<br/>37.2.2 Generic Characteristics<br/>37.2.3 Architecture Building Blocks<br/>37.2.3.1 Characteristics<br/>37.2.3.2 Specification Content<br/>37.2.4 Solution Building Blocks<br/>37.2.4.1 Characteristics<br/>37.2.4.2 Specification Content<br/>37.3 Building Blocks and the ADM<br/>37.3.1 Basic Principles<br/>37.3.1.1 Building Blocks in Architecture Design<br/>37.3.1.2 Building Block Design<br/>37.3.2 Building Block Specification Process in the ADM<br/>Footnotes<br/>38. Introduction<br/>38.1 Introduction<br/>38.2 Structure of Part V<br/>39. Enterprise Continuum<br/>39.1 Overview<br/>39.2 Enterprise Continuum and Architecture Re-Use<br/>39.3 Constituents of the Enterprise Continuum<br/>39.4 Enterprise Continuum in Detail<br/>39.4.1 Architecture Continuum<br/>Foundation Architecture<br/>Common Systems Architectures<br/>Industry Architectures<br/>Organization-Specific Architectures<br/>39.4.2 Solutions Continuum<br/>Foundation Solutions<br/>Common Systems Solutions<br/>Industry Solutions<br/>Organization-Specific Solutions<br/>39.5 The Enterprise Continuum and the ADM<br/>39.6 The Enterprise Continuum and Your Organization<br/>39.6.1 Relationships<br/>39.6.2 Your Enterprise<br/>40. Architecture Partitioning<br/>40.1 Overview<br/>40.2 Applying Classification to Create Partitioned Architectures<br/>40.2.1 Activities within the Preliminary Phase<br/>40.3 Integration<br/>41. Architecture Repository<br/>41.1 Overview<br/>41.2 Architecture Landscape<br/>41.3 Reference Library<br/>41.3.1 Overview<br/>41.4 Standards Information Base<br/>41.4.1 Overview<br/>41.4.2 Types of Standard<br/>41.4.3 Standards Lifecycle<br/>41.4.4 Standards Classification within the Standards Information Base<br/>41.5 Governance Log<br/>41.5.1 Overview<br/>41.5.2 Contents of the Governance Log<br/>41.6 The Enterprise Repository<br/>41.6.1 Requirements Repository<br/>41.6.2 Solutions Repository<br/>41.7 External Repositories<br/>41.7.1 External Reference Models<br/>41.7.2 External Standards<br/>41.7.3 Architecture Board Approvals<br/>42. Tools for Architecture Development<br/>42.1 Overview<br/>42.2 Issues in Tool Standardization<br/>43. Foundation Architecture: Technical Reference Model<br/>43.1 Concepts<br/>43.1.1 Role of the TRM in the Foundation Architecture<br/>43.1.2 TRM Components<br/>43.1.3 Other TRMs<br/>43.2 High-Level Breakdown<br/>43.2.1 Overview<br/>43.2.2 Portability and Interoperability<br/>43.3 TRM in Detail<br/>43.3.1 Introduction<br/>43.3.2 TRM Entities and Interfaces<br/>43.3.3 Application Software<br/>43.3.3.1 Business Applications<br/>43.3.3.2 Infrastructure Applications<br/>43.3.4 Application Platform<br/>43.3.4.1 Platform Concept<br/>43.3.4.2 Extending the TRM<br/>43.3.4.3 Interfaces Between Services<br/>43.3.4.4 Future Developments<br/>43.3.5 Communications Infrastructure<br/>43.3.6 Application Platform Interface<br/>43.3.7 Communications Infrastructure Interface<br/>43.3.8 Qualities<br/>43.4 Application Platform - Taxonomy<br/>43.4.1 Basic Principles<br/>43.4.2 Application Platform Service Categories<br/>43.4.2.1 Object-Oriented Provision of Services<br/>43.4.3 Application Platform Service Qualities<br/>43.4.3.1 Principles<br/>43.4.3.2 Taxonomy of Service Qualities<br/>43.5 Detailed Platform Taxonomy<br/>43.5.1 Data Interchange Services<br/>43.5.2 Data Management Services<br/>43.5.3 Graphics and Imaging Services<br/>43.5.4 International Operation Services<br/>43.5.5 Location and Directory Services<br/>43.5.6 Network Services<br/>43.5.7 Operating System Services<br/>43.5.8 Software Engineering Services<br/>43.5.9 Transaction Processing Services<br/>43.5.10 User Interface Services<br/>43.5.11 Security Services<br/>43.5.12 System and Network Management Services<br/>43.5.13 Object-Oriented Provision of Services<br/>44. Integrated Information Infrastructure Reference Model<br/>44.1 Basic Concepts<br/>44.1.1 Background<br/>44.1.2 Components of the Model<br/>44.1.3 Relationship to Other parts of TOGAF<br/>44.1.4 Key Business and Technical Drivers<br/>44.1.4.1 Problem Space: The Need for Boundaryless Information Flow<br/>44.1.4.2 Solution Space: The Need for Integrated Information Infrastructure<br/>44.1.5 Status of the III-RM<br/>44.2 High-Level View<br/>44.2.1 Derivation of the III-RM from the TRM<br/>44.2.2 High-Level III-RM Graphic<br/>44.2.3 Components of the High-Level III-RM<br/>44.3 Detailed Taxonomy<br/>44.3.1 Detailed III-RM Graphic<br/>44.3.2 Business Applications<br/>44.3.2.1 Information Provider Applications<br/>44.3.2.2 Brokerage Applications<br/>44.3.2.3 Information Consumer Applications<br/>44.3.3 Infrastructure Applications<br/>44.3.3.1 Development Tools<br/>Business Modeling Tools<br/>Design Modeling Tools<br/>Implementation and Construction Tools<br/>Data Modeling Tools<br/>Deployment Tools<br/>Libraries<br/>44.3.3.2 Management Utilities<br/>Operations, Administration, and Management (OA&M) Utilities<br/>Quality of Service Manager Utilities<br/>Copy Management Utilities<br/>Storage Management Utilities<br/>44.3.4 Application Platform<br/>44.3.4.1 Software Engineering Services<br/>44.3.4.2 Security Services<br/>44.3.4.3 Location and Directory Services<br/>44.3.4.4 Human Interaction Services<br/>44.3.4.5 Data Interchange Services<br/>44.3.4.6 Data Management Services<br/>44.3.4.7 Additional Operating System Services<br/>44.3.5 Qualities<br/>Footnotes<br/>45. Introduction<br/>45.1 Overview<br/>45.2 Structure of Part VII<br/>46. Establishing an Architecture Capability<br/>46.1 Overview<br/>46.2 Phase A: Architecture Vision<br/>46.3 Phase B: Business Architecture<br/>46.4 Phase C: Data Architecture<br/>46.5 Phase C: Application Architecture<br/>46.6 Phase D: Technology Architecture<br/>46.7 Phase E: Opportunities & Solutions<br/>46.8 Phase F: Migration Planning<br/>46.9 Phase G: Implementation Governance<br/>46.10 Phase H: Architecture Change Management<br/>46.11 Requirements Management<br/>47. Architecture Board<br/>47.1 Role<br/>47.2 Responsibilities<br/>47.3 Setting Up the Architecture Board<br/>47.3.1 Triggers<br/>47.3.2 Size of the Board<br/>47.3.3 Board Structure<br/>47.4 Operation of the Architecture Board<br/>47.4.1 General<br/>47.4.2 Preparation<br/>47.4.3 Agenda<br/>Minutes of Previous Meeting<br/>Requests for Change<br/>Dispensations<br/>Compliance Assessments<br/>Dispute Resolution<br/>Architecture Strategy and Direction Documentation<br/>Actions Assigned<br/>Contract Documentation Management<br/>Any Other Business (AOB)<br/>Schedule of Meetings<br/>48. Architecture Compliance<br/>48.1 Introduction<br/>48.2 Terminology: The Meaning of Architecture Compliance<br/>48.3 Architecture Compliance Reviews<br/>48.3.1 Purpose<br/>48.3.2 Timing<br/>48.3.3 Governance and Personnel Scenarios<br/>48.4 Architecture Compliance Review Process<br/>48.4.1 Overview<br/>48.4.2 Roles<br/>48.4.3 Steps<br/>48.5 Architecture Compliance Review Checklists<br/>48.5.1 Hardware and Operating System Checklist<br/>48.5.2 Software Services and Middleware Checklist<br/>48.5.3 Applications Checklists<br/>48.5.3.1 Infrastructure (Enterprise Productivity) Applications<br/>48.5.3.2 Business Applications<br/>48.5.3.3 Application Integration Approach<br/>48.5.4 Information Management Checklists<br/>48.5.4.1 Data Values<br/>48.5.4.2 Data Definition<br/>48.5.4.3 Security/Protection<br/>48.5.4.4 Hosting, Data Types, and Sharing<br/>48.5.4.5 Common Services<br/>48.5.4.6 Access Method<br/>48.5.5 Security Checklist<br/>48.5.6 System Management Checklist<br/>48.5.7 System Engineering/Overall Architecture Checklists<br/>48.5.7.1 General<br/>48.5.7.2 Processors/Servers/Clients<br/>48.5.7.3 Client<br/>48.5.7.4 Application Server<br/>48.5.7.5 Data Server<br/>48.5.7.6 COTS (where applicable)<br/>48.5.8 System Engineering/Methods & Tools Checklist<br/>48.6 Architecture Compliance Review Guidelines<br/>48.6.1 Tailoring the Checklists<br/>48.6.2 Conducting Architecture Compliance Reviews<br/>49. Architecture Contracts<br/>49.1 Role<br/>49.2 Contents<br/>49.2.1 Statement of Architecture Work<br/>49.2.2 Contract between Architecture Design and Development Partners<br/>49.2.3 Contract between Architecting Function and Business Users<br/>49.3 Relationship to Architecture Governance<br/>50. Architecture Governance<br/>50.1 Introduction<br/>50.1.1 Levels of Governance within the Enterprise<br/>50.1.2 Nature of Governance<br/>50.1.2.1 Governance: A Generic Perspective<br/>50.1.2.2 Characteristics of Governance<br/>50.1.3 Technology Governance<br/>50.1.4 IT Governance<br/>50.1.4.1 An IT Controls Framework - COBIT<br/>50.1.5 Architecture Governance: Overview<br/>50.1.5.1 Architecture Governance Characteristics<br/>50.1.5.2 Architecture Governance as a Board-Level Responsibility<br/>50.1.5.3 TOGAF and Architecture Governance<br/>50.2 Architecture Governance Framework<br/>50.2.1 Architecture Governance Framework - Conceptual Structure<br/>50.2.1.1 Key Concepts<br/>50.2.1.2 Key Architecture Governance Processes<br/>Policy Management and Take-On<br/>Compliance<br/>Dispensation<br/>Monitoring and Reporting<br/>Business Control<br/>Environment Management<br/>50.2.2 Architecture Governance Framework - Organizational Structure<br/>50.2.2.1 Overview<br/>50.2.2.2 Key Areas<br/>50.2.2.3 Operational Benefits<br/>50.3 Architecture Governance in Practice<br/>50.3.1 Architecture Governance - Key Success Factors<br/>50.3.2 Elements of an Effective Architecture Governance Strategy<br/>50.3.2.1 Architecture Governance and Corporate Politics<br/>Footnotes<br/>51. Architecture Maturity Models<br/>51.1 Overview<br/>51.2 Background<br/>51.3 US DoC ACMM Framework<br/>51.3.1 Overview<br/>51.3.2 Elements of the ACMM<br/>51.3.3 Example: Enterprise Architecture Process Maturity Levels<br/>Level 0: None<br/>Level 1: Initial<br/>Level 2: Under Development<br/>Level 3: Defined<br/>Level 4: Managed<br/>Level 5: Optimizing<br/>51.4 Capability Maturity Models Integration (CMMI)<br/>51.4.1 Introduction<br/>51.4.2 SCAMPI Method<br/>51.5 Conclusions<br/>Footnotes<br/>52. Architecture Skills Framework<br/>52.1 Introduction<br/>52.2 Need for an Enterprise Architecture Skills Framework<br/>52.2.1 Definitional Rigor<br/>52.2.2 Basis of an Internal Architecture Practice<br/>52.3 Goals/Rationale<br/>52.3.1 Certification of Enterprise Architects<br/>52.3.2 Specific Benefits<br/>52.4 Enterprise Architecture Role and Skill Categories<br/>52.4.1 Overview<br/>52.4.2 TOGAF Roles<br/>52.4.3 Categories of Skills<br/>52.4.4 Proficiency Levels<br/>52.5 Enterprise Architecture Role and Skill Definitions<br/>52.5.1 Generic Skills<br/>52.5.2 Business Skills & Methods<br/>52.5.3 Enterprise Architecture Skills<br/>52.5.4 Program or Project Management Skills<br/>52.5.5 IT General Knowledge Skills<br/>52.5.6 Technical IT Skills<br/>52.5.7 Legal Environment<br/>52.6 Generic Role and Skills of the Enterprise Architect<br/>52.6.1 Generic Role<br/>52.6.2 Characterization in Terms of the Enterprise Continuum<br/>52.6.3 Key Characteristics of an Enterprise Architect<br/>52.6.3.1 Skills and Experience in Producing Designs<br/>52.6.3.2 Extensive Technical Breadth, with Technical Depth in One or a Few Disciplines<br/>52.6.3.3 Method-Driven Approach to Execution<br/>52.6.3.4 Full Project Scope Experience<br/>52.6.3.5 Leadership<br/>52.6.3.6 Personal and Professional Skills<br/>52.6.3.7 Skills and Experience in One or More Industries<br/>52.7 Conclusions<br/>A. Glossary of Supplementary Definitions<br/>A.1 Access Control (AC)<br/>A.2 Ada<br/>A.3 Application Component<br/>A.4 Application Software<br/>A.5 Availability<br/>A.6 Batch Processing<br/>A.7 Business System<br/>A.8 Catalog<br/>A.9 Client<br/>A.10 COBIT<br/>A.11 Communications Network<br/>A.12 Communications Node<br/>A.13 Communications System<br/>A.14 Composite Application<br/>A.15 Configuration Management<br/>A.16 Connectivity Service<br/>A.17 Contract<br/>A.18 Control<br/>A.19 CxO<br/>A.20 Data Dictionary<br/>A.21 Data Element<br/>A.22 Data Entity<br/>A.23 Data Interchange Service<br/>A.24 Data Management Service<br/>A.25 Database<br/>A.26 Database Management System<br/>A.27 Directory Service<br/>A.28 Distributed Database<br/>A.29 Driver<br/>A.30 End User<br/>A.31 Enterprise Resource Planning (ERP) System<br/>A.32 Event<br/>A.33 External Environment Interface (EEI)<br/>A.34 FORTRAN<br/>A.35 Functional Decomposition<br/>A.36 Goal<br/>A.37 Guideline<br/>A.38 Hardware<br/>A.39 Human Computer Interface (HCI)<br/>A.40 Information Domain<br/>A.41 Information System (IS)<br/>A.42 Information System Service<br/>A.43 Interaction<br/>A.44 Interaction Model<br/>A.45 Interface<br/>A.46 ITIL<br/>A.47 Key Performance Indicator (KPI)<br/>A.48 Lifecycle<br/>A.49 Location<br/>A.50 Logical Application Component<br/>A.51 Logical Data Component<br/>A.52 Logical Technology Component<br/>A.53 Managing Successful Programs (MSP)<br/>A.54 Matrix<br/>A.55 Measure<br/>A.56 Metaview<br/>A.57 Multimedia Service<br/>A.58 Open Specifications<br/>A.59 Open System<br/>A.60 Operational Governance<br/>A.61 Operating System Service<br/>A.62 Packaged Services<br/>A.63 Physical Application Component<br/>A.64 Physical Data Component<br/>A.65 Physical Technology Component<br/>A.66 Portability<br/>A.67 Portfolio<br/>A.68 PRINCE2<br/>A.69 Process<br/>A.70 Product<br/>A.71 Profile<br/>A.72 Profiling<br/>A.73 Program<br/>A.74 Project<br/>A.75 Risk Management<br/>A.76 Scalability<br/>A.77 Security<br/>A.78 Server<br/>A.79 Service<br/>A.80 Service Quality<br/>A.81 SMART<br/>A.82 Supplier Management<br/>A.83 System<br/>A.84 System and Network Management Service<br/>A.85 System Stakeholder<br/>A.86 Technology Component<br/>A.87 Time Period<br/>A.88 Transaction<br/>A.89 Transaction Sequence<br/>A.90 Use-Case<br/>A.91 User<br/>A.92 User Interface Service<br/>B. Abbreviations<br/>INDEX |
| 520 ## - RESUMEN, ETC. | |
| Nota de sumario, etc. | TOGAF es un marco - un método detallado y un conjunto de herramientas de apoyo - para el desarrollo de una arquitectura empresarial, desarrollado por los miembros de El Foro Open Group Architecture. TOGAF Versión 9.1 es una actualización de mantenimiento de TOGAF 9, dirigiéndose a los comentarios planteados desde la introducción de TOGAF 9 en 2009. Conserva las características principales y la estructura de TOGAF 9, preservando así la inversión existente en TOGAF, y agrega más detalle y aclaración a lo que es ya probado. Puede ser utilizado libremente por cualquier organización que desee desarrollar una arquitectura de la empresa para su uso dentro de esa organización (sujeto a las Condiciones de Uso). Este libro se divide en siete partes. |
| 650 #0 - ASIENTO SECUNDARIO DE MATERIA--TÉRMINO DE MATERIA | |
| Nombre de materia o nombre geográfico como elemento de entrada | TOGAF |
| 9 (RLIN) | 23703 |
| 650 #0 - ASIENTO SECUNDARIO DE MATERIA--TÉRMINO DE MATERIA | |
| Nombre de materia o nombre geográfico como elemento de entrada | SOFTWARE DE CODIGO ABIERTO |
| 9 (RLIN) | 11137 |
| 650 #0 - ASIENTO SECUNDARIO DE MATERIA--TÉRMINO DE MATERIA | |
| 9 (RLIN) | 4687 |
| Nombre de materia o nombre geográfico como elemento de entrada | ARQUITECTURA DE COMPUTADORES |
| 942 ## - ELEMENTOS KOHA | |
| Fuente de clasificación o esquema de ordenación en estanterías | |
| Koha tipo de item | LIBRO - MATERIAL GENERAL |
| Disponibilidad | Mostrar en OPAC | Fuente de clasificación o esquema | Tipo de Descarte | Estado | Código de colección | Localización permanente | Localización actual | Localización en estanterías | Fecha adquisición | Proveedor | Forma de Adq | Precio normal de compra | Datos del ítem (Volumen, Tomo) | Número de Inventario | Préstamos totales | Signatura completa | Código de barras | Fecha última consulta | Fecha último préstamo | Número de ejemplar | Coste, precio de reemplazo | Propiedades de Préstamo KOHA | Programa Académico | Renovaciones totales |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Préstamo Normal | Colección General | Biblioteca Jorge Álvarez Lleras | Biblioteca Jorge Álvarez Lleras | Fondo general | 2016-02-17 | Amazon-444444001-OC21388 | Compra | 284488.00 | Ej. 2 | BIB0001746 | 3 | 004.22 T374t | 024755 | 2023-05-11 | 2023-02-13 | 2 | 292500.00 | LIBRO - MATERIAL GENERAL | Maestría en Gestión de la Información | |||||
| Préstamo Normal | Colección General | Biblioteca Jorge Álvarez Lleras | Biblioteca Jorge Álvarez Lleras | Fondo general | 2016-02-17 | Amazon-444444001-OC21388 | Compra | 284488.00 | Ej. 1 | BIB0001892 | 3 | 004.22 T374t | 024754 | 2017-09-30 | 2017-09-23 | 1 | 292500.00 | LIBRO - MATERIAL GENERAL | Maestría en Gestión de la Información | 2 |
AK. 45 No. 205 - 59, Autopista Norte.
PBX: +60(1) 668 3600 - Bogotá.