Page History

...

1. To get consensus around terminology and parts to develop we need to revise this in diagram and text form.  2
2. This page outlines the goal, as well as some challenges to reach pluggable software components, to be used in a shared reference architecture, as well as reuse into various companies own systems, that seem to vary somewhat.
3. Use the CVII Tech Stack Terminology to understand these component names.  Of course, these terms are open to additional input.

A1)  Partial system diagram (primarily representing an in-vehicle, possibly a single ECU, but in some sense the terms are generic.  The technologies are intended to be reusable)

Source file for this diagram is here:  It can be imported into https://app.diagrams.net/ and edited again.

A2)  Vehicle-to-cloud full architecture

The best representation at this time is the COVESA CCS Project Reference Architecture.  NOTE: Be aware that the technologies mentioned therein are not set in stone.  Rather, this page represents a broader view of the variation of software components/protocols/etc. that may apply.

B)  Development Plan for needed technology (definitions, implementations, tools)

...