Artifacts of architecture: which, why and how to organize them
summary
The presentation surveys which architecture artifacts (diagrams, documents, models, etc.) teams need in a company, categorizes common types and their purposes, and gives practical guidance on organizing and maintaining those artifacts so they remain useful rather than burdensome. It focuses on concrete practices for creating, naming, storing and evolving architectural artifacts to support collaboration and reduce pain during development and operations.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:29Why architecture artifacts
- 8:36Classic frameworks problems
- 15:19Adapting the model
- 23:51System inventory and goals
- 33:03Artifact synchronization
- 38:06Transformation results
- 44:50Q&A
related talks
45mArchitecture and the Architect AD2022
49mCultivating Architecture
07mWhat is Architecture, and Why It Matters
01h 00mDescribing and Documenting Your Architecture
35mOrganization: A Tool for Software Architects
54mArchitecture Is Not Nonsense
40mArchitecture, and How to Cook It
46mBest Practices for Keeping Architecture Documentation Up to Date