知识卡片
实现约束承载全局取舍
实现要遵循架构规定的元素、交互与职责,局部开发者未必知道所有全局权衡。架构师可把端到端性能目标分成各元素预算,使各团队据本地责任实现;前提是组合路径和开销已被正确计入。架构师负责建立、分析和执行这些约束,同时保留算法和语言层面的实现自由。
相关:[[质量预测应先于完整实现]]。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 软件架构为何重要 · 查看原书依据
A classic example is when an architect assigns performance budgets to the pieces of software involved in some larger piece of functionality. If each software unit stays within its budget, the overall transaction will meet its performance requirement. Implementers of each of the constituent pieces may not know the overall budget, but only their own.
参考来源
- 位置:《Software Architecture in Practice, 4th Edition》第2章《软件架构为何重要》(来源项目:book-sources;源文件:extracted/Software Architecture in Practice, 4th Edition/_epub-src/ch02.html)
- 结论依据:原文的定义、机制或比较支持“实现要遵循架构规定的元素、交互与职责,局部开发者未必知道所有全局权衡”;正文保留其条件与取舍。
- 原始内容:A classic example is when an architect assigns performance budgets to the pieces of software involved in some larger piece of functionality. If each software unit stays within its budget, the overall transaction will meet its performance requirement. Implementers of each of the constituent pieces may not know the overall budget, but only their own.