Cloned from: TOGAF9.1_Flashcard

Bookmark and Share

Front Back
TOGAF 9.1 Foundation Bulleted
TOGAF flash cards with answers in bulleted form.
Completed on July 12, 2013.
What is TOGAF?
- Open industry standard
- framework and method
- for enterprise architecture
TOGAF certification levels
- Level 1: TOGAF 9 Foundation
- Level 2: TOGAF 9 Certified
Why is certification important?
- Incentive for organizations to standardize
- Open method for EA
- Avoids lock-in to proprietary methods
- Makes EA a well recognized discipline
- Introduces rigor
Why become certified?
- commitment to EA as a discipline
- possess core knowledge of TOGAF and EA
- Open Group publishes you as certified
Program vision and principles:
- Openness: all countries
- Fairness: You have to pass examinations
- Market relevance: 2 market driven levels
- Learning support: Training courses
- Quality: Open group accredited
- Best practices: In certification industry
What is the basic content of TOGAF 9 Foundation
- Validation candidate knows TOGAF and EA
- Terminology, basic concepts, core principles
- Purpose of The 7 parts of the TOGAF document
- The ADM cycle: Architecture Development Method
What does TOGAF 9 Certified add to Foundation
- Validate candidate can also
- analyze and apply TOGAF
TOGAF foundation certification test characteristics
- 11 topics
- 40 questions
- One hour
- Passing is 22 correct (55%)
11 test components
- Basic Concepts (2)
- Core Concepts (2)
- Introduction to the ADM (3)
- The enterprise Continuum and Tools (4)
- ADM Phases (9)
- ADM Guidelines and Techniques (6)
- Architecture Governance (4)
- Architecture Views, Viewpoints, and Stakeholders (2)
- Building Blocks (2)
- ADM Deliverables (2)
- TOGAF Reference Models (2)
What is TOGAF
- TOGAF = The Open Group Architecture Framework
- Methods and tools for enterprise architecture
- Acceptance, production, use, and maintenance
- Based on an iterative process model
- Supported by best practices
- A re-usable set of architecture assets.
What is an Enterprise
- Collection of organizations with common goals
- Highest organizational level
- Covers all missions and functions
- Can extend to partners, suppliers, customers
- Crosses multiple systems and groups
Define Architecture (2 definitions)
1. Formal system description
- or detailed system plan as components
- to guide a system\'s implementation
2. Structure of components
- their inter-relationships
- principles and guidelines governing design
- evolution over time
Why do I need Enterprise Architecture
- Optimize processes across the enterprise
- Integrated environment
- Responsive to change
- Exploits IT to support business strategy
- Strategic context for IT evolution to needs
List business benefits of an EA
- More efficient
- Lower cost, faster ROI
- More agile
- Shared capabilities and reuse
- Interoperability
- Security
- Reduced complexity
- Reduced risk of failure
- Better and faster procurement
What is an architecture framework
- Foundational structure(s) to develop architectures
- Describe a method for designing a target state
- Describes architecture using building blocks
- Provides set of tools and common vocabulary
- Includes recommended standards, compliant products
to implement building blocks
Why do I need a framework for EA
- Speed and simplify architecture development
- Ensure coverage of the designed solution
- Allow for future growth
- Assure solution responds to business needs
- Comply with regulations
Why is TOGAF suitable as an EA framework
- Developed by 300 leading IT companies
- TOGAF provides:
-- consistent architectures
-- reflect stakeholder needs
-- employ best practice
-- reduces risks
-- considers current and future needs
List the 4 architecture domains
- Business
- Data
- Application
- Technology
Business Architecture domain covers
- Business strategy
- Business Governance
- Business Organization
- Key business processes
Data Architecture domain covers
- Logical and physical data asset structure
- Data management resources.
Application Architecture domain covers
- Blueprint for deployed application systems
- Interactions of systems
- Relationships to core business processes
Technology Architecture domain covers
- Software and hardware capabilities
- Support for business, data, application services
- Includes
-- IT infrastructure
-- middleware
-- networks
-- communications
-- processing
-- standards
TOGAF contains (list the 7 parts)
1: Introduction
2: Architecture Development Method
3: ADM Guidelines and Techniques
4: Architecture Content Framework
5: Enterprise Continuum and Tools
6: TOGAF Reference Models
7: Architecture Capability Framework
Name and describe TOGAF Part I
1. Introduction
- Key concepts of enterprise architecture
- TOGAF approach
- definitions of terms
- release notes + version changes
Name and describe TOGAF Part II
2. Architecture Development Method (ADM)
- Process to derive an EA to address business needs
- The major component of TOGAF
- Architecture development phases in a cycle
- Describes each phase:
-- Objectives
-- Approach
-- Inputs
-- Steps
-- Outputs
Name and describe TOGAF Part III
3. ADM Guidelines and Techniques
- Guidelines: Address adapting the ADM to you
-- Adaptation of ADM for usage scenarios
-- E.g., Use of iteration, security
- Techniques: Tasks to support the use of the ADM
-- Defining principles
-- Business scenarios
-- Gap analysis
-- Migration planning
-- Risk management
Name and describe TOGAF Part IV
4. Architecture Content Framework
- Detailed model of architectural work products:
-- Stores the deliverables you create
-- Stores artifacts within deliverables
-- Stores Architectural building blocks (ABB)
-- Stores Solution building blocks (SBB)
- Provides an overview of typical deliverables
Name and describe TOGAF Part V
5. Enterprise Continuum & Tools
- Model for structuring a virtual repository
- Methods for classifying artifacts
- Shows evolution of artifacts
- Shows how artifacts are used and reused
- Based on industry and enterprise solutions in use
Name and describe TOGAF Part VI
6. TOGAF Reference Models (2)
- TRM - TOGAF Reference Model
-- A Foundation Architecture
-- Generic services foundations for ABBs
- IIIRM - Integrated Information Infrastructure Reference Model
-- Helps design architectures based on TRM
-- A Common Systems Architecture
-- Supports \"Boundaryless information flow\"
Name and describe TOGAF Part VII
7. Architecture Capability Framework
- Address staff and resource management
- Set of resources, guidelines, templates
- Helps architect establish architecture practice
List some characteristics of the ADM
- Core of TOGAF
- A method of deriving an organization\'s EA
- Develops content, transitioning, and governance
- An iterative cycle responding to business needs
List the 10 ADM phases (P, R, A-H)
- P: Preliminary phase
- R: Requirements management
- A: Architecture vision
- B: Business architecture
- C: Information system architectures
- D: Technology architecture
- E: Opportunities and solutions
- F: Migration planning
- G: Implementation governance
- H: Architecture change management
Name and describe ADM Preliminary Phase
P: Preliminary phase
- Prepare to create an Architectural Capability
- Customization + selection of TOGAF artifacts
- Determine other frameworks to use
- Definition of Architecture Principles
Name and describe ADM Requirements Management
R: Requirements Management
- Every stage is based on requirements
- Every stage validates requirements
- Requirements are fed in/out of each phase
- Phases address, dispose, and prioritize reqmts
Name and describe ADM Phase A
A: Architecture vision
- First phase of an ADM cycle
- Define scope, constraints, expectations
- Identify stakeholders
- Create and approve Architecture Vision
- Create Statement of Architecture Work
- Business, data, app, tech archs at 0.1 level
Name and describe ADM Phase B
B: Business architecture
- Develop architecture in the business domain
- Develop baseline, target architectures, gaps
- Select and develop Architecture Viewpoints
- Select relevant tools and techniques
Name and describe ADM Phase C
C: Information system architectures
- Develop architecture in the data, app domains
- Develop baseline, target architectures, gaps
- To support the business architecture
Name and describe ADM Phase D
D: Technology architecture
- Develop architecture in the technology domain
- Develop baseline, target architectures, gaps
- Physical realization of architectural solution:
- Map hardware+software for architectural components
Name and describe ADM Phase E
E: Opportunities and solutions
- Initial implementation plan, delivery vehicles
- Identify major implementation projects
- Group projects into work packages
- Organize solution building blocks (SBB)
- If incremental, identify transition architectures
- Delivers target architecture from phases A-D
Name and describe ADM Phase F
F: Migration planning
- Detailed Implementation and migration plans
- To move from baseline to target architecture\\
- Map out transition architectures, if needed
Name and describe ADM Phase G
G: Implementation Governance
- Architectural oversight of implementation
- Prepare, issue, govern Architecture Contracts
- Govern implementation and deployment
- Ensure conformance with target architecture
Name and describe ADM Phase H
H: Architecture Change Management
- Continual monitoring and change management
- Ensure architecture responds to needs
- Ensure maximum business value of architecture
- Procedures for managing change to target
Three categories of ADM work products
- Deliverables
- Artifacts
- Building blocks
Deliverables are
- Work contractually specified
- Reviewed, agreed, signed off by stakeholders
- Archived or stored in an Architecture Repository
- Reference model, standard, or snapshot
Artifacts are
- Describes an aspect of the architecture
- Components of architectural deliverables
Building blocks are
- Components of business, IT, architecture
- Can be combined with other building blocks
- Deliver architectures and solutions
- Described by artifacts or building blocks
List/summarize 3 kinds of artifacts
- Catalogs: lists of things
- Matrices: Show relationships between things
- Diagrams: Pictures or illustrations
List some examples of artifacts
- Requirements catalog
- Business interaction matrix
- Use case diagram
- Network diagram
- Server specification
List/summarize 2 kinds of building blocks
- ABB: Architectural building block
-- Describes a required capability
- SBB: Solution building block
-- Implements an architectural capability
x of y cards Next > >> >|