We use cookies on this site to enhance your user experience. By using this site, you are giving your consent for us to set cookies.


You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

This is a preliminary page intended to trial using the Artifact design methodology (simplified) to guide and describe the project. At this stage it is a brainstorming WIP

References:

  1. Central Data Service playground proposal

Fundamental components of an artifact design

Problem

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

Goal

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.

Requirements

Tip: Criteria and specifications that the artifact must meet to address the identified problem and achieve the set goals. Typically presented as functional and non-functional.

  • Functional: Specific functions, tasks, or actions that the designed artifact must perform to proof utility. 
  • Non-functional: Specific qualities or characteristics that the artifact must have. They represent the constraints under which the design must operate.
Artifact

Tip: Represents the tangible outcome of a design that aims to solve the problem and fulfils the specified requirements and goals.

  • No labels

Privacy Policy | Cookie Policy