General Information about ADD
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. Different data exchange formats are used for these different interfaces.
However, 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.
Moreover, large quantities of data definitions might be fragmented across a variety of files and might be redundant and inconsistent. These disparate data definitions do not adequately support the information needs of organizations in a dynamic business environment.
Therefore the objective is to map the existing data elements to "common data architecture" and to support the reuse of the data across the complete development cycle. This is one of the major challenges of a streamlined software development process. Reuse starts with the definition and maintenance of data definitions.
- the short name of the tool "A
ictionary" provides a standardization of all variable definitions for the customer. The user is supported in performing the integration step and several check operations are allocated.
The ADD database contains user information, container information, data objects and data types. ADD helps to ensure consistency, correct data declaration and reusability of data objects and -types. At the same time ADD avoids redundancy of data due to company wide availability and uniqueness of these data.
With ADD, a continuous data process
from the step "Function" to "Software" is possible. ADD closes this gap, ensures data consistency and thus improves the quality and reduces the efforts for the function- as well as for the software development.
The objective is to centralize the existing data elements to the "common data architecture" and support the reuse of the data for the function development part as well as to the software development. This means that everyone is able to select a data definition from a single source, where the data is stored unique, project- as well as editor- independent.
Thus it is ensured, that the data definitions are equal in the whole development process.
The main objectives for a seamless data definition covered by ADD are:
to provide a central and company-wide accessible database as a single source for data definitions
(project- as well as editor-independent!)
to ensure company(world)-wide availability and multi-user capability
to support consistency checks during the definition
to ensure data consistency by using versioning and lifecycle for all data definitions
to allocate data and data flow driven search and analyze capabilities
to provide a continuous data process from function- to software devlopment
to improve the quality of the interface description
to provide check operations of several hierarchy levels (modules, aggregates and projects) in a very early step of the development process
Management of data objects: Data objects can be created, modified, reused and deleted
Version management of data objects (versions and revisions)
Lifecycle of data objects (draft, fixed, obsolete)
Search for data objects
Grouping of data objects (container-concept)
Management of datatypes: Lifecycle of datatypes (released, obsolete)
Search for datatypes
Support the data type definition process
Management of master data
Show cross-references of a data object
Reference "System constants" to define value/array size
Show differences between workspace- and database entries
User/Role concept for the control of access authorization
Overview-picture of container with link to the data object definition
Creation of XML-format and support of other formats using style sheets (HTML for reports, MSR SW DTD...)
Management of physical units