Course Catalog  > Architecture  > Solution Architecture
WA2326

Solution Architecture Practitioner's Guide Training

This course is a subset of WA2325 targeted for SA stakeholders involved with solution architecture, yet not responsible for producing architecture artifacts. The course will cover the same concepts. It will focus on understanding the architecture activities and artifacts, instead of developing architecture artifacts.
Request Information
Request On-Site or Customized Course Info
Course Details

Duration

2 days

Prerequisites

No prior knowledge is presumed.

Target Audience

  • Managers and stakeholders involved with SA activities
Course Outline
  • Introduction
  • Solution Architecture Overview
    • Why is Solution Architecture Important?
    • Communications Vehicle Among Stakeholders
    • The Project is Organized Around Architectural Elements
    • What is a System?
    • Why Focus on Structure?
    • Solution Architecture Context
    • Solution Architecture & Domains
    • SA Spans All Domains
    • Relationship to EA Architecture Development Process
    • Solution Architecture
    • Solution Architecture Stakeholders
    • Solution Architecture Deliverables
    • EA Involvement in SA
    • Architecturally Significant
    • Group Discussion: Architecture
    • Resource: Software Engineering Institute (SEI)
    • Resource: SWEBOK
    • Resource: OpenUp
    • Resource: Microsoft Library
    • Group Discussion: Methodologies
  • Core Solution Architecture Methods
    • Shared Vision
    • Example Shared Vision
    • Draw the Boundary
    • Well-defined Interface
    • Example: Context Diagram
    • Identify the External Interfaces
    • Subsystems
    • Subsystem Context Diagram
    • Layers
    • Example: Subsystems with Layers
    • Components
    • Decomposing the System
    • Partitioning Patterns
    • Example Partitioning Based on Patterns
    • Example: Healthcare SOA Framework
    • Requirements Allocation
    • Group Discussion: Requirements Allocation
    • Configuration Management Implications
    • Release Management Implications
    • Testing Implications
    • Work Pattern & Skill Set Implications
    • Work & Build Dependencies
    • Increment/Sprint Planning
    • Sizing Implications
    • More Than Executable Architecture
    • Development Architecture
    • Operations Architecture
    • Group Discussion: Integrating Operations Architecture
  • 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
    • Trade-off Analysis
    • Group Discussion: Trade-offs
    • Requirement Patterns
    • Example: Non-Functional Requirement Patterns
    • Architecture Change Cases
    • Elements of a Change Case
    • Example: Change Case
    • Eliciting Change Cases
    • Group Discussion: Change Case
  • Architecture Deliverables
    • Architecture Requirements Document
    • Template: Requirements Specification
    • IEEE Architectural Description Document
    • Template: Architectural Description Document
    • TOGAF Architecture Definition Document
    • Templates: Architectural Definition Document
    • Group Discussion: Architecture Definition Documents
    • Interface Specifications
    • Interface Specification Best Practices
    • Interface Design Document
    • Template: Interface Design Document
    • Database Design Document
    • Template: Database Design Document
    • Platform Design Document
    • Template: Platform Design Document
    • Architecture Decision Document
    • Template: Architecture Decision Document
    • Group Discussion: Architecture Decision Document
  • Views & Viewpoints
    • Stakeholders
    • Example Stakeholders & Concerns
    • Stakeholder Matrix
    • Stakeholder Map
    • Views & Viewpoints
    • Example: Documenting a Viewpoint
    • Example: Another Viewpoint
    • Group Discussion: Viewpoints
  • Solution Architecture Views
    • The 4+1 Views Approach
    • Take a Multiple View Approach
    • UML: Unified Modeling Language
    • UML Notation Examples
    • Use Case View
    • Logical View
    • Process Views
    • Implementation View
    • Deployment View
  • 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
  • Architecture Techniques
    • ATAM: Scenario-based Architecture Review
    • Progressive Filtering
    • Rubric
    • Example: Service Design Rubric
    • Example: Architecture Rubric
    • Refactoring
    • Think About the Future, But Wait to Act
    • Feature Tree
    • Decision Tables
    • Decision Table Example
    • Flowcharts
    • Strength, Weakness, Opportunity, Threat (SWOT) Analysis
    • Example: SWOT Layout
    • SWOT Steps
  • 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
  • Solution Architecture Styles
    • Message Oriented Middleware (MOM)
    • MOM Messaging
    • MOM Qualities
    • Publish/Subscribe Messaging
    • Point-to-Point Messaging
    • MOM Advantages & Disadvantages
    • MOM Example
    • Service Oriented Architecture
    • Understanding by Analogy
    • Service Oriented Architecture
    • Service Elements
    • Service Actors
    • Service Layering
    • SOA Advantages & Disadvantages
    • SOA Example
    • Web Oriented Architecture
    • The WOA Difference
    • WOA Services
    • WOA Communities
    • WOA Advantages & Disadvantages
    • WOA Example
    • Business Process Management
    • Further Qualifying BPM
    • BPM Architecture
    • BPM Architecture Model
    • BPM Advantages & Disadvantages
    • Master Data Management
    • Understanding Master Data
    • Qualities of Master Data
    • MDM Implementation Styles
    • MDM Advantages & Disadvantages
    • MDM Example
  • SDLC Support
    • Architecture is Only as Good as the Implementation
    • Solution Architecture vs. Project Manager
    • Project vs Product Lifecycle
    • Collaboration Important
    • Quality Requirements
    • Requirements Traceability
    • Testing
    • Test Cycles
    • Group Discussion: Test Types
  • The Architecture Toolbox
    • The Architecture Toolbox
    • The Toolbox
    • What Goes in A Toolbox
    • More Patterns
    • Business Analysis Book of Knowledge (BABOK)
    • Resource: Business Architecture Body of Knowledge (BIZBOK™)
    • DAMA DMBOK
    • Reference Library
    • Practitioner Toolbox Items
    • Group Discussion: Toolbox Items
  • Lessons Learned
    • Process Recommendations Summary
    • Structural Recommendations Summary
    • Anti-Patterns
    • Anti-Pattern: Bleeding Edge
    • Anti-Pattern: Goldplatting
    • Anti-Pattern: Strive for Perfection
    • Anti-Pattern: Stuck in the Weeds