知识卡片
组织分工会冻结架构边界
按架构拆分团队后,计划、预算、配置管理和沟通路径都围绕这些边界展开。重分职责因此不只是搬代码,团队利益与合同还可能阻碍调整。软件结构与组织安排互相塑造,应在形成昂贵组织绑定前分析关键选择,且把后续协调成本纳入架构变化评估。
相关:[[早期绑定放大后续改动]]。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 软件架构为何重要 · 查看原书依据
A side effect of establishing the work-breakdown structure is to freeze some aspects of the software architecture. A group that is responsible for one of the subsystems may resist having its responsibilities distributed across other groups. If these responsibilities have been formalized in a contractual relationship, changing responsibilities could become expensive or even litigious.
参考来源
- 位置:《Software Architecture in Practice, 4th Edition》第2章《软件架构为何重要》(来源项目:book-sources;源文件:extracted/Software Architecture in Practice, 4th Edition/_epub-src/ch02.html)
- 结论依据:原文的定义、机制或比较支持“按架构拆分团队后,计划、预算、配置管理和沟通路径都围绕这些边界展开”;正文保留其条件与取舍。
- 原始内容:A side effect of establishing the work-breakdown structure is to freeze some aspects of the software architecture. A group that is responsible for one of the subsystems may resist having its responsibilities distributed across other groups. If these responsibilities have been formalized in a contractual relationship, changing responsibilities could become expensive or even litigious.