An Instrumentation-Based Approach to Controller Model Validation

Authors:
Rance Cleaveland;Scott A. Smolka;Steven T. Sims
Affiliations:
Department of Computer Science, University of Maryland, Maryland, USA 20742;Department of Computer Science, Stony Brook University, Stony Brook, USA NY 11794-4400;Reactive Systems, Inc., Falls Church, USA VA 22046
Venue:
Model-Driven Development of Reliable Automotive Services
Year:
2006

Citing 0
Cited 3

Generating and Analyzing Symbolic Traces of Simulink/Stateflow Models

CAV '09 Proceedings of the 21st International Conference on Computer Aided Verification
Brace: an assertion framework for debugging cyber-physical systems

Proceedings of the 34th International Conference on Software Engineering
Analysis and testing of matlab simulink models: a systematic mapping study

Proceedings of the 2013 International Workshop on Joining AcadeMiA and Industry Contributions to testing Automation

Quantified Score

Hi-index	0.00

Visualization

Abstract

This paper discusses the concept of Instrumentation-Based Validation(IBV): the use of model instrumentation and coverage-based testing to validate models of embedded control software. IBV proceeds as follows. An engineer first formalizes requirements as assertions, or small models, which may be thought of as monitors that observe the behavior of the controller model as it executes. The engineer then instruments the model with these assertions and develops test suites with the aim of highlighting where assertion violations occur. To make our discussion of IBV more concrete, we also consider its implementation within the Reactis tool suite for the automated testing and validation of controller models given in ®/Stateflow®.