Skip to content

Define the ODD definition format based on the scenario generation process needs #31

Open

Description

@diegoyabuki

Checklist

  • I've read the contribution guidelines.
  • I've searched other issues and no duplicate issues were found.
  • I've agreed with the maintainers that I can plan this task.

Description

Once the scenario generation process is defined, it must be ensured that the ODD definition format adopted can provide all information that is required on later activities in the process.

Purpose

If the ODD definition lacks the fields required to fully specify the test scenarios or use cases, these activities cannot be performed as described in the formal process definition. In this step, we ensure that the ODD format decision takes this aspect into consideration.

Possible approaches

  • Based on the formalized process, look at the activities that require the ODD definition as an input. List all features and fields that are required to perform each activity.
  • If this step depends on the formal definition of later activities, prioritize those first, before continuing with this activity.
  • Select an ODD definition format that provides all required information, or extend an existing one so that the process activity needs are met.

Definition of done

  • The list of fields/features required by use case creation and test scenario creation activities is generated.
  • An initial investigation of the industry standards related to ODD definition is performed.
  • The ODD format to be adopted is decided based on the process activity needs.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions