What is Enterprise – collection of organizations that share a common set of Goals

» What is an Architecture - An Architecture is the fundamental concepts or properties of a

system in its environment embodied in:
– its elements,
– their relationships to each other and the environment,
and the principles governing its design and evolution.

Architecture in the Context of TOGAF

1. A formal description of a system, or a detailed plan of the system at component level to
guide its implementation

2. The structure of components, their inter-relationships, and the principles and guidelines
governing their design and evolution over time

What is Enterprise Architecture - A conceptual blueprint that defines the structure and
operation of an organization. The intent of an enterprise architecture is to determine how an
organization can most effectively achieve its current and future objectives.
What is TOGAF – An Enterprise Architecture framework
TOGAF 9.2 COMPONENTS
1. ADM
– iterative process/method to develop organization specific architectures
2. ADM GUIDELINES AND TECHNIQUES
3. CONTENT FRAMEWORK
– Meta model - structure for inputs and outputs of ADM
- Work products (Deliverables, Artifacts, Building Blocks), their purpose and templates
to create them
4. ENTERPRISE CONTINUUM
- Taxonomy (categorization) of architecture and solution assets based on their
reusability
- Foundation, Common Systems, Industry and Organization Specific
5. CAPABILITY FRAMEWORK
- Guidelines and templates to establish an architecture function within enterprise
- Skills, Roles, Processes, Governance and Architecture Repository

Architecture Development Method (ADM)

Phases of ADM
- Preliminary
o Organization context
 Purpose of org (Mission stmt)
 Drivers, goals and objectives
 Maturity assessment
 ACMM

o Establish Arch capability

 Governance
 Establish arch board
 Establish the EA team (Organization model)
 Select and implement EA tool

o Define arch principles

 Rules and guidelines that tell how an organization fulfils its mission
 Can be used for selecting technology assets
 Four parts
 Name
 Statement
 Rationale (business benefits)– to prioritize
 Implications (Highlight requirements for the principles and
consequences) – what is in it for the stakeholders
 Five qualities
 Understandable – clear and unambiguous
 Robust – enables to take better decisions
 Complete – address all aspects of IT
 Consistent – should not be contradictory
 Stable – long lasting
o Tailor the framework
 Terminology – provide glossary
 Process – adapting ADM
 Content – Metamodel extensions
 Governance
 Process modeling
 Data
 Services
 Infrastructure consolidation
 Motivation
o Outputs
 Principles
  Request for arch work

- Phase A : Architecture Vision

o Establish the project
o Identify stakeholders and their concerns
 Stakeholder mgmt.
 Business scenario
 Identify and understand requirements
 Steps
o Problem stmt.
o Environment
o Objectives
o Human actors
o Computer actors
o Roles and responsibilities
o Refine
o Confirm goals, drivers and constraints
o Define capabilities
 Value chain diagram
 Capability based planning – which emphasizes on business outcomes
 (radar or spider web diagram)
o Business transformation readiness assessment
 Identify readiness factors
 Maturity model for factor
 Risks
 Initial – prior to mitigation action
 Residual – remaining risk after mitigation
o Scope
 Breadth (extent of enterprise)
 Depth ( level of detail )
 Strategic
 Segment
 Capability
 Time
 Arch domains
 Business
 Data
 Application
 Technology
o Confirm principles
o Define vision
 Business scenario
  Solution concept dia
 Building blocks
o reusable components
o Package of functionality
o Interoperability
o Target arch value proposition and kpi
o Risk mgmt
o Output
 Statement of arch work
 Scope and approach
- Steps for four arch
o Select reference models, viewpoints and tools
o Define baseline arch
o Define target arch
o Gap analysis
o Roadmap components
o Impact analysis
o Stakeholder review
o Finalize arch
o Arch definition doc and requirements spec

- Business arch
o Outputs
 Organization structure
 Business capabilities
 Value stream
 Business functions
 Business services
 Business processes
 Business roles
 Business rules
- Information system arch
o Data
 Data entities
o Application
 Applications or services (III-RM is used to develop App Arch)
- Technology arch
o Infrastructure (Technology) services (TRM is used to develop Tech Arch)
o Service qualities
- Opportunities and solutions
 o Implementation factor assessment and deduction matrix
o Business constraints
o Consolidated gaps, solutions and dependencies matrix
o Requirements from a functional perspective
o Interoperability
o Dependencies
o Business transformation readiness assessment
o Implementation and migration strategy
o Identify work packages
o Transition arch
o Arch roadmap and implementation and migration strategy
o 0.1 – high level outline
o Outputs
 Transition arch
- Migration planning
o Confirm mgmt interactions
o Business value
o Estimate cost
 Cost – benefit analysis
o Prioritize migration projects
o Confirm arch roadmap, ADD, ARS, Vision
o Architecture definition increments table (Roadmap) and Transition architecture
state evolution table (Roadmap for Technology services (TRM))
o Complete implementation and migration plan
o Complete arch development cycle and document lessons learned
o Outputs
 Formally reviewed detailed arch (1.0)
- Implementation governance
o Confirm scope and priorities
o Resources and skills
o Guide solutions deployment
o Perform EA compliance
 Project impact assessment
 Compliance review
 Catch errors early
 Following standards
 Standards need modification
 Identity platform/technology services
 Technical readiness
  Procurement activities
 Resource sharing
 Compliance terminology
 Irrelevant
 Consistent
 Compliant
 Conformant
 Fully conformant
 Non-conformant
o Implement business and IT operations
o Post implementation review
- Change mgmt
o Achieve original target business value
o Three categories
 Simplification
 Incremental
 Rearchitecting
o Implement business monitoring tools
o Manage risk
o Analysis for arch change mgmt
o Develop changed requirements
o Governance process
- Requirements mgmt
o Store requirements in and out of ADM phases
o

Content framework
- Metamodel – structure for inputs and outputs of ADM phases
- Work products
o Deliverables – contractual outputs
o Artifacts
 Catalogs – list of things
 Matrices - relationship between two things
 Diagram – pictorial representation
o Building blocks
- Enterprise continuum
classification of architecture and solution assests based on their reusability
o Foundation - TRM
o Common systems – III-RM
 o Industry
o Organization specific
- Arch repository
o Physical storage of arch assests
o Parts
 Arch meta model
 Arch method (ADM)
 Content meta model
 Reference library – guidelines and templates to create new arch
 Standards information base
 List of specification
 Governance log – stores the outputs of governance activities
 Architecture capability – parameters, skills, org structure for arch
governance
 Architecture landscape – snap shot of enterprise
- Strategic (enterprise)
- Segment (program)
- Capability (project)
reference models
- TRM
o Foundation arch – building blocks and corresponding standards
- III-RM – common system – Boundaryless information flow
Arch capability framework
- Guidelines and tech to establish an arch function
- Skills
- Processes
- Repository
View – representation of a system from perspective of related set of concerns
Viewpoint – perspective from a view is taken
Stakeholder – people, teams or organization who have concerns about a system or architecture
Concerns – areas of interest that are crucially important to stakeholders for the acceptance of
system