View source for Simulink/T-VEC Examples
From T-VEC Wiki
The most successful users of T-VEC Tester for Simulink (SL2TVEC) follow a few key guidelines: #They development the models with verification in mind - they are aware of those modeling constructs and patterns that result in safe systems #They perform modeling and the verification activities supported by SL2TVEC iteratively #Understand the tool is performing model checking, and that tests are a byproduct of this process #Understand that the Simmulink/Stateflow tool is continously evolving, and the SL2TVEC integration process may take time to catchup to the changes in every new Simulink release, which further emphasizes point #1. ==Key Guidelines== This section first discusses some key elements that must be used to support and configure the model translation that results in a T-VEC project for model analysis and test generation. ===Signal Ranges=== ===Test Sequences=== ===Assertions=== Assertions are general purpose mechanisms that can be used to specify additional constraint that are external to the model. Such constraints can be used for: *Defining implicit design constraint such as natural laws *Modeling safety properties *Defining additional tests ==Example Links==
Retrieved from "
What links here
About T-VEC Wiki