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

Rename subchapters. Add use cases from concept

parent 8ee1f92a
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1133 188"><defs><style>.cls-1{fill:#b3b3b3;}.cls-1,.cls-5,.cls-7{stroke:#000;}.cls-1,.cls-3,.cls-4,.cls-5,.cls-7{stroke-miterlimit:10;}.cls-2,.cls-3,.cls-4,.cls-7{fill:none;}.cls-3,.cls-4{stroke:#fff;}.cls-3,.cls-4,.cls-7{stroke-width:2px;}.cls-4{stroke-dasharray:12.04 12.04;}.cls-5{fill:#006da2;stroke-width:0.5px;}.cls-6{font-size:18.8px;fill:#fff;}.cls-6,.cls-8{font-family:Hack-Regular, Hack;}.cls-8{font-size:18px;}</style></defs><title>usecase_1_lk</title><g id="road"><rect class="cls-1" x="0.5" y="0.5" width="1132" height="187"/><path class="cls-2" d="M1133,187"/><path class="cls-2" d="M1,187"/><line class="cls-3" x1="1" y1="94" x2="7" y2="94"/><line class="cls-4" x1="19.04" y1="94" x2="1120.98" y2="94"/><line class="cls-3" x1="1127" y1="94" x2="1133" y2="94"/></g><g id="Layer_1" data-name="Layer 1"><path class="cls-2" d="M1026,352.52"/><path class="cls-2" d="M913.41,39.4"/><path id="path5362" class="cls-5" d="M955.51,71c1.31.06,2.18-1.2.55-4.11,12.87.23,25-.06,38.75.29,5.45.13,9.91-.53,16.39-.41,4.9-.25,12.94-.67,16.29-4.17,4.7-4.91,6.12-13.73,6.15-21.37h0v-.79h0c0-7.64-1.45-16.46-6.15-21.37-3.35-3.5-11.41-3.68-16.29-4.17-3.36-.34-10.94-.55-16.39-.41-13.78.35-25.88.06-38.75.29,1.63-2.92.76-4.18-.55-4.11a3.91,3.91,0,0,0-3.22,3.85c-4.4.1-7.42.26-12.73.27-9,0-12.58.93-17.25,5.24-3.79,3.5-8.11,8.5-9.3,13.59.06,3.22,0,4-.09,7.07h0a.66.66,0,0,1,0,.14.76.76,0,0,1,0,.15h0c.11,3.1.15,3.84.09,7.07,1.19,5.09,5.51,10.08,9.3,13.58,4.67,4.31,8.24,5.22,17.25,5.24,5.31,0,8.33.18,12.73.28A3.92,3.92,0,0,0,955.51,71Zm17.71-8.53-23.84-.61s4.09-1.23,6.15-1.82,4.06-1.3,6.15-1.75a23.19,23.19,0,0,1,2.5-.38c1.89-.2,3.79-.35,5.7-.38,6.61-.08,13.21.39,19.81.84,3.55.24,7.28.42,10.63,1a.82.82,0,0,1,.61.53c.2.67-.54,2-.54,2Zm-26.93-1.2a1.22,1.22,0,0,1-.8-.29,10.11,10.11,0,0,1-4.72-4,25.89,25.89,0,0,1-3.83-9.59,29.59,29.59,0,0,1-.62-6.56,29.65,29.65,0,0,1,.62-6.56,25.84,25.84,0,0,1,3.83-9.58,10.08,10.08,0,0,1,4.72-4,1.43,1.43,0,0,1,1.62-.07l13.12,4.28a25.61,25.61,0,0,0-2,6.46,47.78,47.78,0,0,0,0,19,25.61,25.61,0,0,0,2,6.46l-13.12,4.28A2,2,0,0,1,946.29,61.27Zm55.11-4.63h-.85c-6,0-3.91-.09-9.91-.19a76.92,76.92,0,0,0,1-10.39c0-1.22.08-3,.11-4.56h0c0-.17,0-.46,0-.66s0-.48,0-.66h0c0-1.53-.06-3.34-.11-4.56a77.07,77.07,0,0,0-1-10.39c6-.1,3.91-.18,9.91-.18a4.88,4.88,0,0,1,3.26.68,11.7,11.7,0,0,1,5,7.09,29.47,29.47,0,0,1,.92,8,29.47,29.47,0,0,1-.92,8,11.75,11.75,0,0,1-5,7.1,4,4,0,0,1-2.41.69Zm-29-32.5h-2.47a57,57,0,0,1-5.7-.38,23.19,23.19,0,0,1-2.5-.38c-2.09-.45-4.11-1.15-6.15-1.75s-6.15-1.82-6.15-1.82l23.84-.6,27.17.53s.74,1.37.54,2.05a.86.86,0,0,1-.61.53c-3.35.57-7.08.75-10.63,1-5.77.38-11.55.79-17.34.84Z"/><text class="cls-6" transform="translate(958.58 47.64)">ego</text><line class="cls-7" x1="746.07" y1="41" x2="913" y2="41"/><path d="M734,41c5.68,2.11,12.73,5.7,17.09,9.51L747.65,41l3.44-9.51C746.73,35.3,739.68,38.89,734,41Z"/><line class="cls-7" x1="913" y1="41" x2="913" y2="73.93"/><path d="M913,86c-2.11-5.68-5.7-12.73-9.51-17.09L913,72.35l9.51-3.44C918.7,73.27,915.11,80.32,913,86Z"/><text class="cls-8" transform="translate(813.31 81.33)">Distance</text><text class="cls-8" transform="translate(803.33 32.75)">Speed</text></g></svg>
\ No newline at end of file
......@@ -16,8 +16,8 @@ include::subchapters/1-5_relations_to_other_standards_projects_or_organizations.
include::subchapters/2_technical-content.adoc[]
== Project Resources
include::subchapters/3-1_required_resources.adoc[]
include::subchapters/3-2_committed_resources.adoc[]
include::subchapters/3-1_work_packages.adoc[]
include::subchapters/3-2_company_commitments.adoc[]
include::subchapters/3-3_resource_summary.adoc[]
== Project Plan
......
This diff is collapsed.
=== Requirements
=== User Stories
[[a-share]]
==== A) SHARE
1. As an AV/ADAS developer company, I can share with other companies the scenarios I built to test my technology.
2. As an AV/ADAS developer company, I can search, review and reuse scenarios built by other companies.
3. As a test engineer working for an AV/ADAS development company, I can build and run tests as similarly as possible to tests other developers at other companies are running.
4. As a test engineer, I can build and run tests as similarly as possible on different execution platforms.
5. As a researcher developing new technology, I can reutilize industry and open source scenarios to advance my research.
[[b-certify-analyse]]
==== B) CERTIFY & ANALYSE
1. As an auditor/regulator, I can understand how AV/ADAS developers are testing their products.
2. As an auditor/regulator, I can compare the outcome of different execution platforms when they have the same OpenSCENARIO input.
3. As a safety consultant, I can recommend specific scenarios and related conditions (parameters) to my clients to test their products.
4. As a member of the public, I can learn more details about how AV/ADAS products are tested by AV/ADAS developers.
5. As government agency, I can understand what parts of the Operational Domain are verified by an AV/ADAS developer through each scenario.
[[c-develop]]
==== C) DEVELOP
1. As a tool developer, I can reutilize constructs, artifacts and libraries to create tools compatible with other tool vendors in industry.
2. As a service provider, I can integrate tools from multiple tool vendors to provide an integrated solution to test AV/ADAS scenarios.
3. As a system engineer working for an AV/ADAS developer company, I can fully trace which hardware and software in the AV/ADAS stack is verified by which tests.
4. As a software developer, I can process scenario information from different software/hardware releases and produce comparison charts to provide trend and gap analysis.
5. As an existing tool provider or consumer, I can migrate information from previous versions of OpenSCENARIO into OpenSCENARIO 2.0.
6. As a system engineer working for an AV/ADAS developer, I can decompose high level use cases in a standardised way.
[[d-create]]
==== D) CREATE
1. As a content developer, I can use OpenSCENARIO 2.0 to create test scenarios that I can supply to my customers who use a OpenSCENARIO 2.0 compliant toolchain.
2. As a test engineer, I can transform abstract test descriptions into OpenSCENARIO 2.0 (e.g. NCAP tests, UNECE regulations, any requirement list, …).
3. As a development project lead, I can write scenarios on an abstract level to discuss the functional behavior with the stakeholders.
4. As a development project lead, I can create scenarios on an abstract level to document the functional behavior for legal reasons.
5. As a stakeholder, I can create natural language scenarios without having any knowledge about technical details.
[[e-sotif-based-risk-consideration]]
==== E) SOTIF-BASED RISK CONSIDERATION
1. As a SOTIF safety engineer and/or V&V engineer, AV developer, scenario creator, I can use OpenSCENARIO 2.0 to discover scenarios that are going to uncover safety hazards. This refer to SOTIF and safety hazards that can be present even if the system is functioning as designed, without a malfunction.
2. As a SOTIF safety engineer and/or V&V engineer, AV developer, scenario creator, I can use OpenSCENARIO 2.0 to create scenarios that are going to produce emergent behavior of the DUT to discover unknown unknows. OpenSCENARIO 2.0 shall enable to demonstrate that minimum residual risk is attained by the DUT. This is because SOTIF focuses on ensuring the absence of unreasonable risk due to hazards resulting from insufficiencies in the intended functionality or from reasonably foreseeable misuse.
[[f-driving-mission-based-scenarios]]
==== F) DRIVING MISSION-BASED SCENARIOS
1. As an end-to-end V&V engineer, I can use OpenSCENARIO 2.0 to enable specification of a driving mission through inclusion of multiple maneuvers in a sequence or in parallel for both DUT and any other traffic agents.
2. As an end-to-end V&V engineer, I can use OpenSCENARIO 2.0 to enable accomplishing a select driving mission with an indication of whether the mission has been accomplished, what are the mission KPIs and how they are computed, and whether the unambiguous goals of the mission have been attained.
[[g-traffic-model-inclusion]]
==== G) TRAFFIC MODEL INCLUSION
1. As a traffic model developer, an ADS developer, or end-to-end V&V engineer, I can use OpenSCENARIO 2.0 to enable inclusion of multiple traffic models and AI-based traffic agents in the scenarios and evaluators. Also, OpenSCENARIO 2.0 shall enable inclusion of mechanisms to extract scenarios from the traffic models.
2. As a test engineer, I can transform from high level scenario description to low level scenario descriptions and vice versa.
[[h-execute]]
==== H) EXECUTE
1. As a test engineer, I can execute different OpenSCENARIO 2.0 files in an automated way with my OpenSCENARIO 2.0 compliant toolchain; no file modifications are needed.
2. As a test engineer, I can execute the same OpenSCENARIO 2.0 files on different OpenSCENARIO 2.0 compliant toolchains.
3. As a test engineer, I can convert abstract scenarios into tests.
[[i-describe-observations]]
==== I) DESCRIBE OBSERVATIONS
1. A simulation tool can describe randomly executed simulation runs. If the Simulation was run with stochastic metrics, the user wants to have the concrete description of what has happend in OSC2.0 Format.
2. A traffic observer can describe what occured in real world with OSC2.0
3. A test engineer on a test track can describe with OSC2.0 what specific scenario he has observed on a test track. In such a way tolerances and deviations between test description and test execution will become obvious.
=== Requirements
OpenSCENARIO 2.0 should address the basic requirements and features stated in the concept project proposal document. These are repeated here for clarity and their detailed description can be found in the concept project proposal document for OSC 2.0.
......
=== Required
=== Work Packages
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"]
......@@ -192,20 +190,3 @@ This WP will address the necessary ways of packaging functionality into librarie
| 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)
|
|===
=== Committed
=== Company Commitments
Member companies contribute resources for the project as per the following table.
// Company details to be added by individual representatives
......
=== Summary
=== Effort Summary
.Required work effort should be less than or equal to committed work effort + service provider contracts
[cols="2,3"]
......@@ -8,3 +8,21 @@
| *Contracted to Service Providers* |
| *Required Work Effort* |
|===
==== 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)
|
|===
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