3-1_required_resources.adoc

=== 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]

.WP LC-Temporal
[cols="1,2"]
|===
| *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
| *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.
|===

.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.
| *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.
|===

.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.
| *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.
|===

.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.
| *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.
|===

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

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.
|===

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

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
|===

.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

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.
|*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
| *Service Provider*	| Documentation of library, modules, packaging and namespace parts of the specification. ~15% of effort.
|===

.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.
| *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.
|===

.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%).
|===

.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.
| *Effort (Man-days)*	| 30
| *Service Provider*	| Tasks to be performed by a service provider. Also estimate the % of total effort for this WP.
|===

.WP DM-Extend2x
[cols="1,2"]
|===
| *WP Number* | DM-Extend2x
| *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.
| *Effort (Man-days)*	| 40
| *Service Provider*	| Finalization of the UML model draft (10%).
|===

.WP DM-Extensibility
[cols="1,2"]
|===
| *WP Number* | DM-Extensibility
| *Responsibles* | S. Rosenberg
|*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. 
| *Effort (Man-days)*	| 40
| *Service Provider*	| Tasks to be performed by a service provider. Also estimate the % of total effort for this WP.
|===

.WP DM-Ontology
[cols="1,2"]
|===
| *WP Number* | DM-Ontology
| *Responsibles* | S. Kraines, F. Sanchez, I. Whiteside, P. Parekh
|*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. 
| *Effort (Man-days)*	| 60
| *Service Provider*	| Tasks to be performed by a service provider. Also estimate the % of total effort for this WP.
|===


.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)
|
|===