知识卡片
质量目标需要协商成本
利益相关者未必知道应要求多快或多可靠,强迫其提供数字可能得到任意且昂贵的目标。架构师可用类似系统经验说明可达区间与成本,例如解释全天候在线的附加代价,让业务方决定价值是否值得;也可提出更容易实现而有用的替代。量化应建立共同理解,不是用精确数字掩盖未知。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 架构显著需求 · 查看原书依据
First, stakeholders often don’t know what their QA requirements actually are. In that case, architects are called upon to help set the QA requirements for a system. Projects that recognize this need for collaboration and encourage it are much more likely to be successful than those that don’t.
参考来源
- 位置:《Software Architecture in Practice, 4th Edition》第19章《架构显著需求》(来源项目:book-sources;源文件:extracted/Software Architecture in Practice, 4th Edition/_epub-src/ch19.html)
- 结论依据:原文解释利益相关者未必知道应要求多快或多可靠,强迫其提供数字可能得到任意且昂贵的目标;本章后续机制、例子与条件共同限定本卡,原书经验数字和前景不视为当前实测或现状。
- 原始内容:First, stakeholders often don’t know what their QA requirements actually are. In that case, architects are called upon to help set the QA requirements for a system. Projects that recognize this need for collaboration and encourage it are much more likely to be successful than those that don’t.