Traceability for Model Checking Sample Clauses

Traceability for Model Checking. ‌ Over the past two decades, model checking in its various flavors has made impressive progress in terms of applicability in industry. As one example, the approach has become a standard technique for the verification of hardware circuits. As another example, this author’s company applies model checking to verify interlocking system configurations for customers from railway in- dustry, where the configurations are specified in a domain-specific language and then automatically verified for sanity and safety. Apart from the capability to automatically verify system properties provided in temporal logic, a question that commonly arises in industrial projects in safety-critical domains is that of tracing. For the technique to be of value for certification-related activities, it must be possible to identify and relate the configurations and results of the verification process, which naturally leads to the notion of traceability, the purpose of which is to relate certain information and artefacts related to the verification process. Questions to which a traceability implementation should be able to automatically provide answers include: • Is requirement X satisfied for model Y? • Which model checking queries exercise requirement X? • Which is the last model version for which model checking query X failed? It is no surprise that traceability typically is stored as some form of database which relates entities according to a well-defined scheme. We do not con- tribute to these fundamentals, but rather present a scheme that appears well-suited for covering industrial needs related to model checking for safety- critical systems.