知识卡片
上下结合估算成本进度
架构提供工作分解,开发者据各自模块和集成责任做自下而上估计,架构师与项目经理据目标资源做自上而下估计。两者协商比单方估算更能暴露范围误解、预算冲突和依赖,并让执行者对承诺有参与感。需求越清楚估算越可信,架构仍不是消除不确定性的算命工具。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 软件架构为何重要 · 查看原书依据
But the best cost and schedule estimates will typically emerge from a consensus between the top-down estimates (created by the architect and the project manager) and the bottom-up estimates (created by the developers). The discussion and negotiation that result from this process create a far more accurate estimate than use of either approach by itself.
参考来源
- 位置:《Software Architecture in Practice, 4th Edition》第2章《软件架构为何重要》(来源项目:book-sources;源文件:extracted/Software Architecture in Practice, 4th Edition/_epub-src/ch02.html)
- 结论依据:原文的定义、机制或比较支持“架构提供工作分解,开发者据各自模块和集成责任做自下而上估计,架构师与项目经理据目标资源做自上而下估计”;正文保留其条件与取舍。
- 原始内容:But the best cost and schedule estimates will typically emerge from a consensus between the top-down estimates (created by the architect and the project manager) and the bottom-up estimates (created by the developers). The discussion and negotiation that result from this process create a far more accurate estimate than use of either approach by itself.