知识卡片
架构文档也按增量交付
增量架构是在适合项目节奏的时点发布相应深度的架构信息。初次宜提供模块分解以形成团队、uses关系以规划可用子集、传达总体解法的运行视图和粗部署方案;以后按读者需要补细节。先发布什么直接影响团队能否开始工作和集成,不能等全部设计完才交一套文档。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 项目中的架构师角色 · 查看原书依据
Incremental architecture, then, is about releasing the architecture in increments. Specifically, this means releasing architecture documentation (as described in Chapter 22) in increments. This, in turn, entails deciding which views to release (out of your planned set) and at which depth.
参考来源
- 位置:《Software Architecture in Practice, 4th Edition》第24章《项目中的架构师角色》(来源项目:book-sources;源文件:extracted/Software Architecture in Practice, 4th Edition/_epub-src/ch24.html)
- 结论依据:原文解释增量架构是在适合项目节奏的时点发布相应深度的架构信息;本章后续机制、例子与条件共同限定本卡,原书经验数字和前景不视为当前实测或现状。
- 原始内容:Incremental architecture, then, is about releasing the architecture in increments. Specifically, this means releasing architecture documentation (as described in Chapter 22) in increments. This, in turn, entails deciding which views to release (out of your planned set) and at which depth.