You can now reply by email directly to Gitlab notifications you receive in your inbox. Your replies will be automatically created as comments in the respective issue/MR. Give it a try and share any feedback with the ASAM office!

3-1_required_resources.adoc 10.5 KB
Newer Older
Benjamin Engel's avatar
Benjamin Engel committed
1 2 3 4 5 6 7
=== Required 
A breakdown of the project into individual work packages and the corresponding effort required to complete them. Effort should be given in man-hours.

==== Effort

===== Breakdown by Work Packages [WPs]

8
.WP LC-Temporal
Benjamin Engel's avatar
Benjamin Engel committed
9 10
[cols="1,2"]
|===
11 12 13 14
| *WP Number* | LC-Temporal
| *Responsibles* | M. Büker, R. Heidtman, Y. Hollander, H. Hungar
|*Title / Description* | Temporal aspects of the OpenSCENARIO 2.0 language and its execution
|*Deliverable*	| Full description of the temporal aspects of the language, including formal model if any
15 16
| *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.
17 18 19 20 21 22 23 24 25
|===

.WP LC-Syntax
[cols="1,2"]
|===
| *WP Number* | LC-Syntax
| *Responsibles* | Y. Hollander, R. Heidtman
|*Title / Description* | Syntax definition of the OpenSCENARIO 2.0 language
|*Deliverable*	| Full syntax definition, including grammar, of the OpenSCENARIO 2.0 language.
26 27
| *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.
28 29 30 31 32 33 34 35 36
|===

.WP LC-CompoundTypes
[cols="1,2"]
|===
| *WP Number* | LC-CompoundTypes
| *Responsibles* | Y. Hollander
|*Title / Description* | Compound types for OpenSCENARIO 2.0
|*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.
37 38
| *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.
39 40 41 42 43 44 45 46 47
|===

.WP LC-BasicTypes
[cols="1,2"]
|===
| *WP Number* | LC-BasicTypes
| *Responsibles* | Y. Hollander
|*Title / Description* | Basic data types for OpenSCENARIO 2.0
|*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.
48 49
| *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.
50 51 52 53 54 55 56 57
|===

.WP LC-Expressions
[cols="1,2"]
|===
| *WP Number* | LC-Expressions
| *Responsibles* | P. Mai, J. Krasser
|*Title / Description* | Expression language for OpenSCENARIO 2.0
58 59 60 61 62

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.
|*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
| *Service Provider*	| Documentation of expression language parts of the specification. ~25% of effort.
63 64
|===

65 66 67 68 69
.WP LC-Semantics
[cols="1,2"]
|===
| *WP Number* | LC-Semantics
| *Responsibles* | I. Whiteside, Y. Hollander (maybe), S. Rosenberg (maybe)
70 71
|*Title / Description* | A well-defined semantics for OpenSCENARIO 2.0.

72 73 74 75 76
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.
|*Deliverable*	| Semantic rules for the OpenSCENARIO 2.0 language.
| *Effort (Man-days)*	| Estimated work effort: 100 man-days
|===

77 78 79 80 81 82
.WP LC-Libraries
[cols="1,2"]
|===
| *WP Number* | LC-Libraries
| *Responsibles* | P. Mai, Y. Hollander
|*Title / Description* | Libraries, Modules, Packaging and Namespace aspects of OpenSCENARIO 2.0
83 84

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.
85
|*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.
86 87
| *Effort (Man-days)*	| 50 person days
| *Service Provider*	| Documentation of library, modules, packaging and namespace parts of the specification. ~15% of effort.
Benjamin Engel's avatar
Benjamin Engel committed
88 89
|===

90 91 92 93 94 95 96
.WP LC-Transfer1x
[cols="1,2"]
|===
| *WP Number* | LC-Transfer1x
| *Responsibles* | Y. Hollander, J. Krasser
|*Title / Description* | Additional features in OpenSCENARIO 2.0 to support OpenSCENARIO 1.0/1.x features not otherwise part of 2.0
|*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.
97 98
| *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.
99
|===
Benjamin Engel's avatar
Benjamin Engel committed
100

101 102 103 104 105 106 107 108 109
.WP DM-AbstractionRoads
[cols="1,2"]
|===
| *WP Number* | DM-AbstractionRoads
| *Responsibles* | M. Kluge, J.Kaths
|*Title / Description* | Create road network domain model based on concept project proposal.
|*Deliverable*	| A road network UML domain model, 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
| *Service Provider*	| Finalization of the UML model draft (10%).
110
|===
Benjamin Engel's avatar
Benjamin Engel committed
111

112 113 114 115 116 117 118
.WP DM-Transfer1x
[cols="1,2"]
|===
| *WP Number* | DM-Transfer1x
| *Responsibles* | J. Tscheak (maybe), M. Kluge, J.Kaths
|*Title / Description* | Rework Entity Definition from Concept project with regard to OSC 1.0
|*Deliverable*	| Consolidated entity definition that covers existing features of OSC 1.0 and deviates only when necessity is clearly identified and reasoned. Needs to be finished before WP DM-Extend2x.
119 120
| *Effort (Man-days)*	| 30
| *Service Provider*	| Tasks to be performed by a service provider. Also estimate the % of total effort for this WP.
121 122 123 124 125 126
|===

.WP DM-Extend2x
[cols="1,2"]
|===
| *WP Number* | DM-Extend2x
Jakob Kaths's avatar
Jakob Kaths committed
127 128 129
| *Responsibles* | J. Kaths, M. Kluge
|*Title / Description* | Extend Entity Definition from Concept project and other working packages towards OSC 2.0
|*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.
130
| *Effort (Man-days)*	| 40
Jakob Kaths's avatar
Jakob Kaths committed
131
| *Service Provider*	| Finalization of the UML model draft (10%).
132 133 134 135 136 137
|===

.WP DM-Extensibility
[cols="1,2"]
|===
| *WP Number* | DM-Extensibility
Jakob Kaths's avatar
Jakob Kaths committed
138
| *Responsibles* | S. Rosenberg
139 140
|*Title / Description* | Develop technical concept for extensibility of Domain Model
|*Deliverable*	| Technical concept to enable standard-conform extensions of the Domain Model. This should cover special features that can be introduced by single users, but may be extended towards bigger feature sets that a whole user-group agrees upon. 
141 142
| *Effort (Man-days)*	| 40
| *Service Provider*	| Tasks to be performed by a service provider. Also estimate the % of total effort for this WP.
143 144 145 146 147 148
|===

.WP DM-Ontology
[cols="1,2"]
|===
| *WP Number* | DM-Ontology
Jakob Kaths's avatar
Jakob Kaths committed
149
| *Responsibles* | S. Kraines, F. Sanchez, I. Whiteside, P. Parekh
150 151
|*Title / Description* | Develop ontology to establish relations between entities
|*Deliverable*	| Extension of the entity definition delivered by WP DM-Extend2x with an ontology that describes relations between the entities to enable inferrment. 
152 153
| *Effort (Man-days)*	| 60
| *Service Provider*	| Tasks to be performed by a service provider. Also estimate the % of total effort for this WP.
154 155
|===

156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187
.WP FS-FeatureSetsConcept
[cols="1,2"]
|===
| *WP Number* | FS-FeatureSetsConcept
| *Responsibles* | M. Kluge
|*Title / Description* | Create a concept for partial support of the standard
|*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.)
| *Service Provider*	| Not applicable.
|===

.WP FS-FeatureSetsDefinition
[cols="1,2"]
|===
| *WP Number* | FS-FeatureSetsDefinition
| *Responsibles* | M. Kluge
|*Title / Description* | Define viable feature sets
|*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.)
| *Service Provider*	| Language checks and possibly UML model finetuning (20%).
|===

.WP FS-FeatureSetsValidation
[cols="1,2"]
|===
| *WP Number* | FS-FeatureSetsValidation
| *Responsibles* | M. Kluge
|*Title / Description* | Define feature set validation method
|*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.)
| *Service Provider*	| Language checks and possibly UML model finetuning (20%).
|===
Benjamin Engel's avatar
Benjamin Engel committed
188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211

.Total effort
[options="header", cols="1,2,2,2"]
|===
| WP No. | Project member (man-days) | Service Provider (man-days) | Total (man-days) 
||||
|===

==== Budget
This section details the budget required by the project to e.g. pay service providers and the funds to be provided by ASAM.

.Funds required for Service Providers
[options="header"]
|===
| Task Description | Effort| Cost (€700 / man-day) 
|||
|===

.Funds Provided by ASAM
[options="header"]
|===
| Amount (Euros)
|
|===