In this example, the methodology is used in two different levels:

Project design components
- Provide a high-level view of the project itself.
- The description here is rather general and shows the alignment of the project with the COVESA's goals.
Artifact(s) design components
- Provide a detailed view of the main artifacts that belong to the project.
- The description here is mostly technical.

Project design components (High-level)

Problem

Inconsistent data representation of vehicle properties across the automotive industry.

Causes
- Different vehicular systems use disparate data models for concepts of common interest.
  - Examples of vehicular systems: applications, databases, streaming platforms, , etc.
  - Examples of data models (or elements of): terms, hierarchies, meaning, language, datatypes, etc.
Effects
- Interoperability issues.
- Repetition in data engineering processes.
- Increased complexity and maintenance costs.
- Waste of time and resources.
- Slow innovation.

Goal (This should come from COVESA's goals)

To lead the global standardisation of vehicle data, fostering innovation and collaboration in the automotive industry.

Artifact(s)

Requirements (current)

Feature	Functional	Non-funcional	Scope
	A common controlled vocabulary for referring to vehicle properties		Current
			Planned
			Desired (but not planned)

Artifact(s) design components

Requirements (current)

Feature	Functional	Non-funcional	Scope
	A common controlled vocabulary for referring to vehicle properties		Current
			Planned
			Desired (but not planned)

Requirements (current)