JOIN/SIGN UP
Already a Member? |
GET INVOLVED
Understanding and Engaging in COVESA Expert Groups & Projects |
COLLABORATIVE PROJECTS
HISTORICAL
SDV Telemetry Project |
We use cookies on this site to enhance your user experience. By using this site, you are giving your consent for us to set cookies. |
Purpose
The author (Stephen Lawrence) intends for this proposal to facilitate the Data Architecture team in particular and the wider Data Expert Group to find a shared view on documenting Data Patterns and Data Architecture. Contribution is therefore encouraged by commenting inline, contacting the author or in the Data Architecture calls.
This page describes a proposal to move towards joint work on documenting Data Patterns and Architecture after the Spring 2023 AMM.
Following a summary of where we stand, a proposal is made for a possible way forward. The author does not intend the proposal to be a fully formed work plan, but a skeleton roadmap on which the Data Architecture group and the Data Expert Group can iterate on to form one. An important principal is open discussion on what issues need to be tackled down, what is needed to form common understanding and sense of purpose.
Covesa has a range of source material from which to use.
This includes historical work from projects such as Genivi Cloud & Connected Services (CCS) project which investigated the requirements of open data capture in-vehicle and its connection to back-end systems in the cloud and resulted in a high level architecture concept.
CCS was followed by the Common Vehicle Interface Initiative (CVII) Tech Stack project which investigated the software required to transfer and process the standard VSS data model. For that a mutual understanding of terms and common components were required. The latter resulted in the in-vehicle architecture diagram on the right, which is intended to show the likely in-vehicle components and how they interact, rather than specify a specific monolithic architecture. A set of related terminology was also defined.
This evolved into contemporary work in the Covesa Data Expert Group including the Data Architecture pillar of the Group. For example the results from the first workshop included a high level scope to focus on zonal ECUs and above for the functional integration and data architecture. In addition high level deployment scenarios were sketched for in focus use cases including IVI, Smart device, Car2Cloud and Cloud2Cloud.
These sketches now need further work to build out the details. For example Smart Device will involve SmartDevice2Vehicle and SmartDevice2Cloud.
There are also various presentations from meetings and the All Member Meeting (AMM) conferences. For example this input on Data Centric Architectures.
Finally there is individual work intended as contribution to the group work such as the authors work in his vss-otaku project, which includes discussion of combining VSS data stores and data servers.
As the number of adopters of Covesa technology, including VSS, has risen greatly we have seen increasing demand for descriptions of what it is intended for and how to use it. This helps both newcomers understand the technology and supports discussion within the community. At the same time the massive increase in the size of in-vehicle software and the introduction of technologies from outside of automotive has resulted in a need to quickly build understanding between people from a more diverse group of areas.
To be quickly productive this needs a shared vocabulary and understanding of common design components and patterns described in abstract terms. A solution is discussed in more detail in the proposal. To move forward on creating that within the community requires a shared view of the goals. This proposal is intended to help facilitate that.
Patterns / building blocks:
The VSS documentation website has been useful for a number of reasons. It brings the documentation together in one place, whilst supporting navigation and rich enough formatting. Being able to refer to a single URL within, from which other content can be found is useful for both business and technical discussions. It is therefore proposed we do the same for the design documentation that is the topic of this proposal.
For ease of implementation it is suggested we use the same publishing technology used for the VSS documentation, namely Hugo with a similar format template. The requirements to build a static website to test documentation locally are straight forward and the automated build and deployment of Hugo websites is already supported within the Covesa CI. A useful attribute of Hugo is the split between content and publishing. The content can be defined in markdown for example and then consumed by the Hugo framework. This gives flexibility in both choosing tooling for the content creation step and possibly moving to a different website framework in the future if required, i.e. there is little Hugo lock-in.
Document creation and publishing outline: