返回主题:风险驱动的架构设计

知识卡片

普通读书笔记卡 · 2303.a.1.b

ATAM分阶段扩大验证范围

理解等级:中级

准备阶段先约定范围、人员、资料和报告;第一分析阶段由评估方与项目决策者介绍业务和架构、识别方法、建效用树并分析重点场景。第二阶段加入更广的相关者,回顾已有结果、提出并排序新场景,再分析并汇报。最后跟进报告先校对理解再交付。分阶段是为了先理解设计者逻辑,再用更广成功标准检验,不是重复开同一场会。

[[ATAM需要三类合作方]]给出角色,这里说明各方何时进入分析。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 评估架构 · 查看原书依据

      Steps 1–6 are carried out in phase 1 with the evaluation team and the project’s decision makers—typically, the architecture team, project manager, and client. In phase 2, with all stakeholders involved, steps 1–6 are summarized and steps 7–9 are carried out.

    参考来源

    - 位置:《Software Architecture in Practice, 4th Edition》第21章《评估架构》(来源项目:book-sources;源文件:extracted/Software Architecture in Practice, 4th Edition/_epub-src/ch21.html) - 结论依据:原文解释准备阶段先约定范围、人员、资料和报告;第一分析阶段由评估方与项目决策者介绍业务和架构、识别方法、建效用树并分析重点场景;本章后续机制、例子与条件共同限定本卡,原书经验数字和前景不视为当前实测或现状。 - 原始内容:Steps 1–6 are carried out in phase 1 with the evaluation team and the project’s decision makers—typically, the architecture team, project manager, and client. In phase 2, with all stakeholders involved, steps 1–6 are summarized and steps 7–9 are carried out.