SLIDE 18 18
A Reverse Chronology of Evolutionary Architecture and Agile Development March 21, 2017
18
Software Solutions Symposium 2017
Deliver Business Value Early while Applying Long-term Systems Thinking
Evolutionary Architecture
Highly Abstract Elements, More uncertainty More Concrete Elements, Increased Certainty Prototyping & High-Level Development Initial Use Cases/Scenarios Prototyping & Verification/Validation Results Synchronized Implementation & Architecture Requirements
Objectives
- Tech. Requirements
- Mission/Business
Requirements
Capability Models
Capabilities
Process Models
Activities
Use Cases / Scenarios
- Actor
- Triggers
- Pre/Post Conditions
- Normal/Alt. Flows
Data and Information Models
- Exchanged Data
- Persisted Data
- Migrated Data
Systems and Services Models
structure
interactions
Revised Use Cases/Scenarios
Customer Needs and System Concerns
Sprint N… Sprint 6 Sprint 5 Sprint 4 Sprint 3 Sprint 2 Sprint 1 Sprint 0
Integrated Architecture
Establish Conceptual Integrity
Validation and Verification Results Lower-Level Development
Agile Development and Testing
Evolve Architecture Design for Known and Unknown Identify Problems Capture Reqs. and Quality Attributes
Maximize architectural runway opportunities: Understand – Document – Analyze – Evolve
Continuous Verification and Validation Manage Technical Complexity and Risk
Extend and Sustain Architecture
Incrementally Delivered Capabilities