SOFTWARE DESIGN VERIFICATION AND VALIDATION - Software Design for Six-Sigma: A Roadmap for Excellence - page 519

19.6.2 dSPACE Targetlink Production Code Generator

dSPACE is an internationally reputable provider of complete system development
software (control desk and automation desk integreated development environment
(IDEs), targetlink model simulator, etc.), hardware (HIL testers, load-boxes), and
staff solutions for automotive and aerospace industries. Basing observations on page
213 of the 2008 dSPACE Product Catalog 13 illustrating the “workflow between
model design and code implementation,” dSPACE offers a complete MIL/SIL/PIL
integrated environment. The dSPACE design workflow, “modeling simulation and
code specification,” encompasses several tasks including behavioral validity checking
that can be tested in model in the loop paradigm. This stage is related to reference
checking. The next stage of the design process testing is software in the loop in which
production code is hosted in the simulation environment. This stage is related to
precision checking. The next stage of the design process facilitates “production code
target simulation,” which encompasses several tasks including target code verification
testing with processor in the loop evaluation. This stage is related to the optimization
of production code. What the architecture of this environment lacks is clarity as to the
configuration and interface needs and complexity required to link Simulink modeling,
third-party calibration tools and engine control unit (ECU) programmers. Again, the
onus is left to engineering for configuration and interface.

19.6.3 MxVDEV—Unit/System Test Tool Solution

Micro-Max Technology (Bologna, Italy) offers a foundation development environ-
ment, a virtual development bench of programs used for requirements capture, design,
development, and test of real-time control systems. Some components of this suite
include:

Mx-VDev unit/system test tool
Mx-Sim system simulator
Mx-automate continuous integration tool
Mx-Xchange test data interchange tool

Again, the configuration given in Figure 19.12 implies a complete development
environment yet remains vague in the areas of model development, integration, and
especially verification, validation, and test reporting as the project moves toward
completion along the right arm of the V. Alternatively, this figure indicates the
extensibility requirements of tool chains using the V design in which the Mx-VDev
unit test tool can provide an integral component for integration of test development.
Other issues involved with this and other tools include server/resource repository
storage, mapping, and configuration.

13 http://www.dSPACE.de.