Page History

...

Historical note: the minutes for the previous project, the CVII Tech Stack, can be found here: CVII Technology Stack meeting notes

7th June 2023

• Needs
  • Top down
    • Shared high level views
      • Terminology
      • Common patterns
      • Building blocks both descriptive and PoC (trial, playgrounds etc.)
      • User stories and deployment scenarios illustrating the combination of these
        • VSS+methods / services / vehicle API
          • Scenario 1: HVAC service <=> gateway (vehicle API - VSS Data model) | autosar / RT / RTOS (southbound low level parts)
            • / set temp
      • Work
        • Bottom up
          • Patterns / blocks
            • Data Server, Data Store
              • Variants: Mobile App, in-vehicle app, Domain Data Service
            • Integration
              • Variants: flow bi/uni, conflict resolution, latency, volume, frequency
            • Scenarios
              • Data EG Deployment scenarios: IVI, Smart device, Car2Cloud, Cloud2Cloud,
              • Touchpoints

31st May 2023          

• Data Architecture Terminology.
  • Steve presented updated terminology that has a first pass approach to adding Data Store sync
    • Felix suggested moving Sync into its own component description. That matches one of the options previously discussed. Steve happy to try it that way also.
  • Wide ranging discussion of the needs and approaches to getting at a flexible, reusable set of high level component diagrams/descriptions
  • Felix diagrammed some options re the Data Server and Data Store variants. Discussion included differences between a 'fat' Data Store that might be connected to a Data Gateway, versus an in-vehicle application (e.g. following MVC design pattern) that has an API and local 'thin' Data Store dedicated to it.

...