...
Proposal overview (summary)
- A foundational concept is that there is a need for an approach to architecture that describes requirements and components in abstract logical terms.
- This encourages collaboration by avoiding product comparisons and system architecture.
- Provides a shared vocabulary for discussion and illustration.
- Provides flexibility in how such components are arranged.
- Should be the first approach to describing scenarios in Covesa. PoCs for example would first describe the logical design before describing specific technologies used.
Proposal overview (description)
Patterns / building blocks:
- 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