Next to the ASAM ODS API, ASAM ODS defines the ASAM ODS Base Model. The base model is describing all elements, attributes, and relations that are part of ASAM ODS. It is an abstract model that is used as a reference to describe the data that is used within a project.
Therefore, it defines the scope of allowed application models. All colored elements (please see HighQSoft ASAM ODS Base Model Poster below) are fully compatible with the ASAM ODS standard. These colored elements and their added attributes and relates get recognized by all ASAM ODS clients automatically. All elements in grey describe information that can be added to describe special cases that are not covered by colored elements. There are specific cases in e.g. the NVH domain. Usually, these elements are avoided.
The ASAM ODS Application model is a derivation of the ASAM ODS Base Model. It uses the specification and defines a compatible model that fits the required use case.
While the descriptive part for Project Information, Test Objective, Test Environment, and Test Steps is generally fully flexible, standardization is implemented to describe the test data itself. This includes the structure of the data, channel names, and its physical description.
There are standards to describe application models for different domains (e.g. ISO for crash testing) or applications (openMDM). Its content strongly depends on the domain (e.g. engine), use-case, and workflow of the customer as well as the data generated by the project. The task of deriving an application model is usually performed by
At HighQSoft GmbH, we got more than 25 years of first-hand experience with ASAM ODS Applications Models. We developed models for all existing domains and many different kinds of projects.
Usually, testing data is provided in advance for a first analysis. Within a workshop, we discuss the data as well as available enterprise information and processes. As a result, we can design the application model. Not only will it contain all relevant information but it is also optimized for reading processes and databases.
The definition of a data model is a standard task and can be done quickly - some data consolidation is performed in advance. The application model can be reviewed and verified with our ASAMCommander without any server setup.
The derivation of an application model focuses on two aspects:
Additional file formats need to be integrated or other information is required to fulfill a use-case? No problem! We can expand your Test Data Management Solution step by step.
Often the requirement to stay flexible in data management is a very present one. Data model changes within our products are performed quickly and the Test Data Management solutions are always able to adapt to new requirements.
Especially, unplanned changes to a running system come with high efforts. Efforts are usually created by unknowns and details lost over further development of the system.
With our products, all information is fully transparent and can be changed, consolidated, and migrated in a controlled manner.