JOIN/SIGN UP
Already a Member? |
GET INVOLVED
Understanding and Engaging in COVESA Expert Groups & Projects |
COLLABORATIVE PROJECTS
HISTORICAL
SDV Telemetry Project - On Hold |
Info |
---|
This is a preliminary page intended to trial using the Artifact design methodology (simplified) to guide and describe the project. At this stage it is a brainstorming WIP |
Tip | ||
---|---|---|
| ||
Improve (or solve) a <problem> |
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
Tip: Specific issue or challenge that requires a solution or improvement.
|
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
Tip: Ultimate objective(s) that a solution aims to achieve, typically formed by the stakeholders' desires. In the context of COVESA, the goal of an artifact is inherit from the general COVESA goals defined as an alliance. In other words, each artifact will represent (minor or major) steps towards an ultimate goal.
|
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
Tip: Criteria and specifications that the artifact must meet to address the identified problem and achieve the set goals. Typically presented as functional and non-functional.
Functional:
Non-functional:
|
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
Tip: Represents the tangible outcome of a design that aims to solve the problem and fulfils the specified requirements and goals. |
GPT output with the proposal as input:
Design Elements:
1. Problem:
The current lack of a neutral playground for investigating data services and disseminating knowledge within the Covesa ecosystem is causing limitations and hindering development and collaboration.
2. Goal:
The goal is to create a Central Data Service playground that allows for investigation, illustration, and dissemination of data services and their integration with other components. The aim is to accelerate newcomers' understanding of Covesa technology and facilitate collaboration among internal groups.
3. Requirements:
- Functional Requirement: The playground should provide APIs for accessing the data, such as VISS or GraphQL.
- Non-Functional Requirements: The playground should have good performance, usability, security, scalability, and reliability.
4. Artifact Type:
The project is designing a Central Data Service playground, which combines VISS Data Protocol Server with VSS Data Store to create a basic building block. The playground will include supporting documentation, patterns
diagrams, and cookbooks to facilitate understanding and usage.