知识卡片
需求变化要双向保持感知
ASR会变化,架构师需与决定需求的关键方保持双向沟通,反复访谈、工作坊或更新效用树。听到可能变化时可先探索其架构后果,尽早报告高成本,并提出近似满足目标但更经济的替代。需求清单应集中保留以便复查与解释决策,而非一次签字后就冻结;跟踪变化也不意味着预先实现全部猜测。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 架构显著需求 · 查看原书依据
Even better than keeping up with change is staying one step ahead of it. If you get wind of a change to the ASRs, you can take preliminary steps to design for it, as an exercise to understand the implications.
参考来源
- 位置:《Software Architecture in Practice, 4th Edition》第19章《架构显著需求》(来源项目:book-sources;源文件:extracted/Software Architecture in Practice, 4th Edition/_epub-src/ch19.html)
- 结论依据:原文解释ASR会变化,架构师需与决定需求的关键方保持双向沟通,反复访谈、工作坊或更新效用树;本章后续机制、例子与条件共同限定本卡,原书经验数字和前景不视为当前实测或现状。
- 原始内容:Even better than keeping up with change is staying one step ahead of it. If you get wind of a change to the ASRs, you can take preliminary steps to design for it, as an exercise to understand the implications.