|
|
### _How to use this template_
|
|
# **SDV Distro Use Cases**
|
|
|
|
|
|
|
|
_Fill out the sections below with succinct information and context._
|
|
In preparation to define the list of use cases and the scope/content of the SDV distro(s) we are starting a breakout discussion group. The expectation is to have the SDV project leaders or someone representing each project to participate in these meetings. The expected outputs of these meetings are:
|
|
|
|
|
|
|
|
_Not all sections may be needed, so delete/rename if unnecessary._
|
|
- Define and publish a set of SDV use-cases highlighting:
|
|
|
|
- The capabilities and features of software provided by SDV projects
|
|
|
|
- Explore potential collaboration and integration of SDV projects
|
|
|
|
- SDV Distro (s)
|
|
|
|
- Define (and build?) a set of SDV distros, including SDV projects, potentially demonstrating the starting points
|
|
|
|
|
|
|
|
_Use sub-headers below for sub sections_
|
|
|
|
|
|
|
|
|
|
_Be sure to back up your decisions using evidence, data, etc.!_
|
|
## Meeting notes
|
|
|
|
|
|
|
|
---
|
|
You can access the meeting notes [here](https://gitlab.eclipse.org/eclipse-wg/sdv-wg/sdv-technical-alignment/sdv-technical-topics/sdv-distro-usecases/-/tree/main/meeting-notes).
|
|
|
|
|
|
|
|
# **Goals**
|
|
|
|
|
|
|
|
|
|
_Describe the goals of the topic/workstream. Use this as an opportunity to explain non-goals too._
|
|
|
|
|
|
|
|
|
|
- locate the projects on the sdv landscape - scope is using it on the landing page to give an idea of the WG scope
|
|
|
|
|
- define use cases to guide the SDV blueprint distro(s)
|
|
|
|
|
|
|
|
|
|
# **People, Projects and Terms**
|
|
# **People, Projects and Terms**
|
|
|
|
|
|
|
|
_Enumerate key people, related projects and topics and define any terms/acronyms readers may come across in the wiki_
|
|
|
|
|
|
|
|
|
|
**Facilitator**:
|
|
**Facilitator**:
|
|
|
|
|
|
|
|
@ndai Naci Dai
|
|
@ndai Naci Dai
|
|
|
|
|
|
|
|
|
**Projects**:
|
|
|
|
All [SDV Projects](https://sdv.eclipse.org/projects/) can participate and contribute to SDV distros and usecase.
|
|
|
|
|
|
|
**Core participants**:
|
|
**Core participants**:
|
|
|
|
|
|
|
|
SDV Project leads
|
|
- @chheis Heissenberger Christian
|
|
|
|
- @mhaller Mike Haller
|
|
|
|
- @daniellueddecke Daniel Lueddecke
|
|
|
|
- @fprezado Filipe Prezado
|
|
|
|
- @florianreimold Florian Reimold
|
|
|
|
- @marioo Mario Alberto Ortegon Cabrera
|
|
|
|
- @nutario Johannes Baumgartl
|
|
|
|
- @gkreyssing Gabriella Kreysising
|
|
|
|
|
|
|
|
|
|
|
|
|
# **Topic/Workstream Overview**
|
|
# **Topic/Workstream Overview**
|
|
|
|
|
|
|
|
_Describe succinctly the topic and the proposal to address it. Catch everyone reading up and include references/links to documents where necessary._
|
|
Details are provided [here](https://gitlab.eclipse.org/eclipse-wg/sdv-wg/sdv-technical-alignment/sdv-technical-topics/sdv-distro-usecases)
|
|
|
|
|
|
|
|
# **Definition of Done Criteria Checklist**
|
|
|
|
|
|
|
|
|
|
_Describe what you propose to deliver - an assessment, a survey, an architecture design, a recommendation, etc._
|
|
|
|
|
|
|
|
|
|
<table>
|
|
|
|
|
<tr>
|
|
|
|
|
<th>Item</th>
|
|
|
|
|
<th>
|
|
|
|
|
|
|
|
|
|
Applicable to project
|
|
|
|
|
|
|
|
|
|
(Y/N)
|
|
|
|
|
</th>
|
|
|
|
|
<th>Notes(optional)</th>
|
|
|
|
|
</tr>
|
|
|
|
|
<tr>
|
|
|
|
|
<td>
|
|
|
|
|
|
|
|
|
|
</td>
|
|
|
|
|
<td>
|
|
|
|
|
|
|
|
|
|
</td>
|
|
|
|
|
<td>
|
|
|
|
|
|
|
|
|
|
</td>
|
|
|
|
|
</tr>
|
|
|
|
|
</table>
|
|
|
|
|
|
|
|
|
|
# **High Level Design**
|
|
|
|
|
|
|
|
|
|
_From a high level, what are the technical solution being assessed/proposed? Why is this approach desired? Architecture diagrams, data flow diagrams, and any other visual materials should be added as necessary._
|
|
|
|
|
|
|
|
|
|
# **Dependencies**
|
|
|
|
|
|
|
|
|
|
_Are there other projects/topics that this depends on?_
|
|
|
|
|
|
|
|
|
|
# **Key Decisions**
|
|
|
|
|
|
|
|
|
|
_Explain any key decisions Provide evidence, support, or data for your choices._
|
|
|
|
|
|
|
|
|
|
# **Impacts of this Design**
|
|
|
|
|
|
|
|
|
|
<span dir="">_Assess the implications of this design. Security or Privacy issues?_</span>
|
|
|
|
|
|
|
|
|
|
# **Dates, Timelines**
|
|
|
|
|
|
|
|
|
|
_What dates are important to this topic/workstream (eg deadlines)?_
|
|
|
|
|
|
|
|
|
|
# **Open Issues, Risks**
|
|
|
|
|
|
|
|
|
|
<span dir="">_Are there any risks, worries worth calling out?_</span>
|
|
|
|
|
|
|
|
|
|
# **References and other docs**
|
|
|
|
|
|
|
|
|
|
<div>
|
|
|
|
|
|
|
|
|
|
_Include other documents, references, or supporting materials here._
|
|
|
|
|
|
|
|
|
|
</div> |
|
|
|
\ No newline at end of file |
|
|
