Audience
Architects that learned TOGAF and what to understand SA
Prerequisites
TOGAF knowledge
Duration
1 Day
Outline for Integrating Solution Architecture (SA) Training
Chapter 1 - Introduction
- Introductions
- Course Outline
- Handouts & Appendices
- Practical Application: Building Skills
- Practical Application: Filling Your Toolbox
- Course Evaluation & Questions
- Course Delivery Overview
Chapter 2 - 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
- Summary
Chapter 3 - 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
- Summary
Chapter 4 - 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
- Summary
Chapter 5 - 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
- Summary
Chapter 6 - 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
- Summary
Chapter 7 - 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
- Summary
Chapter 8 - 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
- Summary
Handout 1 - Quality Attribute (QA)/Quality of Service (QoS) Categories
- Introduction
- Quality Attributes
Handout 2 - Requirement Patterns
Handout 3 - Requirement Statement Checklist
- Introduction
- Requirement Statement Review Checklist
Appendix A - Reference Library
- Industry Organizations
- References & Further Reading
Appendix B - Glossary
- ABC
- DEF
- GHI
- MNO
- PQR
- STU
- VWXYZ