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:
    • Rather than possibly confuse by trying to explain different configurations in a single document instead outline common variant patterns separately
    • 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
  • Focus likely more on viewpoints showing data flow over assemblies of components, either at high level (e.g. Data EG Deployment Scenario diagrams) or more of a focused snapshot of part of it (e.g. flow between Service, Vehicle API, Gateway and Autosar)
  • Snapshots focusing on specific areas:
    • Vehicle API, Service + gateway and RT/ASIL southbound
    • Knowledge pyramid
      • Focus on connection between layers of pyramid. Specifically the flow of information up and down the knowledge pyramid. Related is connection between pyramids.
  • Data EG Deployment scenarios:
    • From Workshop Miro and as shown in Porto AMM
    • IVI, Smart device,
    • Car2Cloud,
    • Cloud2Cloud,
  • Data EG Touchpoints:
    • The famous hedgehog touchpoints

...