Download now - ASAM

46
case studies
Visu-IT! GmbH:
Solutions Guide 2011
aSam fSX & aSam mDX
Based function Documentation –
generated During Build Process
By choosing an ASAM based solution for our function documentation
tool chain we are flexible concerning the selection
of 3rd party document formatters as well as in the
merge with other documentation parts supplied in ASAM
FSX and ASAM MDX Format.
(Lothar Michel, Entwicklung RP-Tools/
Software Antrieb, AUDI AG)
Summary
Challenge: The data necessary for a function
documentation of simulation models is spread
Figure 1: FunDoc editor with interactive smart viewing functionalities
over several development tools. The challenge
is to put all these data together – automatically.
Solution: The objective is to connect to several
development tools, extract the needed data and
place the gathered information at user’s disposal
for edit or print. In order to be able to further
process the gathered data, standard exchange
formats from ASAM shall be used.
Key Benefits: The time consuming task of collecting
data from different development tools can
be automated and by using the ASAM standard
exchange formats (MDX, FSX, CDF, CC), further
standard compliant tools can be integrated
in the function documentation process.
Situation
At AUDI, several tools are used in the model
driven function development. When generating
the function documentation, the relevant data
must be manually extracted from these tools.
This time consuming and tedious task must be
repeated each time when the documentation
has to be updated e.g. due to updates in the
model or in the data interface.
ChallengeS
To avoid the time consuming task of extracting
the needed data manually from the different
tools again and again, a tool should be developed
which automates this task. The tool must
be able to handle updates, both of the simulation
models and of the interfaces. When simulation
models have been updated, the tool must
notify the user that a change happened and best
what is the change. The tool FunDoc meets this
challenge by performing a “model-diff” on picture
level (in order to be independent from the
modelling tool). The status (e.g. new, changed,
removed) is visually displayed directly in the
documentation.