Application Components in a Phase Space
summary
Claims that software can be modeled as a bounded phase space of all states where objects (users, APIs, domains) exert forces that create wobbling boundary effects around functionality and data. Uses ride‑sharing and Netflix→credit‑card flows as concrete examples of cross‑domain interactions, argues testers can locate failures by drilling toward singular states, and reports an ongoing industry validation with Pfizer (method under review, not yet proven in production).
AI-written summary · about
chapters (7)
- 0:00Introduction to Phase Space
- 1:25Defining Phase Space
- 3:33Challenges in Testing Phase Space
- 5:44Object Interactions and Wobbling Effects
- 7:11Requirements and Context Inflation
- 8:15Multiple Domain Interactions
- 9:20Theory Validation and Conclusion
related talks
39mFrom Domain Boundaries to Software Architecture
50mSoftware Is Details
27mLet's Bring System Dynamics Back to CS!
55mCharting the uncharted: Discovering and evolving bounded contexts
48mPhases in Software Architecture
53mSoftware Design: Beyond Boxes & Lines
34mPlatforms: Defying the laws of IT physics
43mSBA- Journey to a New Architecture