Versions Compared

Old Version 2

changes.mady.by.user Stephen Lawrence

Saved on

compared with

New Version 3

changes.mady.by.user Stephen Lawrence

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Central Data Service playground proposal

...

  1. Artifact design methodology (simplified)


Tip
titleFormulating the design problem

Improve (or solve) a <problem>
by designing an <artifact>
that satisfies <requirements>
in order to achieve <goal(s)>

Fundamental components of an artifact design

Panel
borderColor#B85450
titleBGColor#F8CECC
titleProblem

Tip: Specific issue or challenge that requires a solution or improvement.

  • A neutral playground to investigate internals of data services. In the context of data-centric architectures for example.
  • A neutral playground to investigate, illustrate and disseminate combining data services and the Covesa eco-system with other parts of the vehicle and off-board. For example, to demonstrate how VSS data can be used with VISS for newcomers.
  • Repeated use of shared terminology, patterns and tools leads to quicker understanding in discussions, shared costs in development and can lead to quicker outcomes.
    • Jump from 'what is the box' to 'how are we using the box' for example.
Panel
borderColor#6C8EBF
titleBGColor#DAE8FC
titleGoal

Tip: Ultimate objective(s) that a solution aims to achieve, typically formed by the stakeholders' desires. In the context of COVESA, the goal of an artifact is inherit from the general COVESA goals defined as an alliance. In other words, each artifact will represent (minor or major) steps towards an ultimate goal.

...