[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-seo-242556-105":3,"detail-sidebar-cat-1-en-105":81,"doc-detail-242556-en":127},{"code":4,"msg":5,"data":6},0,"ok",{"site_id":7,"language":8,"slug":9,"title":10,"keywords":11,"description":12,"schema_data":13,"social_meta":74,"head_meta":76,"extra_data":78,"updated_unix":80},105,"en","soilwise-d11-usage-scenarios-requirements-v1-project-deliverable-final","SoilWise - D1.1 Usage Scenarios, Requirements - v1 - project deliverable final","","The purpose of this deliverable is to outline the methodology for co-creation and the definition of user needs, including expected usage scenarios for the architectural design. It specifies requirements and a validation framework delivered through user stories, enabling the co-design of the knowledge and data repository. The document also explains how user stories are transformed into requirements and summarizes the insights gained during this process.",{"@graph":14,"@context":73},[15,34,56],{"@type":16,"itemListElement":17},"BreadcrumbList",[18,23,27,31],{"item":19,"name":20,"@type":21,"position":22},"https://docshare.wps.com","Home","ListItem",1,{"item":24,"name":25,"@type":21,"position":26},"https://docshare.wps.com/template/","Template",2,{"item":28,"name":29,"@type":21,"position":30},"https://docshare.wps.com/template/presentations/","Presentations",3,{"item":32,"name":10,"@type":21,"position":33},"https://docshare.wps.com/template/soilwise-d11-usage-scenarios-requirements-v1-project-deliverable-final/242556/",4,{"url":32,"name":10,"@type":35,"image":36,"author":41,"headline":10,"publisher":44,"fileFormat":47,"inLanguage":8,"description":12,"dateModified":48,"datePublished":49,"encodingFormat":47,"isAccessibleForFree":50,"interactionStatistic":51},"DigitalDocument",{"url":37,"@type":38,"width":39,"height":40},"https://docshare.wps.com/thumbnails/soilwise-d11-usage-scenarios-requirements-v1-project-deliverable-final/242556.png","ImageObject",442,249,{"name":42,"@type":43},"Seraphina","Person",{"url":19,"name":45,"@type":46},"DocShare","Organization","application/pdf","2026-10-14","2026-09-12",true,{"@type":52,"interactionType":53,"userInteractionCount":55},"InteractionCounter",{"@type":54},"ViewAction",8,{"@type":57,"mainEntity":58},"FAQPage",[59,65,69],{"name":60,"@type":61,"acceptedAnswer":62},"What is the main objective of D1.1 Usage Scenarios, Requirements v1?","Question",{"text":63,"@type":64},"It defines how user needs are co-created and translated into expected usage scenarios, requirements, and a validation framework for the SoilWise repository.","Answer",{"name":66,"@type":61,"acceptedAnswer":67},"How does the document derive requirements from user stories?",{"text":68,"@type":64},"It presents a methodology that connects user stories to requirements and captures the insights produced during that process.",{"name":70,"@type":61,"acceptedAnswer":71},"What does the validation framework support in this deliverable?",{"text":72,"@type":64},"It is used to validate the architectural and repository-related outcomes by tying requirements to usage scenarios through user stories and acceptance criteria.","https://schema.org",{"og:url":32,"og:type":75,"og:title":10,"og:site_name":45,"og:description":12},"article",{"robots":77,"canonical":32},"index,follow",{"doc_id":79,"site_id":7},242556,1791731208,{"code":4,"msg":82,"data":83},"success",[84,88,93,98,103,108,113,118,123],{"id":85,"doc_module":22,"doc_module_name":25,"category_name":29,"show_sort_weight":86,"slug":87},11,90,"presentations",{"id":89,"doc_module":22,"doc_module_name":25,"category_name":90,"show_sort_weight":91,"slug":92},12,"Resumes",80,"resumes",{"id":94,"doc_module":22,"doc_module_name":25,"category_name":95,"show_sort_weight":96,"slug":97},14,"Invoices",70,"invoices",{"id":99,"doc_module":22,"doc_module_name":25,"category_name":100,"show_sort_weight":101,"slug":102},15,"Posters",60,"posters",{"id":104,"doc_module":22,"doc_module_name":25,"category_name":105,"show_sort_weight":106,"slug":107},16,"Social Media",50,"social-media",{"id":109,"doc_module":22,"doc_module_name":25,"category_name":110,"show_sort_weight":111,"slug":112},17,"Forms",40,"forms",{"id":114,"doc_module":22,"doc_module_name":25,"category_name":115,"show_sort_weight":116,"slug":117},18,"Letters",30,"letters",{"id":119,"doc_module":22,"doc_module_name":25,"category_name":120,"show_sort_weight":121,"slug":122},21,"Paper Templates",5,"papers-templates",{"id":124,"doc_module":22,"doc_module_name":25,"category_name":125,"show_sort_weight":4,"slug":126},158,"General","general-158",{"code":4,"msg":82,"data":128},{"doc_id":79,"user_id":129,"nickname":42,"user_avatar":130,"doc_module":22,"category_id":85,"category_name":29,"doc_title":10,"doc_description":12,"doc_content":131,"file_id":132,"file_url":133,"file_type":134,"file_size":135,"view_count":55,"is_deleted":4,"is_public":22,"is_downloadable":22,"audit_status":22,"page_count":136,"language":137,"language_code":8,"site_id":7,"html_lang":8,"table_of_contents":138,"faqs":139,"seo_title":140,"seo_description":12,"update_tm":141,"read_time":142},962075114101,"https://ap-avatar.wpscdn.com/avatar/e000253a75eb197efd?x-image-process=image/resize,m_fixed,w_180,h_180&k=1780044092746381165","D1.1 Usage scenarios, requirements, v1  \nM06/FEB 2024  \nThis project has received funding from the Horizon Europe research and innovation programme under Grant Agreement No 101112838.  \nAcronym SoilWise  \n\n| Project Full Title | An open access knowledge and data repository to safeguard soils |\n| --- | --- |\n| GA number | 101112838 |\n| Topic | HORIZON-MISS-2022-SOIL-01-01 |\n| Type of Action | HORIZON Innovation Actions |\n| Project Duration | 48 months |\n| Project Start Date | 1-Sep-23 |\n| Project Website | [https://soilwise-he.eu/](https://soilwise-he.eu/) |\n| Deliverable Title | D1.1 Usage Scenarios, Requirements, v1 |\n| Delivery Time (DOA) | M06 |\n| Deliverable Submission Date | 29/02/2024 |\n| Deliverable resubmission date | 25/06/2025 |\n| Status | final |\n| Dissemination Level | PU-Public |\n| Deliverable Lead | Thaïsa van der Woude (ISRIC) |\n| Author(s)/Organisation(s) | Thaïsa van der Woude (ISRIC), Fenny van Egmond (ISRIC), Paul van Genuchten (ISRIC), Christine Le Bas (INRAE), Somakanthan Somalingam (WE), Dajana Snopková (MU), Radu Giurgiu (EV ILVO), Tuna Coppens (EVILVO) |\n| Contributor(s) | ISRIC, MU, INRAE, EV ILVO, WR, ELO, CIRAD, CREA, VL O, ZALF, GAIA, WE, BIOS, NP |\n| Peer-Reviewers | Cenk Doenmez (ZALF), Theodoros Chalazas (EV ILVO) |\n| Contact | [thaisa.vanderwoude@isric.org](thaisa.vanderwoude@isric.org) |\n| Work Package | WP1 |\n| Dissemination level | Public |\n| Keywords | Use case, user story epic, user story/requirements, acceptance criteria, software, user group, validation framework, rolling plan |\n| Abstract | The purpose of this deliverable is to describe the methodology of cocreation and definition of the user needs, expected usage scenarios for the architectural design, requirements, and validation framework through user stories to facilitate the co-design of the repository. This document also defines the methodology from user stories to requirements and the insights obtained in that process. |\n\nDisclaimer  \nFunded by the European Union. Views and opinions expressed are however those of the author(s) only and do not necessarily reflect those of the European Union. Neither the European Union nor the granting authority can be held responsible for them.  \nList of Abbreviations  \nBIOS  \nBIOSENSE INSTITUTE - RESEARCH TECHNOLOGIES IN BIOSYSTEMS  \nAND DEVELOPMENT INSTITUTE FOR INFORMATION  \nCORDIS  \nCommunity Research and Development Information Service  \nCREA  \nCONSIGLIO PER LA RICERCA IN AGRICOLTURA E L'ANALISI DELL'ECONOMIA AGRARIA  \nDoD Definition of Done  \nELO  \nEuropean Landowners Organization  \nESDAC European Soil Data Centre  \nEV ILVO  \nEIGEN VERMOGEN VAN HET INSTITUUT VOOR LANDBOUW-EN VISSERIJONDERZOEK  \nEUSO EU Soil Observatory  \nGAIA  \nGAIA EPICHEIREIN ANONYMI ETAIREIA PSIFIAKON YPIRESION  \ni.c.w. In connection with  \nINRAE  \nINSTITUT NATIONAL L'ENVIRONNEMENT  \nDE RECHERCHE POUR L'AGRICULTURE, L'ALIMENTATION ET  \n ISRIC STICHTING INTERNATIONAL SOIL REFERENCE AND INFORMATION CENTRE   JRC  European Commission's Joint Research Centre  \n LTE Long Term Field Experiment   KPI  Key Performance Indicator  MRV Monitoring, Reporting, and Verification   MU  Masarykova univerzita  \nMVP Minimum viable product  \n NP  NEUROPUBLIC AE PLIROFORIKIS & EPIKOINONION  \n PC Project Coordinator   PTF  Pedotransfer function  PU Public   \n REA  European Research Executive Agency  R&I Research and Innovation   SC  Scientific Coordinator  \n SWR SoilWise Repository   \n TX.Y  Task, X= number of work package, Y= number of the task  TBA To be added (in the next iteration)   \n TM  Technical Manager  UC Use Case   \n US  User Story  VL O Vlaamse Gewest   WE  WETRANSFORM GMBH  WP Work package   \n WR  STICHTING WAGENINGEN RESEARCH  \n ZALF LEIBNIZ-ZENTRUM FUER AGRARLANDSCHAFTSFORSCHUNG   \nTable of Contents  \n1 INTRODUCTION ........................................................................................................................................8  \n1.1 PROJECT SUMMARY...........................................................","cbCaioEFDr9mD0hq","https://ap.wps.com/l/cbCaioEFDr9mD0hq","pdf",1566238,58,"English","# Introduction\n## Project Summary\n## WP1 Objectives and Relevant Tasks\n## Document Scope\n## Document Structure\n## Relationship to Other Project Deliverables\n# Terminology\n# Methodology\n## General Methodology\n## First Iteration\n## Next Cycle Co-Design Planning\n# Repository Usage Scenarios","[{\"question\":\"What is the main objective of D1.1 Usage Scenarios, Requirements v1?\",\"answer\":\"It defines how user needs are co-created and translated into expected usage scenarios, requirements, and a validation framework for the SoilWise repository.\"},{\"question\":\"How does the document derive requirements from user stories?\",\"answer\":\"It presents a methodology that connects user stories to requirements and captures the insights produced during that process.\"},{\"question\":\"What does the validation framework support in this deliverable?\",\"answer\":\"It is used to validate the architectural and repository-related outcomes by tying requirements to usage scenarios through user stories and acceptance criteria.\"}]","SoilWise - D1.1 Usage Scenarios, Requirements - v1 - project deliverable final | PDF",1789192033,20]