ModelCheckingforEmbeddedSystems.pptVIP

Model Checking for Embedded Systems Edmund Clarke, CMU Embedded Software verification projects Bridging the gap between legacy code andformal specification Verification of a real-time operating system Verifying concurrent embedded C programs Certifying compilation with proof-carrying code More Efficient Model Checking Algorithms Counterexample-Guided Abstraction Refinement for Hybrid Systems Making Bounded Model Checking complete 1. Bridging the Gap between Legacy Code and Formal Specification Daniel Kroening Legacy Software Software is the most complex part of todays safety critical embedded systems Most embedded systems are legacy designs Written in a low level language such asANSI-C or even assembly language Existing tools do not address the verification problem Goal: Verify legacy code with respect to a formal specification A high level design Safety properties Verification of Legacy Code ANSI-C Bounded Model Checking Problem: Fixpoint computation is too expensive for software Idea: Unwind program into equation Check equation using SAT Advantages: Completely automated Allows full set of ANSI-C, including full treatment of pointersand dynamic memory Properties: Simple assertions Security (Pointers/Arrays) Run time guarantees (WECT) Current Project Future Work Interval abstraction for floating point aritmetic Concurrent ANSI-C programs (SpecC) Object oriented languages (C++, Java) Statechart-like specification language 2. Verification of a Real-Time Operating Systems Flavio Lerda Real-Time Operating System Present in many embedded systems Handles main functionalities Correctness is crucial Affects the safety of the whole system Two type of properties Timing properties Functional properties Timing Properties Worst Case Execution Time Analysis For ANSI-C Based on existing low-level analysis Uses bounded model checking Functional Properties Does the system behave as expected? Apply to different components of the OS Check behavioral properties Results Ca