知识卡片
决定反向推动雷达更新
试用新方案或偏离当前圆环的决定,是临时更新雷达的候选信号。可用轻量ADR说明新位置、文字、理由并链接触发决定;暂不更新时保存候选清单,下一次重扫不漏掉。它记录共享经验,不必套用改变共同原则的严格承诺投票。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Using a Technology Radar · 查看原书依据
Decision-driven blip additions or updates are best moved forward via another ADR. If it’s an entirely new blip, then this ADR should be raised by the team or individual who took the initial decision. If it’s a blip update, then this responsibility will likely fall to someone with a cross-system (probably architecture, but possibly a
参考来源
- 位置:《Facilitating Software Architecture》第11章《Using a Technology Radar》(来源项目 /Users/wangyi/claudecodeProject/bookBase/book-sources;源文件:extracted/Facilitating Software Architecture/_epub-src/OEBPS/ch11.html)
- 结论依据:原文分新点与更新的发起者,强调轻量ADR及可延期到下次sweep。
- 原始内容:Decision-driven blip additions or updates are best moved forward via another ADR. If it’s an entirely new blip, then this ADR should be raised by the team or individual who took the initial decision. If it’s a blip update, then this responsibility will likely fall to someone with a cross-system (probably architecture, but possibly a