Communicating, Sharing and Maintaining Architectural Decisions in Development Teams
summary
Shows concrete tools and practices for communicating, sharing and maintaining architectural decisions in PHP teams: uses the C4 model for diagrams, records decisions with ADRs, and automates checks via php-cs-fixer/phpcs extensions and phpstan. Presents a prototype rule that enforces classes in a namespace to end with "Data", explains that writing such rules is feasible but requires low-level work, and notes that deptrac finds unwanted dependencies; demos and published code are working.
AI-written summary · about
chapters (9)
- 0:00Start
- 7:24C4 Model
- 8:37Context
- 9:23Container
- 10:03Component
- 10:26Code
- 11:14C4 PlantUML
- 11:52Architecture Decision Records (ADR)
- 22:43Try this at home!
related talks
45mSW Design, Architecture & Clarity at Scale
30mCommunicating and documenting architectural decisions
01h 00mVisualise, document and explore your software architecture
57mVisualise, document and explore your software architecture
51mConsistent architecture diagrams for C++ projects
47mArchitecture as Code or How to Survive Legacy and Keep Your Sanity
02h 37m[Workshop] How to Document Your Decisions
24mThe too many faces of Architecture