知识卡片
扩展状态回应真实需要
时限性选择可用Expired提醒到期重新审视,但重审仍应形成新决定,不等同自动迁移。系统无替代地结束可用Retired。“没有采纳改动”通常也是接受保持现状的决定,因此未必需要Rejected状态。新增状态要看是否减少读者歧义,而非只为模板更全。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Architectural Decision Records · 查看原书依据
The first nonstandard status is “Expired,” shown in Figure 6-3. I’ve used this with a number of clients when a decision is time sensitive and they want to revisit it after a certain period of time has passed. For example, perhaps they had a need to deliver a product to market, and at the
参考来源
- 位置:《Facilitating Software Architecture》第06章《Architectural Decision Records》(来源项目 /Users/wangyi/claudecodeProject/bookBase/book-sources;源文件:extracted/Facilitating Software Architecture/_epub-src/OEBPS/ch06.html)
- 结论依据:原文分别讨论Expired、Retired和认为不必要的Rejected,以说明扩展点的利弊。
- 原始内容:The first nonstandard status is “Expired,” shown in Figure 6-3. I’ve used this with a number of clients when a decision is time sensitive and they want to revisit it after a certain period of time has passed. For example, perhaps they had a need to deliver a product to market, and at the