← 返回刚才阅读的位置

知识卡片

普通读书笔记卡 · 1845.i

架构定边界团队设计细节

理解等级:高级

架构师与负责人明确顶层分解、对外与跨团队API,再让熟悉实现上下文的人设计组件细节并共同评审。这样利用分散知识,也培养团队判断力和设计所有权。默认规范仍可存在,偏离时要求解释收益与代价;放权不是取消边界,而是让关键约束清楚后把可局部判断的事交给最近的人。

[[独立交付减少重建连锁]]明确团队的交付责任,这里进一步明确团队内的设计决定权。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 构建与演进系统 · 查看原书依据

      Therefore, it is best to design the top-level architecture with the key people: let architecture owners design services and let component developers design the components. However, this does not mean we cannot have consistent best practices.

    参考来源

    - 位置:《Software Architecture and Decision-Making》第13章《Building and Evolving the Systems》(来源项目:book-sources;源文件:extracted/Software Architecture and Decision-Making Leveraging Leadership, Technology, and Product Management to Build Great Products… (Srinath Perera)/_epub-src/ch13.xhtml) - 结论依据:摘录说明架构师与负责人明确顶层分解、对外与跨团队API,再让熟悉实现上下文的人设计组件细节并共同评审。其余条件结合本章相邻例子与取舍说明,数字示例不作当前性能承诺。 - 原始内容:Therefore, it is best to design the top-level architecture with the key people: let architecture owners design services and let component developers design the components. However, this does not mean we cannot have consistent best practices.