Powered by OpenAIRE graph
Found an issue? Give us feedback
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/ ZENODOarrow_drop_down
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/
ZENODO
Other literature type . 2025
License: CC BY
Data sources: ZENODO
ZENODO
Project deliverable . 2025
License: CC BY
Data sources: Datacite
ZENODO
Project deliverable . 2025
License: CC BY
Data sources: Datacite
versions View all 2 versions
addClaim

AD4GD D1.2 Multi-Actor and Knowledge Centres Co-Design and Requirements Definition Report (Final)

Authors: Koopmann, Marisa; Berwanger, Kristian; Mebus, Lina;

AD4GD D1.2 Multi-Actor and Knowledge Centres Co-Design and Requirements Definition Report (Final)

Abstract

This deliverable presents the outcomes of Task T1.1, Multi-Actor and Knowledge Centres Co-Design and Requirements Definition, within Work Package 1 (WP1) of the All Data for Green Deal (AD4GD) project. It builds upon the foundations laid in Deliverable 1.1 and documents the iterative process of refining user requirements for the Green Deal Data Space (GDDS). A central element of this process was the Co-Design Workshop, held in September 2023, which brought together project partners and stakeholders to collaboratively define user needs for two pilot applications—Lake Splashboard and BioConnect—as well as the broader General User Interface of the GDDS. Through participatory design methods, user journeys were created, initial prototypes were developed and user stories extracted. These prototypes were subsequently evaluated by potential end users, leading to the identification of additional user needs and refinement of existing user stories. As a result of this iterative process, a total of 115 user requirements were formulated, 30 requirements for Pilot 1, 49 requirements for Pilot 2 and 34 requirements for the General User Interface of the GDDS. This deliverable concludes the requirements definition phase, providing structured foundation for the implementation of the GDDS tools. The methodology applied, based on Human-Centered Design (HCD) principles, ensures that user needs remain central throughout the development process.

Keywords

User stories, Human-Centred Design, User requirements, Data Space, Stakeholder Engagement

  • BIP!
    Impact byBIP!
    selected citations
    These citations are derived from selected sources.
    This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
    0
    popularity
    This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network.
    Average
    influence
    This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
    Average
    impulse
    This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network.
    Average
Powered by OpenAIRE graph
Found an issue? Give us feedback
selected citations
These citations are derived from selected sources.
This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
BIP!Citations provided by BIP!
popularity
This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network.
BIP!Popularity provided by BIP!
influence
This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
BIP!Influence provided by BIP!
impulse
This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network.
BIP!Impulse provided by BIP!
0
Average
Average
Average
Funded by