What Causes a System to Satisfy a Specification?
| dc.creator | Chockler, Hana | |
| dc.creator | Halpern, Joseph Y. | |
| dc.creator | Kupferman, Orna | |
| dc.date | 2003-12-17 | |
| dc.date.accessioned | 2026-07-07T03:20:44Z | |
| dc.date.available | 2026-07-07T03:20:44Z | |
| dc.description | Even when a system is proven to be correct with respect to a specification, there is still a question of how complete the specification is, and whether it really covers all the behaviors of the system. Coverage metrics attempt to check which parts of a system are actually relevant for the verification process to succeed. Recent work on coverage in model checking suggests several coverage metrics and algorithms for finding parts of the system that are not covered by the specification. The work has already proven to be effective in practice, detecting design errors that escape early verification efforts in industrial settings. In this paper, we relate a formal definition of causality given by Halpern and Pearl [2001] to coverage. We show that it gives significant insight into unresolved issues regarding the definition of coverage and leads to potentially useful extensions of coverage. In particular, we introduce the notion of responsibility, which assigns to components of a system a quantitative measure of their relevance to the satisfaction of the specification. | |
| dc.identifier | https://arxiv.org/abs/cs/0312036 | |
| dc.identifier | http://arxiv.org/abs/cs/0312036 | |
| dc.identifier.uri | http://salesiana.dossiersoluciones.com/handle/123456789/31934 | |
| dc.subject | Logic in Computer Science | |
| dc.subject | Artificial Intelligence | |
| dc.subject | F.4.1; F.3.1; I.2.4 | |
| dc.title | What Causes a System to Satisfy a Specification? | |
| dc.type | text |