Page History

...

Useful long discussion on finding common ground. Overran by 30 mins.
Recognition that a workshop soon would be useful to facilitate longer discussion.
Working towards this 'central text' Design Pattern
- Data model and technology agnostic
- Capable of supporting multiple touch points from same arch (robust, flexible etc)
- Capable of multiple data domains sharing same data m/w
- Explain Explains requirements but avoiding avoid deep heavy specification setting
- Vehicle is not a single IT blob. Need to engage with reality of requirements from different domains in outlining use cases and touch points: Hard RT vs needs of Analytics, signal read vs storage for processing.

25th January 2023

Steve: Let's continue discussion of BMW presentation with goal of moving towards a roadmap
Christian is waiting for permission to make presentation public
Christian: Requirements are definitely an interesting collaboration point for us
Felix: Alternative approaches to meet the requirements
Ulf: I've forwarded the presentation within Ford waiting for feedback
Christian: Slide 7
- Important point is the architecture supporting other data models and personal data (arch not be VSS specific)
- VSSo not just for data integration but enabling knowledge transfer
Steve: to my mind we seem to be moving towards a central design pattern from which others and implementations may be spun off
Proposal sketch: Design Pattern: Data Centric Arch including requirements
- Patterns for Touchpoints
- Implementations/PoCs proving such
  - e.g Realm showing VSS sync via middleware
General agreement this makes sense.
Ulf: The implementation section matches what I am working on in Ford
Next steps:
- Start to plan the central Design Pattern

...