December 2023
Newsletter Subscription

151, boulevard de l'hôpital - 75013 Paris

D6.1 – Validation Process Specifications

D6.1 – Validation Process Specifications

  • Posted by Eleonora Bongiovanni
  • On March 28, 2022
Download is available until [expire_date]
  • Version
  • Download 4
  • File Size 672.96 KB
  • File Count 1
  • Create Date March 28, 2022
  • Last Updated May 26, 2022

D6.1 - Validation Process Specifications

CONFIDENTIAL DELIVERABLE, for more information contact us


Authors: SUPSI


Abstract: This deliverable reports on the validation process aiming at evaluating the success of the entire INEDIT solution made up by the development and integration of various avant-garde tools and technologies. The validation methodology follows the V-model approach already introduced in D2.3, whose methodological thread consists of four main steps: unit testing, integration testing, system testing and acceptance testing.
In this report, the integration testing will be not addressed since it will be the goal of work package 4. On the other hand, the other three steps first required a preliminary literature review, highlighting the most suitable platform KPIs and the characteristics they should have in order to be valuable and usable; then an interaction with the use case leaders and technology developers with the aim of defining ad hoc and consistent evaluation KPIs.

Specifically, the report is divided into four parts: the first two chapters are devoted to a brief introduction and the specification of the INEDIT validation approach. §3 is the core of the entire deliverable and, following the steps of the methodology, details the KPIs with a brief description and the related metric aimed at calculating the value. It is crucial to specify that the target values and benchmark for the validation are not defined in this document, but they will be determined in subsequently and complementary D6.6.
§4 contains the validation timeline defining a preliminary activity schedule of D6.6 and a brief risk analysis followed by mitigation actions. Finally, the document deals with the match between the high-level objectives (HLOs) specified in the DoA and the stakeholder requirements. Moreover, the annexes detail what stands behind the validation process presented in §3.