Commit a6252d71 authored by Benjamin Engel's avatar Benjamin Engel
Browse files

Add WP LC-Syntax writeup

parent 01c84d88
......@@ -9,7 +9,7 @@ A breakdown of the project into individual work packages and the corresponding e
|*Description* | Temporal aspects of the OpenSCENARIO 2.0 language and its execution
| *Responsibles* | M. Büker, R. Heidtman, Y. Hollander, H. Hungar
|*Deliverable* | Full description of the temporal aspects of the language, including formal model if any
| *Effort (Man-days)* |Estimated work effort to complete this WP.
| *Effort* |Estimated work effort to complete this WP.
| *Service Provider* | Tasks to be performed by a service provider. Also estimate the % of total effort for this WP.
|===
......@@ -17,10 +17,10 @@ A breakdown of the project into individual work packages and the corresponding e
[cols="1,5",caption='WP {counter:wp1}: ']
|===
|*Description* | Syntax definition of the OpenSCENARIO 2.0 language
| *Responsibles* | Y. Hollander, R. Heidtman
|*Deliverable* | Full syntax definition, including grammar, of the OpenSCENARIO 2.0 language.
| *Effort (Man-days)* |Estimated work effort to complete this WP.
| *Service Provider* | Tasks to be performed by a service provider. Also estimate the % of total effort for this WP.
| *Responsibles* | R. Hadar
|*Deliverable* | Full syntax definition, including grammar, of the OpenSCENARIO 2.0 language. Basic building blocks are file organization, type definitions, compound type definitions and their internals, temporals, behavior description and expressions. Integration of the other WG syntax definition into a single syntactic entity that shares the same look and feel.
| *Effort* | 35 man-days
| *Service Provider* | Documentation of language syntax. ~25% of effort.
|===
.LC-CompoundTypes
......@@ -29,7 +29,7 @@ A breakdown of the project into individual work packages and the corresponding e
|*Description* | Compound types for OpenSCENARIO 2.0
| *Responsibles* | Y. Hollander
|*Deliverable* | Semantic description of the definition, inheritance and extensiblity mechanisms for all compound data types of the OpenSCENARIO 2.0 language. Input for LC-Syntax on syntax aspects of the compound data types.
| *Effort (Man-days)* |Estimated work effort to complete this WP.
| *Effort* |Estimated work effort to complete this WP.
| *Service Provider* | Tasks to be performed by a service provider. Also estimate the % of total effort for this WP.
|===
......@@ -42,7 +42,7 @@ This WP will address the semantic description of the basic generic datatypes (in
| *Responsibles* | Sharon Rosenberg
|*Deliverable* | Semantic description of the definition of all basic, i.e. non-compound data types of the OpenSCENARIO 2.0 language. Input for LC-Syntax on syntax aspects of the basic data types.
| *Effort (Man-days)* | 100
| *Effort* | 100 man-days
| *Service Provider* | Documentation of basic types parts of the specification. ~25% of effort.
|===
......@@ -54,7 +54,7 @@ This WP will address the semantic description of the basic generic datatypes (in
This comprises the generic parts of expressions (e.g. arithmetic, logic, etc.) based on the properties of the domain model, as well as ways to define more complex domain-specific expressions.
| *Responsibles* | P. Mai, J. Krasser
|*Deliverable* | Full semantic description of the expression language of the OpenSCENARIO 2.0 language. Input for LC-Syntax on syntax aspects of the expression language.
| *Effort (Man-days)* | 50 person days
| *Effort* | 50 man-days
| *Service Provider* | Documentation of expression language parts of the specification. ~25% of effort.
|===
......@@ -66,7 +66,7 @@ This comprises the generic parts of expressions (e.g. arithmetic, logic, etc.) b
As the levels of abstraction have been raised, so the effort and understanding needed for a simulation engine to implement support for this standard is raised. As such, the semantics of a scenario become more important: to give an unambiguous understand of a) whether that scenario could be executed at all; b) whether that scenario could be executed on a given map; c) how to execute that scenario unambigously.
| *Responsibles* | I. Whiteside, Y. Hollander (maybe), S. Rosenberg (maybe)
|*Deliverable* | Semantic rules for the OpenSCENARIO 2.0 language.
| *Effort (Man-days)* | Estimated work effort: 100 man-days
| *Effort* | 100 man-days
|===
.LC-Libraries
......@@ -77,7 +77,7 @@ As the levels of abstraction have been raised, so the effort and understanding n
This WP will address the necessary ways of packaging functionality into libraries and modules in ways that foster re-use across users and implementations. Related namespacing problems are addressed. Relation to OpenSCENARIO 1.0 re-use concepts will be addressed.
| *Responsibles* | P. Mai, Y. Hollander
|*Deliverable* |Full semantic description of the library, modules, packaging and namespace aspects of the OpenSCENARIO 2.0 language. Input for LC-Syntax on syntax aspects of the libraries, modules, packaging and namespaces aspects.
| *Effort (Man-days)* | 50 person days
| *Effort* | 50 man-days
| *Service Provider* | Documentation of library, modules, packaging and namespace parts of the specification. ~15% of effort.
|===
......@@ -87,7 +87,7 @@ This WP will address the necessary ways of packaging functionality into librarie
|*Description* | Additional features in OpenSCENARIO 2.0 to support OpenSCENARIO 1.0/1.x features not otherwise part of 2.0
| *Responsibles* | Y. Hollander, J. Krasser
|*Deliverable* | Semantic extensions to the OpenSCENARIO 2.0 language to support specific 1.0/1.x concepts not otherwise supported. Input for LC-Syntax on syntax aspects of these extensions.
| *Effort (Man-days)* |Estimated work effort to complete this WP.
| *Effort* |Estimated work effort to complete this WP.
| *Service Provider* | Tasks to be performed by a service provider. Also estimate the % of total effort for this WP.
|===
......@@ -97,7 +97,7 @@ This WP will address the necessary ways of packaging functionality into librarie
|*Description* | Create road network domain model based on concept project proposal.
| *Responsibles* | M. Kluge, J.Kaths
|*Deliverable* | UML entity definition of the road network, which provides an intuitive way of addressing elements in the network. This for example will be used to define conditions in the behavior definition, e.g. "turn right at the second 4-way junction". An ID based access with detailed knowledge of the road network content must also be possible. The abstract road network domain model should allow the usage of different map sources like OpenDRIVE in OpenSCENARIO 1.0 or HD maps.
| *Effort (Man-days)* | 30 (Could not find the actual number from the meeting...)
| *Effort* | 30 (Could not find the actual number from the meeting...)
| *Service Provider* | Finalization of the UML model draft (10%).
|===
......@@ -107,7 +107,7 @@ This WP will address the necessary ways of packaging functionality into librarie
|*Description* | Rework entity definition from concept project with regard to OpenSCENARIO 1.0.
| *Responsibles* | J. Tscheak (maybe), M. Kluge, J.Kaths
|*Deliverable* | Consolidated UML entity definition that covers existing features of OpenSCENARIO 1.0 standard. Differences between 1.0 and the concept project domain model should be identified, listed and resolved. Deviations should only be allowed when necessity is clearly identified and reasoned. This work package is a predecessor of DM-Extend2x and should be finished first.
| *Effort (Man-days)* | 30 (Could not find the actual number from the meeting...)
| *Effort* | 30 (Could not find the actual number from the meeting...)
| *Service Provider* | Finalization of the UML model draft (10%).
|===
......@@ -117,7 +117,7 @@ This WP will address the necessary ways of packaging functionality into librarie
|*Description* | Extend Entity Definition from Concept project and other working packages towards OSC 2.0
| *Responsibles* | J. Kaths, M. Kluge
|*Deliverable* | UML entity definition that extends the ones from OSC 2.0 Concept Project and from work package DM-Transfer1x with high level scenario descriptions (e.g. drive()) and other missing features. It will also incorporate the road model developed in work package DM-AbstractionRoads. The result is the full entity definition for OSC 2.0. Similar to the separation of DM-AbstractionRoads, this work package is likely to be split into further work packages as the project progresses.
| *Effort (Man-days)* | 40
| *Effort* | 40 man-days
| *Service Provider* | Finalization of the UML model draft (10%).
|===
......@@ -130,7 +130,7 @@ This WP will address the ability of adding and removing entities for the standar
| *Responsibles* | S. Rosenberg
|*Deliverable* | Description of how to add entities (attributes, actor, action, etc.) to the design model and how to leverage the modified model for user specific scenarios and coverage,
| *Effort (Man-days)* | 20
| *Effort* | 20 man-days
| *Service Provider* | Documentation of the domain model extensibility chapter . ~15% of effort.
|===
......@@ -140,7 +140,7 @@ This WP will address the ability of adding and removing entities for the standar
|*Description* | Develop ontology to establish relations between entities
| *Responsibles* | S. Kraines, F. Sanchez, I. Whiteside, P. Parekh
|*Deliverable* | Extension of the entity definition delivered by WP DM-Extend2x with an ontology that describes relations between the entities to enable inferrment.
| *Effort (Man-days)* | 60
| *Effort* | 60 man-days
| *Service Provider* | Tasks to be performed by a service provider. Also estimate the % of total effort for this WP.
|===
......@@ -150,7 +150,7 @@ This WP will address the ability of adding and removing entities for the standar
|*Description* | Create a concept for partial support of the standard
| *Responsibles* | M. Kluge
|*Deliverable* | Concept to fragment content of the standard into clusters (features sets). Has to contain the approach on how to cluster the content (e.g. on domain model level), a first draft of viable feature sets and an idea on how to check language files for feature set compatibility. Predeccesor for work packages FS-FeatureSetsDefinition.
| *Effort (Man-days)* | 30 (Estimation by M Kluge.)
| *Effort* | 30 man-days
| *Service Provider* | Not applicable.
|===
......@@ -160,7 +160,7 @@ This WP will address the ability of adding and removing entities for the standar
|*Description* | Define viable feature sets
| *Responsibles* | M. Kluge
|*Deliverable* | Definition and documentation of feature sets based on first draft provided by successor work package FS-FeatureSetsConcept. Might also contain the addition of new elements in the language to declare feature set compatibility. Predeccesor for work packages FS-FeatureSetsValidation.
| *Effort (Man-days)* | 30 (Estimation by M Kluge.)
| *Effort* | 30 man-days
| *Service Provider* | Language checks and possibly UML model finetuning (20%).
|===
......@@ -170,7 +170,7 @@ This WP will address the ability of adding and removing entities for the standar
|*Description* | Define feature set validation method
| *Responsibles* | M. Kluge
|*Deliverable* | Definition, documentation and implementation of validation approach of language files against feature sets. Necessary for actual usage of usage of feature sets.
| *Effort (Man-days)* | 20 (Estimation by M Kluge.)
| *Effort* | 20 man-days
| *Service Provider* | Language checks and possibly UML model finetuning (20%).
|===
......
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