Here are notes regarding potential deliverables from Fall AMM wrap-up meeting:

Best Practices Pillar

Security

• Review - input
• Data classification
• Send out best practices presentation
• logging

Governance Models for VSS and DEG

Version Control - best practices for data models (e.g. VSS)

COVESA - Scope 

Use Github for DEG issues?

Way of working - GitHub wiki or confluence?

Auto meets world presentation - presentation to highlight the challenges of automotive that other industries may not face.

Serialization Guidelines

Modeling and Ontology Pillar

EV Charging - need to get serious and more formal about this

VSS 

• Documentatiin and Use Cases
• API definitions
• Test cases
• Overlays - more formal
• Compex Types - need a decision/path forward
• AUTOSAR - how will VSS be exposed via AUTOSAR plugin
  • Will it be tightly tied to someip
  • Too heavy
  • No need to develop full AUTOSAR solution in the car
  • DDS 
  • Meeting tomrrow

Sensoris for object detection - leverage for inspiration/starting point if possible

Architecture

Target Architectures - It is very clear everyone would like to understand the target/bounding architectures for context when discussing issues.

Reference diagrams - where does everything sit - same as above

Cloud Architecture - is needed.  We always show in vehicle but no cloud?

Show single feature all the way through - It is very clear everyone would like to understand the target/bounding architectures for context when discussing issues.

Deployment

Security design patterns

BMW - and Mongo - conversations merged Arch and VSS

Guidance - what type? databases in vehicle?

Use case families - e.g how to synch data

Deployment of VSS in context - what is the context - touchpoint

Design patterns

Interfaces

VSS is often seen as an interface when in fact it is a data model.  We need clarity for the community here.

VSS vs interface

What interfaces do we want to cover?

Fat APIs?

VISS and out of the box interfaces