Log In
Or create an account ->
Imperial Library
Home
About
News
Upload
Forum
Help
Login/SignUp
Index
Cover
Title
Copyright
Table of contents
Open Agile Architecture
Preface
The Open Group
This Document
Trademarks
Acknowledgements
Referenced Documents
Normative References
Informative References
1. Introduction
1.1. Objective
1.2. Overview
1.3. Conformance
1.4. Normative References
1.5. Terminology
1.6. Future Directions
2. Definitions
2.1. Accountability
2.2. Alignment Diagram
2.3. Allowable Lead Time
2.4. Architectural Runway
2.5. Architecture
2.6. Architecture Principle
2.7. Architecture Style
2.8. Capability
2.9. Catchball
2.10. Continuous Architecture
2.11. Customer Experience
2.12. Customer Journey
2.13. Design Thinking
2.14. Digital Platform
2.15. Digital Practices
2.16. Digital Technology
2.17. Digital Transformation
2.18. Domain Model: Domain-Driven Design
2.19. Ecosystem
2.20. Epic
2.21. Event Storming
2.22. Evolutionary Architecture
2.23. Evolvability
2.24. Feature
2.25. Hardware
2.26. Information Security
2.27. Integrality
2.28. Intentional Architecture
2.29. Job-To-Be-Done
2.30. Journey Mapping
2.31. Lead Time
2.32. Lean Value Stream
2.33. Modularity
2.34. Modularization
2.35. Operating System
2.36. Outcome
2.37. Persona
2.38. Platform Business Model
2.39. Process
2.40. Product
2.41. Product Backlog
2.42. Product-Centric Organization
2.43. Refactoring
2.44. Responsibility
2.45. Service
2.46. Social System
2.47. System
2.48. User Story
2.49. Value Stream
2.50. Work System
Part 1: The O-AA Core
3. A Dual Transformation
3.1. Why Organizational Agility Matters
3.2. Connecting Touchpoints to the Operating System
3.3. Developing Business and Organizational Agility
4. Architecture Development
4.1. Architecture
4.2. Development Building Blocks
4.2.1. Strategy
4.2.2. Corporate Brand Identity, Culture
4.2.3. Value
4.2.4. Perspectives
4.2.5. What the Enterprise “Is”
4.2.6. What the Enterprise “Does”
4.3. Data, Information, and Artificial Intelligence
4.4. Software and Hardware Architecture
4.5. Architecture Development Styles
4.5.1. Emergence
4.5.2. Intentional Architecture
4.5.3. Concurrent, Continuous, and Refactored
4.5.4. Tailoring Architecture Development
5. Intentional Architecture
5.1. Enterprise Architecture versus Solution Architecture
5.2. Architecturally Significant Decisions
5.3. Architecture Decision Record
5.4. Example: Car Sharing Platform (CSP)
5.5. From Intentional to Continuous
5.6. When Intentional Architecture is Recommended
5.7. Set-Based Concurrent Engineering (SBCE)
5.8. SBCE of the CSP
5.9. A Few Concluding Words
6. Continuous Architectural Refactoring
6.1. Introduction
6.1.1. Refactoring
6.1.2. Architectural
6.1.3. Continuous
6.2. Planning for Continuous Architectural Refactoring
6.3. Understanding and Guiding the Architecture
6.3.1. Constraints
6.3.2. Fitness Functions
6.3.3. Guardrails
6.4. Creating the Right Technical Environment
6.4.1. Continuous Delivery
6.4.2. Componentization
6.5. Creating the Right Non-Technical Environment
6.5.1. Justifying Ongoing Investment in Architectural Refactoring
6.5.2. Developing an Architectural Roadmap
6.5.3. Progressive Transformation (Experience)
7. Architecting the Agile Transformation
7.1. Accountability
7.2. Incremental Agile Transformation
7.3. Architecting the Organization
7.4. DevOps Culture
7.5. Leadership Drives Change
8. Agile Governance
8.1. Classical IT Governance
8.2. Governance in the Face of Agile
8.3. Agile Governance
9. Axioms for the Practice of Agile Architecture
9.1. Axiom 1. Customer Experience Focus
9.2. Axiom 2. Outside-In Thinking
9.3. Axiom 3. Rapid Feedback Loops
9.4. Axiom 4. Touchpoint Orchestration
9.5. Axiom 5. Value Stream Alignment
9.6. Axiom 6. Autonomous Cross-Functional Teams
9.7. Axiom 7. Authority, Responsibility, and Accountability Distribution
9.8. Axiom 8. Loosely-Coupled Systems
9.9. Axiom 9. Modular Data Platform
9.10. Axiom 10. Simple Common Operating Principles
9.11. Axiom 11. Partitioning Over Layering
9.12. Axiom 12. Organization Mirroring Architecture
9.13. Axiom 13. Organizational Leveling
9.14. Axiom 14. Bias for Change
9.15. Axiom 15. Project to Product Shift
9.16. Axiom 16. Secure by Design
Part 2: The O-AA Building Blocks
10. Building Blocks Overview
10.1. Building Blocks Logic
10.2. Enterprise Decomposition
10.3. Segmentation Approach
10.4. Mental Model Shifts
10.5. Navigation Table
11. Agile Strategy
11.1. Agile Strategy Tenets
11.1.1. Tenet 1. Grasp the Situation
11.1.2. Tenet 2. Frame Strategy Around “Hard-to-Reverse” Choices
11.1.3. Tenet 3. Anticipate Unintended Consequences
11.1.4. Tenet 4. Strategy is a Journey
11.1.5. Tenet 5. Mix Stability and Dynamism
11.1.6. Tenet 6. Do Not Deploy Strategy in Silos
11.2. Bending the Law of Unintended Consequences
11.3. Succeeding Strategy Deployment
12. Agile Organization
12.1. Learnings from Socio-Technical Systems
12.1.1. Example: English Coal Mines
12.1.2. Principles
12.2. Autonomy and Self-Organization
12.3. Team Taxonomy
12.3.1. Stream-Aligned Teams
12.3.2. Platform Teams
12.3.3. Competency Teams
12.4. Product Teams
12.4.1. Product Manager versus Product Owner
12.4.2. Lean Chief Engineer
12.5. Shifting to an Agile Organization
13. Experience Design
13.1. Experience Design Approach
13.2. What is a Product?
13.2.1. Intangible Goods
13.3. Customer Research
13.3.1. Market Research
13.3.2. Jobs-To-Be-Done
13.4. Combining Product Discovery with Customer Research
13.4.1. Experience Mapping
13.4.2. Goods Features
13.4.3. Service Features
13.4.4. Feature Outcomes and Benefits
13.4.5. Digital Products: Connected Goods and Fingertip Services
13.4.6. Quality Properties: The “ilities” of Products
13.5. Example: Ride-Hailing Company
14. Product Architecture
14.1. Defining Product Architecture
14.2. Interdependence and Modularity
14.2.1. Modularity Wins
14.2.2. Integration Wins
14.2.3. Modular Goods
14.2.4. Modular Services
14.3. Modularity-Integrality Trade-Off
14.4. Product Platforms
14.5. Concluding Words
15. Journey Mapping
15.1. Moments of Truth
15.2. The Human Side
15.3. The Role of Automation
16. Lean Value Stream Mapping
16.1. From Process to Value Stream
16.1.1. Visualizing Processes
16.1.2. Value-Driven
16.1.3. Value Stream Mapping
16.1.4. Granularity Level
16.2. Approach Overview and Key Concepts
16.2.1. Current Conditions
16.2.2. Ideal “Clean-Slate” Vision
16.2.3. Waste
16.2.4. Mura and Muri
16.3. Future State Mapping
16.3.1. Schedule an Appointment
16.3.2. Discover, Offer, and Choose Products
16.3.3. Collect and Control Documents
16.3.4. Capacity Management
16.3.5. Increase On-Boarding Capacity
16.3.6. Printing Credit Cards in Branches
16.4. Key Points to Take Away
16.4.1. Benefits
16.4.2. Organizational Implications
17. Operations Architecture
17.1. Capability
17.2. Operations Architecture Decisions
17.3. Leveraging Digital Technology
17.4. Example: AR
17.5. Product Variety
18. Data Information and Artificial Intelligence (AI)
18.1. Data Streaming Architectures
18.2. Coupling Data Streaming with AI
18.3. Data Model and Reality
18.4. The Monolithic Data Model
18.5. Moving Away from Monolithic Data Architectures
18.6. Machine Learning Pipelines
18.7. Deep Learning for Mobile
18.8. A Few Concluding Words
19. Event Storming
19.1. Summary: Why? How? Who?
19.2. Domain Event
19.3. Event Storming Principles
19.4. Types of Event Storming Session
19.5. Event Storming Notation and Concepts
19.6. Benefits
19.7. Event Storming Workshop Facilitation Techniques
20. Domain-Driven Design: Strategic Patterns
20.1. Problem Space
20.1.1. Domains and Sub-Domains
20.2. Solution Space
20.3. Context Map
20.3.1. Upstream Patterns
20.3.2. Midway Patterns
20.3.3. Downstream Patterns
20.3.4. Mapping the Context Map Patterns
21. Software Architecture
21.1. What is Software Architecture?
21.2. Event-Driven Architecture
21.2.1. Concepts of Command, Query, and Event
21.2.2. Benefits of Event-Driven Architecture
21.2.3. Event Sourcing
21.2.4. Command Query Responsibility Segregation (CQRS)
21.2.5. Command, Query, and Event Metadata
21.2.6. System Consuming Other Systems' Events
21.2.7. Ensuring Global Consistency with Saga Patterns
21.3. Hexagonal Architecture: Why? Benefits?
21.3.1. Domain, Application, and Infrastructure Code
21.3.2. Inside and Outside, Ports and Adapters
21.3.3. Inbound Ports and Adapters (or Primary, Driving, Left, API)
21.3.4. Outbound Ports and Adapters (or Secondary, Driven, Right, SPI)
21.4. Non-Functional Software Requirements
21.4.1. Security
21.4.2. Reliability
21.4.3. Performance
21.4.4. Operability
21.4.5. Maintainability
21.4.6. Interoperability
21.5. Software Cross-Cutting Concerns
22. Software Engineering for Hardware
22.1. Infrastructure as Code
22.2. DevOps Example
22.2.1. DevOps Objectives: Organizational and Software-Delivery Performance
22.2.2. Four Key Metrics
22.2.3. DevOps Principles
22.2.4. Capabilities
22.2.5. Behavior and Practices
22.2.6. DevOps Tools
22.3. Site Reliability Engineering (SRE)
22.3.1. SRE Principles
22.3.2. SRE Practices
22.3.3. Cloud-Native Infrastructure
Appendix A: Acronyms
Index
← Prev
Back
Next →
← Prev
Back
Next →