知识卡片
条件与合理性检查互补
条件监控检查进程设备状态及设计假设,如校验和;合理性检查则利用设计、系统状态或数据知识,判断某次操作或输出是否可信,常放在接口。监控本身应简单且受验证,避免引入新错误。自检可由组件或监控器触发,主动确认自身操作而非仅依靠外部存活信号。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
- · 第04章 可用性
原书出处 · 1 处
- 可用性 · 查看原书依据
Sanity checking. This tactic checks the validity or reasonableness of specific operations or outputs of a component. It is typically based on a knowledge of the internal design, the state of the system, or the nature of the information under scrutiny. It is most often employed at interfaces, to examine a specific information flow.
参考来源
- 位置:《Software Architecture in Practice, 4th Edition》第4章《可用性》(来源项目:book-sources;源文件:extracted/Software Architecture in Practice, 4th Edition/_epub-src/ch04.html)
- 结论依据:原文的定义、机制或比较支持“条件监控检查进程设备状态及设计假设,如校验和;合理性检查则利用设计、系统状态或数据知识,判断某次操作或输出是否可信,常放在接口”;正文保留其条件与取舍。
- 原始内容:Sanity checking. This tactic checks the validity or reasonableness of specific operations or outputs of a component. It is typically based on a knowledge of the internal design, the state of the system, or the nature of the information under scrutiny. It is most often employed at interfaces, to examine a specific information flow.