知识卡片
效用树分开业务价值与风险
每个叶子场景分别评业务价值和实现技术风险,可用高中低而不追求虚假的精度。高价值意味着不满足会影响成功,高风险意味着没有信心实现;同时为高的项应优先投入验证。太多高高场景可能说明目标不可行,只有质量目录没有叶子则提醒继续调查,不必机械补齐每一种质量。两种分数不能混成一项“重要性”。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 架构显著需求 · 查看原书依据
Once the ASRs are recorded as scenarios and placed at the leaves of the tree, you can evaluate these scenarios against two criteria: the business value of the candidate scenario and the technical risk of achieving it.
参考来源
- 位置:《Software Architecture in Practice, 4th Edition》第19章《架构显著需求》(来源项目:book-sources;源文件:extracted/Software Architecture in Practice, 4th Edition/_epub-src/ch19.html)
- 结论依据:原文解释每个叶子场景分别评业务价值和实现技术风险,可用高中低而不追求虚假的精度;本章后续机制、例子与条件共同限定本卡,原书经验数字和前景不视为当前实测或现状。
- 原始内容:Once the ASRs are recorded as scenarios and placed at the leaves of the tree, you can evaluate these scenarios against two criteria: the business value of the candidate scenario and the technical risk of achieving it.