JOIN/SIGN UP
Already a Member? |
GET INVOLVED
Understanding and Engaging in COVESA Expert Groups & Projects |
COLLABORATIVE PROJECTS
HISTORICAL
SDV Telemetry Project |
Status colour Yellow title Draft Status title V.0.12
title | * Disclaimer |
---|
Problem: Specific issue or challenge that requires a solution or improvement.
Goal(s): Ultimate objective(s) that a solution aims to achieve, typically formed by the stakeholders' desires.
Requirements: 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.
Artifact: Represents the tangible outcome of a design that aims to solve the problem and fulfils the specified requirements and goals.
The fundamental components of an artifact design form together a clear and well-scoped summary. Following the template suggested in [3], each workflow at COVESA must target only artefacts with a complete set of design components as follows:
Tip | ||
---|---|---|
| ||
Improve (or solve) a <problem> |
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
Specific issue or challenge that requires a solution or improvement. |
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
Ultimate objective(s) that a solution aims to achieve, typically formed by the stakeholders' desires. |
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
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.
|
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
Represents the tangible outcome of a design that aims to solve the problem and fulfils the specified requirements and goals. |
The fundamental components of an artifact design form together a clear and well-scoped summary. Following the template suggested in [3], each workflow at COVESA must target only artefacts with a complete set of design components as follows:
Tip | ||
---|---|---|
| ||
Improve (or solve) a <problem> |
Bear in mind that specific details of the fundamental components might be unclear at the starting phase of a project. Nevertheless, as the work advances, they must be updated according to the development and aligned with the official releases of an artifact.
Status | ||||||
---|---|---|---|---|---|---|
|
Here comes a Figure that shows the steps to follow.
Here comes an specific example of an existing project in COVESA and its associated artefacts.
Status | ||||
---|---|---|---|---|
|
[1]
A. Hevner, S. March, J. Park, and S. Ram, “Design science in information systems research,” MIS Quarterly, vol. 28, no. 1, pp. 75–105, 2004.
[2]
S. Gregor and A. Hevner, “Positioning and presenting design science research for maximum impact,” MIS quarterly, pp. 337–355, 2013.
[3]
R. J. Wieringa, Design Science Methodology for Information Systems and Software Engineering. Berlin, Heidelberg: Springer Berlin Heidelberg, 2014. doi: 10.1007/978-3-662-43839-8.
[4]
P. Offermann, S. Blom, M. Schönherr, and U. Bub, “Artifact Types in Information Systems Design Science – A Literature Review,”
in Global Perspectives on Design Science Research, vol. 6105, R. Winter, J. L. Zhao, and S. Aier, Eds., in Lecture Notes in Computer Science, vol. 6105. , Berlin, Heidelberg: Springer Berlin Heidelberg, 2010, pp. 77–92. doi: 10.1007/978-3-642-13335-0_6.