Commit 5fe17867 authored by Bock, Florian (I/EF-A3)'s avatar Bock, Florian (I/EF-A3)
Browse files

updated usage and pragmatics introduction and scenario creation/workflow section

parent 5378d4da
......@@ -61,3 +61,57 @@ WP DM-Ontology - Develop ontology to establish relations between entities
* Iain Whiteside (FiveAI) can provide a presentation on practical usage of their ontology
* UK has developed a standard (or a PAS really) called 1883 for a driving ontology (Siddhartha could help here)
* possible input as well from Steven and Florian Bock (Audi)
==== Usage and Pragmatics
Responsible: Florian Bock
This section includes different topics about the usage of scenarios and the corresponding workflows.
The content of a scenario can be modified in different ways: Data can be altered, data can be added or removed. The latter two are important regarding the different abstraction levels. Whereas functional scenarios are quite abstract and therefore do not included very much details about the objects and subjects, concrete scenarios that can be used for simulation naturally have to include a tremendous amount of details to allow that. To get from one abstraction level to the other, two ways are common: Concretization (adding more details) and abstraction (removing details).
One important point, that has to be discussed within the project is the linkage or respectively the interfacing to previous OpenSCENARIO version (0.x and 1.x). At least a migration plan to convert artifacts from previous version should be available to amplify the usage and prominence of OSC 2.0.
To create, use and maintain scenarios, a corresponding process or workflow has to be defined in order to guide the user. This workflow should cover all use cases defined in the use case section.
This is also true for a proper testing workflow, that should describe the interaction between requirements, scenarios and test cases within the development.
===== Abstraction, Concretization of Scenarios
Responsible: ?
====== Scenario summary to functional Scenario (i.e. Rules of Abstraction)
Responsible: ?
====== Functional Scenario to concrete scenario (i.e. Rules of Concretization)
Responsible: ?
====== Interfacing with concrete scenarios from OSC 1.x
Responsible: Sandeep P.
===== Creation of Scenarios & Scenario Workflow (from creation to maintenance of scenarios)
Responsible: Florian Bock
As already stated, scenarios are used throughout the development process with different levels of detail. The corresponding use cases (at least the ones that the concept project group could think of) were mentioned in Section X. Due to the fact, that each use case partially represents different people from different groups with different goals, constraints and circumstances, their intention of the usage of scenarios and their way of using them sometimes may, but often will divert.
The goal of defining one single workflow for the creation and usage of scenarios seems ambitious and possibly unachievable. To cover all defined use cases, this would result in a very complex process, that would be hardly usable. Nevertheless, the goal should be to cover as much use cases as possible. To do so, an iterative approach for the application within the OSC 2.0 standardization project seems reasonable.
This implies several steps:
- A review of the already defined use cases should be done to identify missing use cases, improve the description and the differentiation among themselves and finalize the list
- Representatives for each use case should be determined to deliver insight in the background and the underlying assumptions
- Each representative should write down his or her workflow/definition in a similar way (e.g., by using the same type of diagram or template)
- Each worfklow should be reviewed by at least one reviewer to find flaws, unclear parts and missing elements
- All workflows should be checked for duplicates (either in whole or in parts)
- All workflows should be split into atomic parts that can be separated
- A generic workflow should be created/designed based on the separated atomic parts
- Each covered use case should be documented within the workflow
- Uncovered use cases should be documented with ideas, how to proceed with them
The created workflow should include all lifetime phases for a scenario, from prerequesites and ideas, over the creation and modification, until the maintenance and documentation phases. This enables the user to track the scenario in its current lifetime phase and to know how to proceed.
As an illustration of the concept, e.g., the creation of a scenario can be done by using different methods, from manual writing, over tool-assisted (either textual or graphical) creation to extraction or generation out of a predefined data pool. All those ways should be covered within the defined process.
===== Scenario based testing workflow
Responsible: Sharon Rosenberg
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