ORPP logo
Image from Google Jackets

Modeling Enterprise Architecture with TOGAF : A Practical Guide Using UML and BPMN.

By: Contributor(s): Material type: TextTextSeries: The MK/OMG Press SeriesPublisher: San Diego : Elsevier Science & Technology, 2014Copyright date: ©2014Edition: 1st edDescription: 1 online resource (305 pages)Content type:
  • text
Media type:
  • computer
Carrier type:
  • online resource
ISBN:
  • 9780124199958
Subject(s): Genre/Form: Additional physical formats: Print version:: Modeling Enterprise Architecture with TOGAFDDC classification:
  • 658.4/0380285
LOC classification:
  • TK5105.52.D474 2014
Online resources:
Contents:
Front Cover -- Modeling Enterprise Architecture with TOGAF®: A Practical Guide Using UML and BPMN -- Copyright -- Contents -- Preface -- Aim of this book -- Who is this book for? -- Acknowledgments -- Foreword -- Chapter 1: TOGAF®: General Presentation -- 1.1. What is TOGAF? -- 1.1.1. Positioning and history -- 1.1.2. ``A´´ for Enterprise Architecture -- 1.1.3. ``F´´ for framework -- 1.1.4. The TOGAF document -- 1.2. TOGAF: Key points -- 1.2.1. ADM and the TOGAF crop circle diagram -- 1.2.2. Architecture transformation -- From baseline architecture to target architecture -- Transforming architecture -- Transition architectures and increments (states) -- Gap analysis -- Impact evaluation -- The concept of capability -- 1.2.3. Architecture in TOGAF -- Architecture and description of architecture -- Domains and phases -- Architecture repository -- Architecture and solution -- 1.2.4. Goals, constraints, and requirements -- 1.2.5. Stakeholders and the human factor -- Managing stakeholders -- Transformation Readiness Assessment -- Views and viewpoints -- 1.2.6. Architecture strategy, governance, and principles -- A strategic view of enterprise architecture -- Governance -- Architecture principles -- 1.3. Summary -- 1.4. Using TOGAF -- 1.4.1. Adapting the framework -- 1.4.2. TOGAF: One framework among many? -- TOGAF and DODAF -- TOGAF and ITIL -- TOGAF and CMMI -- 1.5. Fundamental concepts -- Chapter 2: The ADM Method -- 2.1. The ADM cycle -- 2.1.1. The breakdown into phases -- 2.1.2. The typical path -- 2.2. The phases of the ADM -- 2.2.1. The preliminary phase -- 2.2.2. Phase A (vision) -- 2.2.3. Phases B, C, and D (Elaboration of Business, Information System, and Technology Architectures) -- Phase B (business architecture) -- Phase C (information systems architecture) -- Phase D (technology architecture).
2.2.4. Phases E and F (opportunities and solutions, migration planning) -- 2.2.5. Phases G and H (implementation governance, architecture change management) -- 2.2.6. Requirements management -- What is a requirement? -- Functional requirements and nonfunctional requirements -- Centralized requirements management -- Requirements management techniques -- Business scenarios -- 2.3. Iterations -- 2.3.1. Iteration cycles -- 2.3.2. Priority to target architecture or baseline architecture -- 2.4. ADM techniques and guidelines -- 2.4.1. The different techniques -- 2.4.2. Techniques in ADM phases -- 2.5. Fundamental concepts -- Chapter 3: The Components of TOGAF Architecture -- 3.1. Architecture components -- 3.1.1. Artifacts, deliverables, and building blocks -- 3.1.2. Using other content frameworks -- 3.2. The metamodel -- 3.2.1. The ``TOGAF core metamodel´´ -- 3.2.2. Metamodel extensions -- 3.2.3. Conceptual, logical, and physical -- 3.2.4. Relationship to ADM phases -- 3.3. Artifacts -- 3.3.1. Viewpoints and views -- 3.3.2. Catalogs, matrices, and diagrams -- 3.3.3. The catalog of TOGAF views -- 3.3.4. Tools and languages -- 3.4. Building blocks -- 3.4.1. The game of building -- 3.4.2. Architecture building blocks and solution building blocks -- 3.5. Deliverables -- 3.5.1. Description and use -- 3.5.2. Deliverables and ADM phases -- Deliverables linked to architecture work management -- Deliverables linked to principles, goals, and requirements -- Architecture description deliverables -- Deliverables dedicated to architecture transition -- Deliverables linked to implementation -- 3.6. Fundamental concepts -- Chapter 4: The Repository and Governance -- 4.1. The architecture repository -- 4.1.1. The repository and the ADM -- 4.1.2. The structure of the repository -- 4.1.3. The landscape -- 4.1.4. Classification plan: Architecture continuum.
4.1.5. TOGAF reference models -- The technical reference model -- The integrated information infrastructure reference model -- 4.1.6. Repository tooling -- 4.2. Architecture governance -- 4.2.1. Architecture management -- 4.2.2. The architecture board -- 4.2.3. The architecture contract -- 4.2.4. Compliance reviews -- 4.2.5. ``Good´´ governance -- 4.3. Fundamental concepts -- Chapter 5: Key Modeling Techniques -- 5.1. Models: Benefits, uses, and characteristics -- 5.1.1. Definition -- What is a model? -- A universal need -- History -- 5.1.2. Usefulness of a model -- Understanding and thinking about a problem -- Communicating, sharing, and collaborating -- Planning and simulating -- Producing -- 5.1.3. Characteristics of models -- Abstraction -- Standardization -- Formal or informal models -- 5.1.4. Limitations of models -- 5.2. The concept of viewpoints -- 5.2.1. The angle from which a problem is looked at -- 5.2.2. View and viewpoint: Definition -- 5.2.3. Usefulness of views -- 5.2.4. TOGAF viewpoints -- 5.3. Special role played by diagrams -- 5.3.1. Models and diagrams -- 5.3.2. Diagrams for communicating -- 5.4. Consistency and traceability -- 5.4.1. What is a ``good´´ model? -- 5.4.2. Traceability links -- 5.4.3. Using traceability in enterprise architecture -- 5.5. Architecture repository -- 5.6. Risks and main difficulties -- 5.6.1. Limitations inherent to any model -- Intrinsic limitations of models -- A partial description of the problem -- Confining modeling work -- Making a model a reference -- 5.6.2. Usefulness and support: Major criteria -- 5.6.3. ``Bottom-up´´ or ``top-down´´: Two limited techniques -- 5.7. Repository governance -- 5.8. Tools and languages -- 5.8.1. Modeling tools: A necessary medium -- 5.8.2. Tools available in the marketplace -- 5.8.3. Summary of the appropriate use of modeling techniques -- 5.9. Fundamental concepts.
Chapter 6: Introduction to TOGAF Models -- 6.1. TOGAF artifacts -- 6.1.1. Using models to realize artifacts -- 6.1.2. Preliminary phase: Determining useful artifacts in the context of the enterprise -- 6.1.3. Structuring artifacts -- 6.1.4. Organization of the model -- 6.2. UML and BPMN for TOGAF modeling -- 6.2.1. Choosing a representation mode for TOGAF models -- 6.2.2. Modeling standards for TOGAF -- Panorama of standards that are useful for TOGAF -- The UML standard -- Extending and adapting UML: The profile mechanism -- The BPMN standard -- Adapting standards to TOGAF: The Enterprise Architecture Profile -- 6.3. The ``Discount Travel´´ enterprise -- 6.4. Fundamental concepts -- Chapter 7: Models for Phase A: Vision -- 7.1. Phase A artifacts -- 7.1.1. Nature of phase A artifacts: Vision -- 7.1.2. Essential concepts used in models -- 7.2. Stakeholder matrix -- 7.3. Artifacts linked to goals -- 7.3.1. Goal analysis -- Goals: A companys reason for being -- Goals in phase A -- Goals and objectives -- Identifying goals -- Assigning goals and objectives -- Goal graph -- Defining priorities for goals -- Summary of best practices for defining goals -- 7.3.2. The ``Goal diagram´´ artifact -- Description of the artifact -- 7.3.3. The ``Goal catalog´´ artifact -- 7.4. Artifacts linked to requirements -- 7.4.1. The ``Requirements catalog´´ artifact -- Description of the artifact -- Characteristics of a requirement -- Properties that must be verified by a requirement -- Goals and requirements -- 7.4.2. The ``Requirement diagram´´ artifact -- Description of the artifact -- 7.5. Artifacts linked to business processes -- 7.5.1. Modeling business processes in phase A -- 7.5.2. The ``Event diagram´´ artifact -- Description of the artifact -- The enterprises key business processes -- Business events and processes.
The ``Event diagram´´ artifact (intermediate view) -- The ``Event diagram´´ artifact (view focused on a process) -- Business process catalog -- 7.6. The ``Solution concept diagram´´ artifact -- 7.6.1. Definition of the artifact -- 7.6.2. Providing the envisaged solution with an orientation -- 7.7. The ``Value chain diagram´´ artifact -- 7.7.1. Definition of the artifact -- 7.7.2. Contribution of business functions to value -- 7.8. Fundamental concepts -- Chapter 8: Models for Phase B: Business Architecture -- 8.1. Phase B artifacts -- 8.1.1. Nature of Phase B artifacts: Business architecture -- 8.1.2. Essential concepts used in business architecture models -- 8.2. The ``business dictionary´´ artifact -- 8.2.1. Description of the artifact -- 8.2.2. Terminology: The cornerstone of business knowledge -- 8.3. Artifacts linked to enterprise organization -- 8.3.1. Concepts that support enterprise organization -- 8.3.2. Actors and roles -- 8.3.3. The ``actor organization diagram´´ artifact -- Description of the artifact -- The actor model clarifies enterprise functioning -- Actor-centric view: Definition of positions -- Actor catalog -- 8.3.4. The ``organization decomposition diagram-flows´´ artifact -- 8.3.5. The ``organization decomposition diagram-role allocation´´ artifact -- 8.3.6. The ``location organization diagram´´ artifact -- 8.3.7. The ``location diagram´´ artifact -- 8.4. Artifacts linked to enterprise functions and services -- 8.4.1. The ``functional decomposition diagram´´ artifact -- Description of the artifact -- Business function -- Summarized representation of the enterprises capacities -- 8.4.2. The ``Goal/Objective/Service diagram´´ artifact -- Description of the artifact -- Business service -- 8.5. Artifacts linked to business processes -- 8.5.1. Key business processes of the enterprise -- 8.5.2. The ``process flow diagram´´ artifact.
Description of the artifact.
Tags from this library: No tags from this library for this title. Log in to add tags.
Star ratings
    Average rating: 0.0 (0 votes)
No physical items for this record

Front Cover -- Modeling Enterprise Architecture with TOGAF®: A Practical Guide Using UML and BPMN -- Copyright -- Contents -- Preface -- Aim of this book -- Who is this book for? -- Acknowledgments -- Foreword -- Chapter 1: TOGAF®: General Presentation -- 1.1. What is TOGAF? -- 1.1.1. Positioning and history -- 1.1.2. ``A´´ for Enterprise Architecture -- 1.1.3. ``F´´ for framework -- 1.1.4. The TOGAF document -- 1.2. TOGAF: Key points -- 1.2.1. ADM and the TOGAF crop circle diagram -- 1.2.2. Architecture transformation -- From baseline architecture to target architecture -- Transforming architecture -- Transition architectures and increments (states) -- Gap analysis -- Impact evaluation -- The concept of capability -- 1.2.3. Architecture in TOGAF -- Architecture and description of architecture -- Domains and phases -- Architecture repository -- Architecture and solution -- 1.2.4. Goals, constraints, and requirements -- 1.2.5. Stakeholders and the human factor -- Managing stakeholders -- Transformation Readiness Assessment -- Views and viewpoints -- 1.2.6. Architecture strategy, governance, and principles -- A strategic view of enterprise architecture -- Governance -- Architecture principles -- 1.3. Summary -- 1.4. Using TOGAF -- 1.4.1. Adapting the framework -- 1.4.2. TOGAF: One framework among many? -- TOGAF and DODAF -- TOGAF and ITIL -- TOGAF and CMMI -- 1.5. Fundamental concepts -- Chapter 2: The ADM Method -- 2.1. The ADM cycle -- 2.1.1. The breakdown into phases -- 2.1.2. The typical path -- 2.2. The phases of the ADM -- 2.2.1. The preliminary phase -- 2.2.2. Phase A (vision) -- 2.2.3. Phases B, C, and D (Elaboration of Business, Information System, and Technology Architectures) -- Phase B (business architecture) -- Phase C (information systems architecture) -- Phase D (technology architecture).

2.2.4. Phases E and F (opportunities and solutions, migration planning) -- 2.2.5. Phases G and H (implementation governance, architecture change management) -- 2.2.6. Requirements management -- What is a requirement? -- Functional requirements and nonfunctional requirements -- Centralized requirements management -- Requirements management techniques -- Business scenarios -- 2.3. Iterations -- 2.3.1. Iteration cycles -- 2.3.2. Priority to target architecture or baseline architecture -- 2.4. ADM techniques and guidelines -- 2.4.1. The different techniques -- 2.4.2. Techniques in ADM phases -- 2.5. Fundamental concepts -- Chapter 3: The Components of TOGAF Architecture -- 3.1. Architecture components -- 3.1.1. Artifacts, deliverables, and building blocks -- 3.1.2. Using other content frameworks -- 3.2. The metamodel -- 3.2.1. The ``TOGAF core metamodel´´ -- 3.2.2. Metamodel extensions -- 3.2.3. Conceptual, logical, and physical -- 3.2.4. Relationship to ADM phases -- 3.3. Artifacts -- 3.3.1. Viewpoints and views -- 3.3.2. Catalogs, matrices, and diagrams -- 3.3.3. The catalog of TOGAF views -- 3.3.4. Tools and languages -- 3.4. Building blocks -- 3.4.1. The game of building -- 3.4.2. Architecture building blocks and solution building blocks -- 3.5. Deliverables -- 3.5.1. Description and use -- 3.5.2. Deliverables and ADM phases -- Deliverables linked to architecture work management -- Deliverables linked to principles, goals, and requirements -- Architecture description deliverables -- Deliverables dedicated to architecture transition -- Deliverables linked to implementation -- 3.6. Fundamental concepts -- Chapter 4: The Repository and Governance -- 4.1. The architecture repository -- 4.1.1. The repository and the ADM -- 4.1.2. The structure of the repository -- 4.1.3. The landscape -- 4.1.4. Classification plan: Architecture continuum.

4.1.5. TOGAF reference models -- The technical reference model -- The integrated information infrastructure reference model -- 4.1.6. Repository tooling -- 4.2. Architecture governance -- 4.2.1. Architecture management -- 4.2.2. The architecture board -- 4.2.3. The architecture contract -- 4.2.4. Compliance reviews -- 4.2.5. ``Good´´ governance -- 4.3. Fundamental concepts -- Chapter 5: Key Modeling Techniques -- 5.1. Models: Benefits, uses, and characteristics -- 5.1.1. Definition -- What is a model? -- A universal need -- History -- 5.1.2. Usefulness of a model -- Understanding and thinking about a problem -- Communicating, sharing, and collaborating -- Planning and simulating -- Producing -- 5.1.3. Characteristics of models -- Abstraction -- Standardization -- Formal or informal models -- 5.1.4. Limitations of models -- 5.2. The concept of viewpoints -- 5.2.1. The angle from which a problem is looked at -- 5.2.2. View and viewpoint: Definition -- 5.2.3. Usefulness of views -- 5.2.4. TOGAF viewpoints -- 5.3. Special role played by diagrams -- 5.3.1. Models and diagrams -- 5.3.2. Diagrams for communicating -- 5.4. Consistency and traceability -- 5.4.1. What is a ``good´´ model? -- 5.4.2. Traceability links -- 5.4.3. Using traceability in enterprise architecture -- 5.5. Architecture repository -- 5.6. Risks and main difficulties -- 5.6.1. Limitations inherent to any model -- Intrinsic limitations of models -- A partial description of the problem -- Confining modeling work -- Making a model a reference -- 5.6.2. Usefulness and support: Major criteria -- 5.6.3. ``Bottom-up´´ or ``top-down´´: Two limited techniques -- 5.7. Repository governance -- 5.8. Tools and languages -- 5.8.1. Modeling tools: A necessary medium -- 5.8.2. Tools available in the marketplace -- 5.8.3. Summary of the appropriate use of modeling techniques -- 5.9. Fundamental concepts.

Chapter 6: Introduction to TOGAF Models -- 6.1. TOGAF artifacts -- 6.1.1. Using models to realize artifacts -- 6.1.2. Preliminary phase: Determining useful artifacts in the context of the enterprise -- 6.1.3. Structuring artifacts -- 6.1.4. Organization of the model -- 6.2. UML and BPMN for TOGAF modeling -- 6.2.1. Choosing a representation mode for TOGAF models -- 6.2.2. Modeling standards for TOGAF -- Panorama of standards that are useful for TOGAF -- The UML standard -- Extending and adapting UML: The profile mechanism -- The BPMN standard -- Adapting standards to TOGAF: The Enterprise Architecture Profile -- 6.3. The ``Discount Travel´´ enterprise -- 6.4. Fundamental concepts -- Chapter 7: Models for Phase A: Vision -- 7.1. Phase A artifacts -- 7.1.1. Nature of phase A artifacts: Vision -- 7.1.2. Essential concepts used in models -- 7.2. Stakeholder matrix -- 7.3. Artifacts linked to goals -- 7.3.1. Goal analysis -- Goals: A companys reason for being -- Goals in phase A -- Goals and objectives -- Identifying goals -- Assigning goals and objectives -- Goal graph -- Defining priorities for goals -- Summary of best practices for defining goals -- 7.3.2. The ``Goal diagram´´ artifact -- Description of the artifact -- 7.3.3. The ``Goal catalog´´ artifact -- 7.4. Artifacts linked to requirements -- 7.4.1. The ``Requirements catalog´´ artifact -- Description of the artifact -- Characteristics of a requirement -- Properties that must be verified by a requirement -- Goals and requirements -- 7.4.2. The ``Requirement diagram´´ artifact -- Description of the artifact -- 7.5. Artifacts linked to business processes -- 7.5.1. Modeling business processes in phase A -- 7.5.2. The ``Event diagram´´ artifact -- Description of the artifact -- The enterprises key business processes -- Business events and processes.

The ``Event diagram´´ artifact (intermediate view) -- The ``Event diagram´´ artifact (view focused on a process) -- Business process catalog -- 7.6. The ``Solution concept diagram´´ artifact -- 7.6.1. Definition of the artifact -- 7.6.2. Providing the envisaged solution with an orientation -- 7.7. The ``Value chain diagram´´ artifact -- 7.7.1. Definition of the artifact -- 7.7.2. Contribution of business functions to value -- 7.8. Fundamental concepts -- Chapter 8: Models for Phase B: Business Architecture -- 8.1. Phase B artifacts -- 8.1.1. Nature of Phase B artifacts: Business architecture -- 8.1.2. Essential concepts used in business architecture models -- 8.2. The ``business dictionary´´ artifact -- 8.2.1. Description of the artifact -- 8.2.2. Terminology: The cornerstone of business knowledge -- 8.3. Artifacts linked to enterprise organization -- 8.3.1. Concepts that support enterprise organization -- 8.3.2. Actors and roles -- 8.3.3. The ``actor organization diagram´´ artifact -- Description of the artifact -- The actor model clarifies enterprise functioning -- Actor-centric view: Definition of positions -- Actor catalog -- 8.3.4. The ``organization decomposition diagram-flows´´ artifact -- 8.3.5. The ``organization decomposition diagram-role allocation´´ artifact -- 8.3.6. The ``location organization diagram´´ artifact -- 8.3.7. The ``location diagram´´ artifact -- 8.4. Artifacts linked to enterprise functions and services -- 8.4.1. The ``functional decomposition diagram´´ artifact -- Description of the artifact -- Business function -- Summarized representation of the enterprises capacities -- 8.4.2. The ``Goal/Objective/Service diagram´´ artifact -- Description of the artifact -- Business service -- 8.5. Artifacts linked to business processes -- 8.5.1. Key business processes of the enterprise -- 8.5.2. The ``process flow diagram´´ artifact.

Description of the artifact.

Description based on publisher supplied metadata and other sources.

Electronic reproduction. Ann Arbor, Michigan : ProQuest Ebook Central, 2024. Available via World Wide Web. Access may be limited to ProQuest Ebook Central affiliated libraries.

There are no comments on this title.

to post a comment.

© 2024 Resource Centre. All rights reserved.