知识卡片
风险主题回到业务目标
分析结束后,把具有共同系统性缺陷的风险归成主题,例如备份不足、文档长期失真,再指出每个主题威胁了哪些初始业务目标。这样技术细节成为管理方能判断的业务风险,也帮助制定缓解计划。主题不是按问题标题随意分类,需来自真实风险的共同根因或关注点;评估报告要保留具体场景与推理,不能只留红黄绿结论。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 评估架构 · 查看原书依据
For each risk theme, the evaluation team identifies which of the business goals listed in step 2 are affected. Identifying risk themes and then relating them to specific drivers brings the evaluation full circle by relating the final results to the initial presentation, thereby providing a satisfying closure to the exercise.
参考来源
- 位置:《Software Architecture in Practice, 4th Edition》第21章《评估架构》(来源项目:book-sources;源文件:extracted/Software Architecture in Practice, 4th Edition/_epub-src/ch21.html)
- 结论依据:原文解释分析结束后,把具有共同系统性缺陷的风险归成主题,例如备份不足、文档长期失真,再指出每个主题威胁了哪些初始业务目标;本章后续机制、例子与条件共同限定本卡,原书经验数字和前景不视为当前实测或现状。
- 原始内容:For each risk theme, the evaluation team identifies which of the business goals listed in step 2 are affected. Identifying risk themes and then relating them to specific drivers brings the evaluation full circle by relating the final results to the initial presentation, thereby providing a satisfying closure to the exercise.