B.12 Workflows for system engineers
The following workflows concentrate on typical jobs for system engineers.
B.12.1 Workflow list
-
Section B.12.2
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.
B.12.2 Tracing back verification
B.12.2.1 Workflow short description
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.
B.12.2.2 Workflow detailed description
OpenSCENARIO 2.0 is agnostic to the execution platform including the used hardware and software. This means that an abstract scenario should not be hardcoded for a specific implementation nature or version.
At the same time, an OpenSCENARIO 2.0 tool chain allows the tracing between the execution log result and the abstract executed scenario. The actions level of abstraction can be determined by the user.
B.12.2.4 Steps for tracing back verification
-
Choose the level of abstraction of your scenario
The scenario can be composed of low-level or high-level actions. Typically scenarios are high-level vehicle level use-cases, but it is up to the user to create a more refined scenario. -
Create coverage attributes to identify which hardware or software system is executed in each scenario. Note that each scenario exercises multiple hardware and software units. You can set goals for each unit capturing the depth.
-
Execute the scenarios and observe the coverage data.
-
Review the coverage result to understand if the goals for the HW and SW components are met.
The result of running this use case is a clear understanding of which hardware and software components were executed, in which challenges they ran and how well they did.