WA2336
Reference Architectures and Roadmaps Training
This course focuses on the most commonly used architecture deliverables and skills that organizations use when starting an EA program. The course includes: Reference Architecture development, architecture requirements definition, gap analysis, architecture roadmaps, architecture patterns, architecture tactics, architecture techniques, COTS architecture and considerations.
Course Details
Duration
1 day
Prerequisites
Prior knowledge of TOGAF® is required.
Target Audience
Architects that learned TOGAF and are ready to apply
Course Outline
- Introduction
- Reference Architecture
- Reference Architecture
- Reference Architecture Components
- Reference Architecture Summarized
- Reference Architecture Context
- Architecture Principles
- Components of Principles
- Qualities of a Good Set of Principles
- EA Principles: Creation Process
- Templates: Principle & Principle Catalog
- Example: Architecture Principles
- Group Discussion: Principles
- Applying Architecture Principles
- Policies
- Template: Policy
- Example: Governance Policies
- Example: SOA Policy
- Example: Policies
- Reference Models
- Example: IBM Business Analytics & Optimization Reference Architecture
- Example: IBM Insurance Application Architecture
- Example: SOA Reference Architecture
- Example:Customer Experience Reference Architecture
- Business Scenarios
- Business Scenario Summary
- Business Scenario Outline
- Template & Example: Business Scenario
- Practices: Standards & Guidelines
- Example: Interoperability Standards
- Example: Insurance Reporting Reference Architecture
- Example: Electronic Product Code™ (EPC) Standards
- Example: Health Care Reference Architecture
- Resource: Financial Industry Organizations
- Resource: Health Industry Organizations
- Resource: Retail Industry Organizations
- Resource: Technical Organizations
- Industry Organizations
- Insurance Industry Standards ROI
- Requirements
- Example: Mobile Security Reference Architecture
- Example: MSRA Requirements
- Architecture Building Blocks: Reusable Requirement Sets
- Resource: NIST Security Requirements
- Example: COTS Standard Requirements Set
- Architecture Requirements
- Architecture Quality Attributes
- Quality of Service Requirement Categories
- Quality Attribute (QA)/Quality of Service (QoS) Definitions
- Trade-off Analysis
- Group Discussion: Trade-offs
- Requirement Patterns
- Example: Non-Functional Requirement Patterns
- Requirement Statement Best Practices
- Architecture Change Cases
- Elements of a Change Case
- Example: Change Case
- Eliciting Change Cases
- Group Discussion: Change Case
- Architecture Gap Analysis, Roadmap & Migration Planning
- Putting the Pieces Together
- Gap Analysis
- Gap Analysis Matrix
- Example: DOE Gap Analysis
- Consolidated Gaps, Solutions, and Dependencies Matrix
- Architecture Roadmap Table
- Transition Architectures in Context
- Architecture Roadmap
- General Roadmap Methodology
- Defining Work Packages
- Roadmap Development Strategies
- Example: High-Level Architecture Roadmap
- Example: Pharmacy Standards Roadmap
- Example: SOA Roadmap
- Example: Business Intelligence Roadmap
- Template: Architecture Roadmap
- Migration Planning
- Business Value Assessment Technique
- Example: DOE Transition Plan
- Example:Transition Milestone Table
- Example: EPA Transition Plan
- Template: TOGAF Implementation & Migration Plan Template
- Process Summary
- Patterns
- What are Patterns?
- Elements of a Pattern
- Pattern Levels
- Pattern Types
- How to Start Using Patterns?
- Common Architectural Patterns
- Layers Pattern
- Example: Retail Layered Architecture
- Object-Oriented Design Patterns
- Structural Design Pattern: Facade Pattern Example
- Enterprise Integration Patterns
- Messaging Systems: Overview
- Example Pattern: Pipes and Filters
- Monitoring Credit Bureau Example
- EAA Patterns
- Model-View-Controller (MVC) Pattern
- SOA Patterns
- Example: Saga Pattern
- Business Process Patterns
- Example: Synchronizing Merge Pattern
- Configuration Management Patterns
- New Patterns Continue to Emerge
- Group Discussion: Patterns
- Architecture Tactics
- Tactics
- Availability Tactics
- Modifiability Tactics
- Architectural Patterns and Corresponding Tactics for Modifiability
- Performance Tactics
- Security Tactics
- Testability Tactics
- Usability Tactics
- Approach for Describing Tactics
- Group Discussion: Tactics
- Pipes & Filters: Tactics
- Service-Oriented Architecture (SOA): Tactics
- Commercial-Off-The-Shelf (COTS)
- COTS Advantages & Disadvantages
- COTS Implication: Accept Design Influence
- COTS Implication: Plan for Stability
- COTS Implication: Sustain Competency
- COTS Implication: Vendor Lock-In
- COTS Implication: Balance Business Needs & Architecture
- COTS Inherent Risks
- COTS Risk Management Strategy #1
- COTS Risk Management Strategy #2
- COTS Risk Management Strategy #3
- Group Discussion: COTS
- Typical COTS Architecture
