This site uses cookies. By continuing, your consent is assumed. Learn more

139.3fm shares

Verifying and validating automatically generated codeds

opinion

TargetLink performs the three different simulation modes without any changes to the model or the generated code.

IV&V Facility. Analyses of the...

TargetLink does this automatically in the background. Although code generators produce virtually flawless results, when compared to manual programming, the generated code still needs to be tested as well as the underlying specification.

TargetLink provides powerful and easy-to-use means to verify the generated code.

Keywords: Model-Based Design, Verification, Validation,...

The code tests are performed in the same simulation environment that was used to specify the underlying simulation model. Functional identity has been achieved when the simulation results match. TargetLink provides a three-step verification process which shows at the click of a button whether the specification the model and implementation the generated code are functionally identical.

Data is recorded for reference plots from the simulation model. Signals from selected blocks and state variables are automatically logged by TargetLink. The model-in-the-loop simulation captures the specified behavior of the model that is to be implemented in C code later on. The recorded signal plots act as the reference for the next verification steps.

Introduction

Model-in-the-loop simulation can also be used for detecting overflows of integer variables, and its results are used for simulation-based autoscaling. The code is generated and replaces the controller blocks in the simulation model for example, the same plant and stimulus signals.

News feed