Overview
OVERVIEW
Enterprise Architecture certification provides validation that an individual has the knowledge, comprehension, and ability to analyze and apply the standard to developing, sustaining, and using an Enterprise Architecture.
This course provides a variety of tools, building blocks and resources that facilitate the process and enables the design of Enterprise Architecture across four domains; Business, Data, Applications and Technology. It offers the means of uniting different methodologies in business planning, It Architecture and project management under one common framework.
Upon completion, participant can enroll in the following certification exam:
Enterprise Architecture Part 1
This provides validation that the candidate has gained knowledge of the terminology and basic concepts and understands the core principles of Enterprise Architecture
Enterprise Architecture Part 2
This certification provides validation that in addition to knowledge and comprehension the candidate is able to analyse and apply knowledge
Audience Profile
All Architects, IT Governance teams, Middle Management to Senior Management
Prerequisities
None
At Course Completion
• To understand the context within which an Enterprise Architecture practitioner must operate
• To apply the stakeholder management technique
• To implement the Architecture Vision phase including its applicable techniques
• To implement the Architecture Development Method (ADM) Phases B, C, and D to develop an architecture, together with the applicable techniques
• To implement the ADM Phases E, F, and G to implement an architecture, together with the applicable techniques
• To implement Architecture Change Management
• To manage architecture requirements
• To use Library
• To support the ADM work with applicable techniques
• To use architecture levels to organize the Architecture Landscape
• To understand the Architecture Content Framework
Course Outline
• What an Enterprise is
• The purpose and benefits of Enterprise Architecture
• The standard as a framework for Enterprise Architecture
• The four architecture domains
• Architecture Abstraction
• The Enterprise Continuum
• The Architecture Repository
• The Content Framework and Enterprise Metamodel
• Architecture Capability
• Risk Management
• Gap Analysis
Understand relevant terminology
• The ADM and its phases
• Draft and Approved status for deliverables
• The iterative approach of the ADM
• The need to govern Enterprise Architecture
• How to Scope an Architecture
• Architecture alternatives and trade-offs
• The purpose and objectives of each of the ADM phases
• How architecture can be applied to support Agile software development
• How the ADM and Supporting Guidelines and Techniques relate to each other
• Architecture Principles
• Business Scenarios
• Gap analysis
• Interoperability
• Business Transformation Readiness Assessment
• Architecture Risk Management
• Where guidance is available
• How iteration within the ADM enables concurrent operation
• The Architecture Landscape
• Purposes to frame Architecture Projects
• How the Standard can be applied to support the digital enterprise
• The concept of Architecture Governance
• Why Architecture Governance is beneficial
• The role and responsibilities of an Architecture Board
• Architecture Contracts
• Architecture Compliance
• The concepts of stakeholders, concerns, architecture views and architecture viewpoints
• Architecture Building Blocks (ABBs)
• Architecture deliverables
• Guiding Effective Change: The Purpose of Enterprise Architecture
• What does an Enterprise Architecture look like?
• Architecture Capability
• Architecture Governance and the role of an Enterprise Architect
• Architecture Compliance, Levels of Conformance, Reviews, and the Role of the
• Architect
• How an Architecture enables alignment to Organizational Objectives using Agile
• development as an example
• The need to Manage Multiple Architecture States
• Enterprise Security Architecture
• Security, a Cross-Cutting Concern
• Managing Uncertainty in order to optimize Maximum Business Benefit and
• Minimum Business Loss
• How to identify Stakeholders, their Concerns, Views, and the Communication involved
• The use of Architecture Views
• Stakeholder Engagement and Requirements Management
• Using Trade-off to Support Architecture development
• Information necessary to execute the Architecture Vision phase
• How to apply Phase A and how it contributes to Architecture Development Work
• Security-specific Architecture Design that is sufficient — Phase A
• Outputs necessary to proceed with the Architecture Development
• Steps applicable to all ADM Phases
• Risk and Security considerations during the Architecture Development (ADM Phases B to D)
• Relevant Information to produce outputs valuable to the Architecture Development
• How to apply Phases B, C, and D, and how they contribute to the Architecture Development work
• Information relevant to Phase C (Data and Applications) to produce outputs for the Architecture Development
• Information needed in Phase D to produce outputs relevant to the architecture development
• Outputs of Phases B, C, and D necessary to proceed with the Architecture Development Work
• Risk and Security considerations for Phases E, F, & G
• Steps (Phase E) to create the Implementation and Migration Strategy
• Basic Approaches to Implementation
• Identifying and Grouping Work Packages
• Creating and Documenting Transition Architectures
• The Impact of Migration Projects on the Organization and the Coordination Required
• Why and how Business Value is assigned to each Work Package
• How to Prioritize the Migration Projects (Phase F)
• Confirm the Architecture Roadmap (Phase F)
• The outputs of Phase F necessary to Proceed with the Architecture Implementation
• Inputs to Phase G Implementation Governance
• How Implementation Governance is executed (Phase G)
• Outputs to support Architecture Governance
• How Architecture Contracts are used to communicate with Implementers
• Inputs triggering Change Management — Change Requests
• Activities necessary for effective Change Management (Stakeholder Management)
• Outputs relevant to proceed with a Change
• The inputs that feed the Requirements Management Phase
• How the Requirements Management steps correspond to ADM Phase Steps
• The Purpose of the outputs of Requirements Management
• How Library can be used to support the Practitioner’s Work
• Business Scenarios
• The purpose of Compliance Assessments
• How Migration Planning techniques are used to review and consolidate the Gap Analysis results from earlier Phases
• How a Repository can be structured using the Architecture Repository as an Example
• What to expect in a well-run Architecture Repository
• How the concepts of Architecture Levels are used to Organize the Architecture Landscape
• Different Levels of Architecture that exist in an Organisation
• Determining the Level that an Architecture is being Developed at
• The Role of Architecture Building Blocks (ABBs)
• Guidelines and Techniques for Business Architecture
• Applying Gap Analysis
• How Iteration can be used in Architecture Practices
• How the Implementation Factor Catalogue can be used
• The Content Framework and the Enterprise Metamodel
• When the Architecture Content Framework (ACF) needs to be Filled throughout the ADM Cycles
• Using an Enterprise Metamodel
• Using a Taxonomy
• How Risk Assessment can be used
TRAINING AND CERTIFICATION