知识卡片
情境写清决定依赖什么
Context应说明为何此刻需要决定、已知事实、约束和相关要求。先把信息写出,再删除与问题无关细节,必要时画出可控制与不可控制的部件。先问问题是什么,而非抢写解法;背景可以接受咨询,因为问题框定本身也可能漏掉关键人或事实。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Architectural Decision Records · 查看原书依据
Writing the Context clarifies your awareness of both the issue at hand and the key factors that affect it (the things that the decision “depends on”). These factors can be other teams, other parts of the software system, cost, available skills, tooling (including pipelines), and more. It’s impossible—and unnecessary—to be exhaustive, but as I highlighted
参考来源
- 位置:《Facilitating Software Architecture》第06章《Architectural Decision Records》(来源项目 /Users/wangyi/claudecodeProject/bookBase/book-sources;源文件:extracted/Facilitating Software Architecture/_epub-src/OEBPS/ch06.html)
- 结论依据:原文把情境列为最重要思考部分之一,并说明brain dump、精炼及顾问受众如何澄清问题。
- 原始内容:Writing the Context clarifies your awareness of both the issue at hand and the key factors that affect it (the things that the decision “depends on”). These factors can be other teams, other parts of the software system, cost, available skills, tooling (including pipelines), and more. It’s impossible—and unnecessary—to be exhaustive, but as I highlighted