Commit 7dc19ef2 authored by Michael Kluge's avatar Michael Kluge
Browse files

First draft of entity definition chapter WPs 1 and 2.

parent 84383a77
Pipeline #905 passed with stage
in 14 seconds
......@@ -29,19 +29,19 @@ The technical content description shall be understandable for readers with an en
==== Domain Model
===== Entity Definition
[NOTE]
Responsibles for filling this sub-chapter: J. Tscheak (maybe), M. Kluge, J.Kaths, F. Bock (maybe), S. Rosenberg (maybe)
WP DM-Transfer1x - Rework Entity Definition from Concept project with regard to OSC 1.0
overhaul entity definition with regard to OSC 1.0 (maybe Jupp Tscheak, Michael, Jakob)
* identify deviations
* clarify if deviations are necessary or should
* clarify naming / terminology
* create a mapping where necessary
WP DM-Extend2x - Extend Entity Definition from Concept project and from WP DM-Transfer1x towards OSC 2.0
identify entities and their actions / methods that are introduced by high-level description of OSC 2.0 (so not part of OSC 1.0) (maybe Florian Bock, Michael Kluge, Jakob Kaths, maybe Sharon Rosenberg)
* identify new entities, their actions and attributes that are necessary to cover high-level scenario descriptions in OSC 2.0 (e.g. Road, drive(), etc.)
* integrate them properly in Domain Model
* close interrelation on working-level with language group (was a lack during concept phase)
The definition of the domain model specific entities is essential as those build the core of new language. A full support of the https://www.asam.net/standards/detail/openscenario/#[OpenSCENARIO 1.0 standard], which has already been published by ASAM, is one major requirement for OpenSCENARIO 2.0. This includes a full migration path from the 1.x versions to the language to be developed in this project, which directly leads to the first work packages for the domain model group:
*WP_DM1_Transfer1x*
The domain model, that has been defined in the https://www.asam.net/index.php?eID=dumpFile&t=f&f=3460&token=14e7c7fab9c9b75118bb4939c725738fa0521fe9[OpenSCENARIO 2.0 Concept Project], did not focus on the compatibility to OpenSCENARIO 1.0. That initial version 1.0 already contains multiple domain model entities though, for whom possible deviations to the new model have to be identified. Fore each of those deviations it has to be defined how they should be handled in order to achieve compatibility. Inconsistent naming and terminology has to be resolved or, if this is not feasible, a mapping between entities in both models has to be defined. All entities in the 1.0 model must have a counterpart in 2.0.
[NOTE]
Identify entities and their actions / methods that are introduced by high-level description of OSC 2.0 (so not part of OSC 1.0) (maybe Florian Bock, Michael Kluge, Jakob Kaths, maybe Sharon Rosenberg)
*WP_DM2_Extend2x*
The existing model draft has to be refined and extended, as the result of the concept project focused on "most important properties, attributes, possible actions and interrelations.". New entities, their actions and attributes might have to defined, for example to cover high-level scenario descriptions, which will be introduced in OpenSCENARIO 2.0. All different use cases for the scenario definition and contents from the 1.0 domain model have to be properly integrated in the final model for 2.0. As experienced in the development of the 2.0 concept paper, a close working-level interaction and interrelation with the language group is essential for the success of this work package. This should be established already in the beginning of the project.
===== Extensibility
Responsibles for filling this sub-chapter: S. Rosenberg, H. Bothe (maybe)
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment