Commit c75fcc71 authored by Ben Engel's avatar Ben Engel
Browse files

Update efforts from Excel from review meeting

parent 8b8e3c65
......@@ -13,7 +13,6 @@ 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* | 100 man-days
| *Service Provider* | Documentation of basic types parts of the specification. ~25% of effort.
|===
.LC-CompoundTypes
......@@ -26,7 +25,6 @@ This WP will address the semantic description of the compound datatypes (structs
| *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* | 100 man-days
| *Service Provider* | Documentation of compound types parts of the specification. ~25% of effort.
|===
.LC-Expressions
......@@ -38,7 +36,6 @@ This comprises the generic parts of expressions (e.g. arithmetic, logic, etc.) b
| *Responsibles* | P. Mai
|*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* | 50 man-days
| *Service Provider* | Documentation of expression language parts of the specification. ~25% of effort.
|===
.LC-Syntax
......@@ -48,7 +45,6 @@ This comprises the generic parts of expressions (e.g. arithmetic, logic, etc.) b
| *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. To cover functional scenarios, abstract descriptions of road topologies/infrastructure elements have to be included. For the use case of regulatory reviews, a natural-language syntax has to be supported.
| *Effort* | 100 man-days
| *Service Provider* | Documentation of language syntax. ~25% of effort.
|===
......@@ -87,7 +83,6 @@ This WP will address the necessary ways of packaging functionality into librarie
| *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* | 50
| *Service Provider* | Documentation of library, modules, packaging and namespace parts of the specification. ~15% of effort.
|===
.LC-Transfer1x
......@@ -97,7 +92,6 @@ This WP will address the necessary ways of packaging functionality into librarie
| *Responsibles* | J. Krasser
|*Deliverable* | Semantic extensions to the OpenSCENARIO 2.0 language to support specific 1.0/1.x concepts not otherwise supported. This WP will monitor the featureset of both projects and provide recommendations accordingly. It will also coordinate with the corresponding WPs from OSC 1.x. Input for LC-Syntax on syntax aspects of these extensions. Semantic mapping (migration path) from the most recent OpenSCENARIO 1.x version to OpenSCENARIO 2.0
| *Effort* | 70
| *Service Provider* | Documentation of the additonal features and the semantic mapping from OpenSCENARIO 1.0 to OpenSCENARIO 2.0 (15% of effort)
|===
==== Domain Model
......@@ -109,7 +103,6 @@ This WP will address the necessary ways of packaging functionality into librarie
| *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* | 40
| *Service Provider* | Finalization of the UML model draft (10%).
|===
.DM-Ontology
......@@ -127,8 +120,7 @@ This WP will address the necessary ways of packaging functionality into librarie
- guidelines for how to use computer reasoning to assist people in creating abstract-level scenarios that are complete and logically coherent
| *Effort* | 100
| *Service Provider* | Tasks to be performed by a service provider. Also estimate the % of total effort for this WP.
| *Effort* | 60
|===
.DM-AbstractionRoads
......@@ -138,7 +130,6 @@ This WP will address the necessary ways of packaging functionality into librarie
| *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* | 30
| *Service Provider* | Finalization of the UML model draft (10%).
|===
.DM-Extensibility
......@@ -148,10 +139,9 @@ This WP will address the necessary ways of packaging functionality into librarie
This WP will address the ability of adding and removing entities for the standard domain-model
| *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* | 20 man-days
| *Service Provider* | Documentation of the domain model extensibility chapter . ~15% of effort.
| *Effort* | 20
|===
.DM-Transfer1x
......@@ -160,8 +150,7 @@ This WP will address the ability of adding and removing entities for the standar
|*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* | 30 (Could not find the actual number from the meeting...)
| *Service Provider* | Finalization of the UML model draft (10%).
| *Effort* | 30
|===
==== Usage & Pragmatics
......@@ -173,7 +162,6 @@ This WP will address the ability of adding and removing entities for the standar
| *Responsibles* | F. Bock
| *Deliverable* | Unified process for the scenario creation workflow, that covers all use cases mentioned in the use case section of the concept project document. The resulting process should be based on already existing workflows and incorporate the input from all working group members. Process documentation should use a common format (such as, e.g., UML).
| *Effort* | 50
| *Service Provider* | Assistance with the creation of the process diagram, polishing.
|===
.UP-ScenarioAbstractionConcretization
......@@ -184,7 +172,6 @@ This WP will address the ability of adding and removing entities for the standar
| *Responsibles* |
| *Deliverable* | Documentation & guidelines on transitioning between different degrees of scenario abstraction. Requirements to Language Concepts WPs.
| *Effort* | 50
| *Service Provider* |
|===
.UP-SuccessCriteria
......@@ -194,7 +181,6 @@ This WP will address the ability of adding and removing entities for the standar
| *Responsibles* |
| *Deliverable* | Guidelines & reccomendations for success criteria of various scenario types. Requirements to Language Concepts Wps.
| *Effort* | 30
| *Service Provider* |
|===
.UP-TestDefinition
......@@ -205,8 +191,7 @@ This WP will address the ability of adding and removing entities for the standar
| *Deliverable* | Clarification of boundaries between test case & scenarios
Workflow guidelines (e.g. when integrated with a scenario vs. defined separately)
| *Effort* | 60
| *Service Provider* | Finalization and review (10%)
| *Effort* | 30
|===
.UP-Transfer1x
......@@ -218,25 +203,16 @@ Apart from the migration rules, any other interfacing forms should also be discu
| *Responsibles* | Sandeep Pendharkar
| *Deliverable* | Migration guidelines from 1.x to 2.0
| *Effort* | 50
| *Service Provider* |
|===
==== Feature Subset
==== Feature Subsets
.FS-FeatureSubSetsConcept
.FS-FeatureSubsetsConcept
[cols="1,5",caption='WP {counter:wp1}: ']
|===
|*Description* | Create a concept for support of predefined feature subsets of the standard. If viable, propose specific feature subsets and guidelines/methodology for validating them.
| *Responsibles* | M. Kluge
|*Deliverable* | Concept to fragment content of the standard into clusters (feature subsets). Has to contain the approach on how to cluster the content (e.g. on domain model level), a first draft of viable feature subsets and an idea on how to check language files for feature subset compatibility. Definition and documentation of feature subsets based on first draft provided by successor work package FS-FeatureSubSetsConcept. Might also contain the addition of new elements in the language to declare feature subset compatibility. Definition, documentation and implementation of validation approach of language files against feature subsets. Necessary for actual usage of feature subsets. An example for such a subset may be an OpenSCENARIO 1.0 compatible subset.
|*Deliverable* | Concept to fragment content of the standard into clusters (feature subsets). Has to contain the approach on how to cluster the content (e.g. on domain model level), a first draft of viable feature subsets and an idea on how to check language files for feature subset compatibility. Definition and documentation of feature subsets.. Might also contain the addition of new elements in the language to declare feature subset compatibility. Definition, documentation and implementation of validation approach of language files against feature subsets. Necessary for actual usage of feature subsets. An example for such a subset may be an OpenSCENARIO 1.0 compatible subset.
| *Effort* | 100 man-days
| *Service Provider* | Maybe language checks and possibly UML model finetuning (20%).
|===
.Total effort
[options="header", cols="1,2,2,2"]
|===
| WP No. | Project member (man-days) | Service Provider (man-days) | Total (man-days)
||||
|===
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