Windsor Software

Windsor Software Model™ of the
TOGAF® Architecture Development Method (ADM)
 
 
TOGAF ADM Preliminary Phase - Outputs Phase A - Architecture Vision - Outputs Phase B - Business Architecture - Outputs Phase C - Information Systems Architecture - Outputs Phase D - Technology Architecture - Outputs Phase E - Opportunities and Solutions - Outputs Phase F - Migration Planning - Outputs Phase G - Implementation Governance - Outputs Phase H - Change Management - Outputs Requirements Management

ADM Phases & Outputs - Phase B - Business Architecture:

  • Refined and updated versions of the Architecture Vision phase deliverables, where applicable, including:
  • Draft Architecture Definition Document (see Part IV, 36.2.3 Architecture Definition Document), including:
    • Baseline Business Architecture, Version 1.0 (detailed), if appropriate
  • Target Business Architecture, Version 1.0 (detailed), including:
    • Organization structure - identifying business locations and relating them to organizational units
    • Business goals and objectives - for the enterprise and each organizational unit
    • Business functions - a detailed, recursive step involving successive decomposition of major functional areas into sub-functions
    • Business services - the services that the enterprise and each enterprise unit provides to its customers, both internally and externally
    • Business processes, including measures and deliverables
    • Business roles, including development and modification of skills requirements
    • Business data model
    • Correlation of organization and functions - relate business functions to organizational units in the form of a matrix report
    • Views corresponding to the selected viewpoints addressing key stakeholder concerns
  • Draft Architecture Requirements Specification (see Part IV, 36.2.6 Architecture Requirements Specification), including such Business Architecture requirements as:
    • Gap analysis results
    • Technical requirements - identifying, categorizing, and prioritizing the implications for work in the remaining architecture domains; for example, by a dependency/priority matrix (for example, guiding trade-off between speed of transaction processing and security); list the specific models that are expected to be produced (for example, expressed as primitives of the Zachman Framework)
    • Updated business requirements
  • Business Architecture components of an Architecture Roadmap (see Part IV, 36.2.7 Architecture Roadmap)
Click on any Phase to learn about ADM Methods
 
See our new book "Building Enterprise Architecture"
This book describes a new EA framework and
methodology that fills in where TOGAF leaves off.
 
 
© Copyright Windsor Software 2014. All Rights Reserved.