Resources |
◎ COVESA Events |
Join/Sign Up |
◎ Join COVESA |
Example: VSS fundamental design components
In this example, the methodology is used in two different levels:
Project
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.
Artifacts
Provide a detailed view of the main artifacts that belong to the project.
The description here is mostly technical.
Project
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
To lead the global standardisation of vehicle data, fostering innovation and collaboration in the automotive industry.
The project's goal is inherit from the goals of the whole organization.
Artifacts
VSS Data model
VSS Tools
Artifact - VSS Data model
Problem
Inconsistent data representation of vehicle properties across the automotive industry.
Goal
To unify descriptions, meaning, and relevant metadata for vehicle properties.
Artifact
VSS Data model
Requirements
Feature | Functional | Non-funcional | Scope |
|---|---|---|---|
| A common controlled vocabulary for referring to vehicle properties |
|
|
|
|
|
|
|
|
|
|
Artifact - VSS Tools
Problem
The data specification alone is not machine readable.
Goal
To enable machines to interpret and use the specification in real systems.
Artifact
VSS Tools
Requirements
Feature | Functional | Non-funcional | Scope |
|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|