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.

Current situation (summary)

Current situation (description)

Proposal overview (summary)

• A foundational concept is that there is a need for an approach to architecture that describes requirements and components in abstract logical terms.
  • This encourages collaboration by avoiding product comparisons and system architecture.
  • Provides a shared vocabulary for discussion and illustration.
  • Provides flexibility in how such components are arranged.
  • Should be the first approach to describing scenarios in Covesa. PoCs for example would first describe the logical design before describing specific technologies used.

Proposal overview (description)

Patterns / building blocks:

• Data Server, Data Store
  • Focus on the makeup of these components and the connections between them. A building block in wider arch.
  • Variants:
    • Mobile App, in-vehicle app
      
      • Store likely close to app process.
    • Domain Data Service
      • Possibly data store centric, e.g. DB, with remote clients
• Integration
  • Variants: data flow bi/uni-directional, conflict resolution, latency, volume, frequency
• Scenarios
  • Snapshots focusing on specific areas: Vehicle API, Service + gateway (as in Adnan example above), etc.
  • Data EG Deployment scenarios: IVI, Smart device, Car2Cloud, Cloud2Cloud,
  • Data EG Touchpoints