Tools of Intentional Architectures
summary
Claims that relying on opinionated stacks like Angular and tools like Nx can produce accidental architectures unless architecture work is intentional and measurable and cites studies that ~70% of issues originate when understanding stakeholder needs and ~50% of project cost goes to rework after unit testing. Recommends concrete practices: run a quality attribute workshop, produce ADRs and a quality attribute utility tree, use an architecture trade-off analysis method to surface risks and track ngRx and other framework impacts so architecture decisions are auditable.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:37Welcome
- 0:54Context
- 3:58Common Reasons
- 5:56Confidence
- 8:14Architecture Drivers
- 11:00Quality Attributes
- 13:56Quality Attributes Workshop
- 19:02Documentation
- 24:06Manual Activities
- 25:57Architecture Depths
related talks
27mThe Superpower of Intentional Architecture
59mDeliberate Architecture
24mThe too many faces of Architecture
01h 09mAgile Software Architecture
45mArchitecture: The Stuff That's Hard to Change
41mArchitecture and Agility: A Shared Skillset!
43mTesting Software Architectures
40mThe (too) many faces of architecture