D6.2 Validation of Components and of the Integrated System, Version 1


Rajendra Akerkar, Therese Friberg, Matthias Moi, Alexis Gizikis, Massimo Cristaldi, Federico Sangiorgio, Christian Reuter, Andrew Muddiman, Mike Hewlett


This document establishes a verification and validation concept of the EmerGent. The validation activity is the key check-point at the transition from the development and deployment phases to demonstration, and will evaluate the (i) compliance of subsystems with specifications and reference implementation standards; (ii) relationships and discrepancies between what has been implemented and user requirements. The activity will run internal technical testing to verify that the specified technical subsystems and modules are actually working as specified. This document also includes the initial verification report.

The structure of the document is as follows:

Section 2 presents clear distinction between verification, validation and evaluation in the context of EmerGent. Then the section describes verification and validation strategy and plan.

Section 3 elaborates a role of different work packages as well as presents milestones associated with verification and validation activities. The section also describes related tasks and responsibilities in validation process.

Section 4 provides a brief outline of subsystems with timeline and dependencies among those subsystems.

Section 5 illustrates basic test cases based on gathered user requirements in deliverable D3.4. These test cases are prepared for system testing / validation as input for evaluation.

Section 6 presents first verification report including duly completed checklists for development and system integration phases. Then the section describes each subsystem with related requirements and also summarizes fulfilled user requirements in each subsystem.

Section 7 provides the conclusions and next step in the validation process.

Finally appendix A provides checklists to ensure that all activities related to the test plan have been addressed. These checklists will be used during the preparation, implementation and review of testing activities depending on the types of testing conducted. Further appendix B gives a sample questionnaire for validation.

Purpose of the document

The main purpose of the document is

  • to describe the process and procedures used by EmerGent developers to ensure that software has its design verified and its implementation validated against the EmerGent user requirements, and
  • to present basic test cases that have been prepared for validating the functionality of the system.