Development Process using tools from Visu-IT!
In most publications, the automotive development process for electronic control
units is described using the V-cycle. In this development process there exist several interfaces between the different process phases from requirements engineering to implementation and back to verification.
Central label management in a global data dictionary
Support of SW development and ASAP2 file generation on project scope
-> The ADD-DDS interface/link
closes the (process-)gap between function- and SW development and assures data consistency!
Different data exchange formats are used for these different interfaces.
Interface between function- and software development
Today no easy and widespread data exchange format for the interface between function- and software development exists. This gap often causes inconsistencies between function- and software engineers.
The comprehensive data declaration tools from Visu-IT! help in maintaining data consistency.
Visu-IT! offers both:
A tool which covers the needs of function
engineers -> ADD (Automotive Data Dictionary)
The tool ADD serves as a global database
which handles several versions
of objects/labels defined in the ECU function specification. This tool is
mainly used by function engineers.
And a tool which covers the needs of software developers and calibration engineers -> DDS (Data Declaration System)
The tool DDS operates on project scope
and focuses on the support of the
ECU software development as well as the support of measurement and
calibration needs. It is used by software as well as calibration
engineers, but not by function engineers.
The two tools interoperate smoothly and thus close the gap
and ensure data
between these two process steps.
Interface between software development
and measurement & calibration. This interface focuses on the
description of variables and calibration parameters which should be
measured or tuned during the calibration step. Details about their
software implementation are no longer important at this point, but
rather information about measure- and calibration subjects, like
resolutions, limits, physical addresses, etc. For this interface, several ASAM compliant data exchange formats exist, e.g. ASAM MCD 2, calibration data formats (e.g. CDF) or calibration data initialization (e.g. PACO).