Page History

...

• 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

Document creation and publishing:

• New doc site using same publishing tech already used within Covesa, e.g. VSS doc
  
  • Suggested Dev method for
    
    • Text generation/collaboration on Confluence = ease of editing, simultaneous edit, inline comments
    • Diagrams in open flexible format. Suggest drawio.
    • Once topic document complete convert page to .md and regenerate site
    • Existing CI pattern can automate generation and publishing.
  • Purpose of site
    • In abstract logical language, i.e. typically product agnostic, describe use of VSS
    • Hierarchical classification of above topic types on left hand side, e.g. Patterns, Architectures, Touchpoints
    • Topic document on right