Attachment 0

Ref.
Ares(2018)4940772 - 26/09/2018
This project has received funding from the European Union’s Horizon 2020
research and innovation programme under grant agreement No 687289
Coastal Waters Research Synergy Framework
Verification and Validation Plan

Framework
Document Code: CORESYF-T2-VVR-VVP01-E-R
Delivery milestone: CDR-2 meeting (T0+28)

Deliverable identifier: D2.08
Version of document: 2.0 – last updated 15/05/2018
Dissemination level for document: PU
Table of Signatures
Name Function Signature
Prepared by Hervé Caumont WP2 Leader
Reviewed by Nuno Grosso WP3 Leader
Approved by Miguel Terra-Homem Executive Board Chair
Signatures and approvals appear on original

Verification and Validation Plan | Framework
Project start date: 01/01/2016

Project duration: 36 months
Revision Records
Version Date Changes Authors
1.0 15/12/1016 First issue of document for CDR-1 review Hervé Caumont
2.0 15/05/2018 First issue of document for CDR-2 review Hervé Caumont
PUBLIC Page 2 of 61
Table of Contents
1 Introduction 6
1.1 Purpose and Scope 6
1.2 Document Structure 7
2 SOFTWARE VERIFICATION PLAN 8
2.1 Software Verification Process Overview 8
2.1.1 Organization 8
2.1.2 Master Schedule 8
2.1.3 Techniques and Methods 8
2.1.4 Standards, Practices and Conventions 8
2.1.5 Resource Summary 8
2.2 Verification Activities 9
2.2.1 Software Validation Process Verification 9
2.2.2 Software Delivery and Acceptance Process Verification 9
2.3 Software Verification Reporting 9
3 SOFTWARE VALIDATION PLAN 9
3.1 Software Validation Process Overview 9
3.1.1 Organization 9
3.1.2 Master Schedule 9
3.1.3 Techniques and Methods 10
3.1.4 Standards, Practices and Conventions 10
3.1.5 Resource Summary 10
3.2 Software Validation Test Facilities 10
3.3 Software Validation Test Reporting 11
4 GENERAL V&V ADMINISTRATIVE PROCEDURES 11
4.1 Anomaly Report and Resolution 11
4.2 Task Iteration Policy 11
4.3 Deviation Policy 11
4.4 Control Procedures 11
5 ACCEPTANCE TESTS 12
5.1 Acceptance Test Designs 12
PUBLIC Page 3 of 61
5.2 Acceptance Test Specifications 13

5.3 Acceptance Test Procedures 59
6 Verification Control Matrix 59
7 References 59
8 Annex I : Template for the Test Procedures 60
List of Tables
Table 5-1 : V1 Acceptance Tests Specifications 13
List of Figures
No table of figures entries found.
PUBLIC Page 4 of 61
Acronyms and Abbreviations

CMS Corporate Management System
Co-ReSyF Coastal Waters Research Synergy Framework
EO Earth Observation
GUI Graphical User Interface
OS Operating System
SPR Software Problem Report
VCM Verification Control Matrix
VVP Verification & Validation Plan
VTP Validation Test Procedures
VTS Validation Test Specifications
PUBLIC Page 5 of 61
1 Introduction
The Co-ReSyF project will implement a dedicated data access and processing infrastructure, with
automated tools, methods and standards to support research applications using Earth Observation
(EO) data for monitoring of Coastal Waters, levering on the components deployed SenSyF
(www.sensyf.eu). The main objective is to facilitate the access to Earth Observation data and pre-
processing tools to the research community, towards the future provision of future Coastal Waters
services based on EO data.
Through Co-ReSyF‘s collaborative front end, even inexperienced researchers in EO will be able to
upload their applications to the system to compose and configure processing chains for easy
deployment on the cloud infrastructure. They will be able to accelerate the development of high-
performing applications taking full advantage of the scalability of resources available in the cloud
framework. The system’s facilities and tools, optimized for distributed processing, include EO data
access catalogues, discovery and retrieval tools, as well as a number of pre-processing tools and
toolboxes for manipulating EO data. Advanced users will also be able to go further and take full
control of the processing chains and algorithms by having access to the cloud back-end, and to
further optimize their applications for fast deployment for big data access and processing.
The Co-ReSyF capabilities will be supported and initially demonstrated by a series of early adopters
who will develop new research applications on the coastal domain, guide the definition of
requirements and serve as system beta testers. A competitive call will be issued within the project to
further demonstrate and promote the usage of the Co-ReSyF release. These pioneering researchers
in will be given access not only to the platform itself, but also to extensive training material on the
system and on Coastal Waters research themes, as well as to the project's events, including the
Summer School and Final Workshop.
1.1 Purpose and Scope

Define verification and validation strategy for the first version of the system Framework
requirements, explaining how each requirement is going to be verified and what is the criteria for
the verification of the same.
Within the Co-ReSyF platform it can be identified two major components that support the operation
of the research activities performed within the platform. One component is the Framework, which is
composed of all the things that support the environment where the applications are defined and
executed, and the other component are the Tools which are things that can be used to build an
application and to analyse/visualize the results of the application.
The Framework includes the Cloud back-end, which is the infrastructure that runs the applications in
the cloud and is in charge of coordinating and creating the VMs for distributed processing and
collection of input and output data. It also includes the Data Access API which is a set of tools that
allows the query and retrieval of the data within the Co-ReSyF catalogue and also any open data
catalogue available online. The other part of the framework is related to the user interaction and it is
the part that directly interfaces with the user, this includes the Front-end (GUI that provides the
PUBLIC Page 6 of 61
connection to all the platform functionalities) and the Expert Centre and Knowledge Base (wiki with
relevant information for newcomers of the platform to start using it).
The Tools live within the Framework and are a set of executables or libraries that can be used by the
researchers to build and manage their applications or handle the data. It includes the Automated
Orchestration, which is a set of tools designed to configure and monitor the execution of the
sequence of tasks that compose one application. The Image Inter-calibration, Atmospheric
corrections, Data Co-registration and Fusion and Other tools, which are tools used to process the
data commonly used by several applications and provided in a default tool-kit available to all users
of the platform. Finally there is also a set of Visualisation tools, which are provided as default by the
platform that allow the users to visualise and manipulate the data is commonly used data
visualization tools (different from the main front-end data visualization provided with the platform).
This document focuses solely on the V1 requirements of the Framework part of the Co-ReSyF
platform.
1.2 Document Structure

The structure of the document is as follows:
● Chapter 2 : describes the Verification approach.

● Chapter 3 : describes the Validation approach.
● Chapter 4 : describes the procedures for anomaly and deviations handling.
● Chapter 5 : describes the Acceptances tests to be executed.
● Chapter 6 : includes the Verification Control Matrix.
● Chapter 7 : details of the Reference Documents.
PUBLIC Page 7 of 61
2 SOFTWARE VERIFICATION PLAN
2.1 Software Verification Process Overview
2.1.1 Organization
The project will follow a simplified software verification process to be carried out by the PA&QA
responsible of the project, based on verifying only the acceptance testing activities defined in
(Deimos, 2016a).
The verification process will be carried out solely by the PA&QA and the results reported to the
Executive Board via the Verification Control Matrix (VCM) document (see Section 6). The VCM shall
also be included in the Verification and Validation Report.
2.1.2 Master Schedule

The verification activities will be carried out according to the schedule below, where the milestone
reviews in (Co-ReSyF, 2016c) are used as reference dates:
1. After PDR-1 the first version of the VCM is prepared with the requirements baseline for V1;
2. At the CDR-1 the VCM is reviewed;
3. After the implementation of all V1 functionality and the execution of the acceptance tests the
VCM is updated reflecting the status of the requirements;
4. At the SAR-1 the VCM is reviewed;
5. After PDR-2 the VCM is updated to include the updates to the requirements baseline for V2
(addition of requirements);
6. At the CDR-2 the VCM is reviewed;
7. After the implementation of all V2 functionality and the execution of the acceptance tests the
VCM is updated reflecting the status of the requirements;
8. At the SAR-2 the VCM is reviewed.
2.1.3 Techniques and Methods

The method to be used for the verification activities is to inspect the Verification and Validation Plan
and the Verification and Validation Report documents and record the findings related to the
requirements traceability to tests and test results in the VCM document.
2.1.4 Standards, Practices and Conventions

The verification activities follow the standard defined in the Deimos Corporate Management System
(Deimos, 2016a), tailored for the simplified approach of this project that focus only on the
verification of the Acceptance activities.
2.1.5 Resource Summary

The verification activities only require the QA&PA responsible.
PUBLIC Page 8 of 61
2.2 Verification Activities
2.2.1 Software Validation Process Verification

The verification of the Software Validation Process uses as input the Acceptance Test Specifications
(contained in this document) and checks that all the requirements applicable to the respective
software version (V1 or V2) have a test case specification (with defined acceptance criteria). The
traceability between requirements and test cases is recorded in the VCM, which is the output of the
verification process. All the requirements applicable to the respective software version need to be
traced to a test case and the acceptance criteria defined in order to consider the verification
successful.
2.2.2 Software Delivery and Acceptance Process Verification

The verification of the Software Delivery and Acceptance Process uses as input the Verification and
Validation Report document, which contains the results of the execution of the acceptance tests
performed for the respective software version.
The verification consists in checking the result of the test steps that check each requirement and
record if the requirement is passed or failed in the VCM document. All the requirements applicable
to the software version need to have been tested with clear indication of their status in order to
consider the verification successful.
2.3 Software Verification Reporting

The results of the software verification activities will be recorded in the VCM document, which will
be delivered, attached to the Verification and Validation Plan and Report documents.
3 SOFTWARE VALIDATION PLAN

3.1 Software Validation Process Overview
3.1.1 Organization
The project will follow a simplified software validation process, based on carrying out only the
acceptance testing activities defined in (Deimos, 2016a).
The validation activities will be carried out by the WP3 leader, with assistance of the Deimos
development team. The WP3 leader is responsible for defining, preparing and executing the
acceptance tests to be carried out during the Acceptance campaign.
The results of the Acceptance Campaign will be reported to the Executive Board in the Verification
and Validation Report document.
3.1.2 Master Schedule

The Validation activities will be carried out according to the schedule below, where the milestone
reviews in (Co-ReSyF, 2016c) are used as reference dates:
PUBLIC Page 9 of 61
1. After PDR-1 the first version of the Acceptance Tests specification is prepared with the
requirements baseline for V1;
2. At the CDR-1 the Acceptance Tests specification is reviewed;
3. During the implementation period of all V1 functionality the test procedures for the Acceptance
Tests is defined;
4. One month before SAR-1 (SAR-1 – 1m), the Acceptance Tests are executed and the results are
recorded in the Verification and Validation Report;
5. At the SAR-1 the Verification and Validation Report is reviewed;
6. After PDR-2 the Acceptance Tests specification is updated to include the updates to the
requirements baseline for V2 (addition of requirements);
7. During the implementation period of all V2 functionality the test procedures for the new
Acceptance Tests is defined;
8. One month before SAR-2 (SAR-2 – 1m), the new Acceptance Tests are executed and the results
are recorded in the Verification and Validation Report;
9. At the SAR-2 the Verification and Validation Report is reviewed.
3.1.3 Techniques and Methods

The method to be used for the Validation activities is to execute a set of Acceptance tests on the
operational platform in order to verify that the requirements defined in (Co-ReSyF, 2016b) are
implemented, for the applicable software version. There is only one testing method foreseen, which
is to execute a set of procedural steps on the running software that will verify the functionality of
the requirement. The validation criteria and ID of the requirement will be defined at the applicable
step of the procedure. The information will be recorded in the Verification and Validation Report
document.
3.1.4 Standards, Practices and Conventions

The validation activities follow the standard defined in the Deimos Corporate Management System
(Deimos, 2016a), tailored for the simplified approach of this project that focus only on the
Acceptance activities.
3.1.5 Resource Summary

The validation activities will require the execution of the defined acceptance test procedures. These
procedures will be executed by the WP3 Leader and will use a standard PC (or Laptop) to connect to
the online platform. Additional open source tools may be used in the local PC/Laptop for analysis of
the results, if needed, although an effort will be made when defining the test procedures to use only
the functionalities provided by the online platform.
3.2 Software Validation Test Facilities

The validation will be done directly on the operational platform, and being it an online platform the
needed test facilities are a simple PC/Laptop with a good network connection (e.g. it is advisable to
have at least a 100 Mbps network). There is no restriction on the OS of the used PC/Laptop.
PUBLIC Page 10 of 61
3.3 Software Validation Test Reporting

The results of the Acceptance tests to be carried out for the validation activities will be reported in
the Verification and Validation Report document. For each acceptance test procedure the result of
the step shall be recorded and the date of when the test procedure was executed also.
4 GENERAL V&V ADMINISTRATIVE PROCEDURES
4.1 Anomaly Report and Resolution

The procedure for Light Process for Problem Management for small projects as defined in (Deimos,
2016b) will be followed for anomaly reporting and resolution. The difference to the procedure as
defined in (Deimos, 2016b) is that the project manager is replaced by the WP3 Leader for the case of
Validation of the Tools Requirements.
The SPRs will be raised and traced in the JIRA Deimos issues management tool.
4.2 Task Iteration Policy

An acceptance test procedure should be repeated whenever a failed step in the procedure prevents
the validation of a requirement and as a result of that a software modification is needed. For those
cases the full test procedure shall be repeated in order to ensure that all the requirements in that
same test procedure are validated after the change in the software.
4.3 Deviation Policy

All the requirements that are not implemented and are proposed to not be verified for a respective
applicable version (or not verified at all), will need to be flagged in the VCM document. The VCM will
be reviewed by the Executive Board and the deviation will need to be approved at the Executive
Board meeting. The authorization for the deviation shall be recorded at the meeting minutes and the
same referenced in the VCM document.
4.4 Control Procedures

As described in Section 5 of the PMP (Co-ReSyF, 2016c), the developed software shall be stored in a
Git repository (configuration control system). The results of the software verification and validation
shall be recorded and stored in the VCM and Verification and Validation Report documents and shall
be stored and versioned in the Deimos document management system (as also described in the
same Section 5 of the PMP).
5 ACCEPTANCE TESTS
5.1 Acceptance Test Designs
The Acceptance tests are designed to test a specific functionality that can cover only one
requirement or several requirements. The approach for grouping or not requirements in one test
case is decided on a case by case basis and best practice is to ensure that the Pass/Fail Criteria can
be written in a simple way.
If the Pass/Fail Criteria becomes complex to describe this is an indicator that the test case is covering
too many requirements.
Several test cases can be further grouped into one test procedure, when defining the test
procedures, if they share common steps, in order to reduce the execution time of the tests. Clear
candidates to grouping are test cases that have the same scenario and inputs.
A test case is specified using the following fields:

● A unique identifier for each VTS.
● A brief description of the functionality that the test aims to validate.
● The set of requirements that specify the functionality being tested. Note that the test cases
often entail the execution of other functionalities besides the one that is the subject of the test,
but the requirements associated with those other functionalities are not listed (i.e. they are not
part of the aims of that particular test case). This is done deliberately to make it easier to define
the pass/fail criteria for each test.
● A brief description of the overall scenario for the test (including the state that the software and
the test environment have to be in before the test begins), i.e. explains how the functionality
will be tested.
● The inputs to the test, described in more detail than in the test scenario. Note that the table
does not give the complete, detailed description of all the inputs, because that is done instead in
the test procedure.
● The test pass criteria, e.g. in terms of the expected values of certain outputs.
5.2 Acceptance Test Specifications
Table 5-1 : V1 Acceptance Tests Specifications
Identifiers of
Functionality
VTS No. requirements Test Scenario Required Inputs Pass/Fail Criteria
Tested
tested
FMWK-VTS-01 App Designer CORESYF-FMWK-CBE-1 As a Developer user, I want to Co-ReSyF online platform 1. The application structure on the
environment design and build hosted processing available, with a valid user with Sandbox /home application
application as a scalable workflow access to a sandbox. folder is generated from the
Application Design for distributed computing, by sandbox “application archetype”
and Integration making use of a cost-effective maven tool, for either 'python' or
Cloud Sandbox environment, so ‘bash’ wrapping functions.
Processing that I only focus on the data staging 2. The workflow viewer on the
Workflows design and data publication requirements Sandbox dashboard reflects the
of a single node, designed as a actual workflow definition (jobs
unitary part of a potentially larger and DAG sequence).
computing cluster of similar nodes. 3. User can execute his workflow
using the CIOP tools like ciop-run
or through the sandbox
Dashboard WPS client.
4. The workflow run correctly
reports success or eventual
failure in the workflow steps
Identifiers of
Functionality
Tested
tested
FMWK-VTS-02 App Integration CORESYF-FMWK-CBE-2 As a Developer user, I want to wrap Co-ReSyF online platform 1. A section <requires> of the
environment my existing, native processing available, with a valid user with Maven file "pom.xml" is provided
library and only have to write access to a sandbox. where a Developer can specify
Application Design Hadoop callbacks (either in R, RPM dependencies.
and Integration Python or Bash) in order to enable 2. User can create and reference
linear scalability on cost-effective RPM packages (e.g. from maven
Additional commodity hardware, automated or yum repositories) for
Application handling of hardware failures, and dependencies.
Programming performance improvement through 3. Python dependencies
Models seamless data locality management specification is automatically
performed by leveraging the
Supported conda package management
programming system.
languages 4. Bash, Python or R callback
functions are available from the
sandbox environment to ensure
the linear scalability of relevant
workflow nodes
Identifiers of
Functionality
Tested
tested
FMWK-VTS-03 App Interoperability CORESYF-FMWK-CBE-3 As a Developer user, I want to Co-ReSyF online platform 1. Metadata collections are
environment leverage standard interfaces for available, with a valid user with queryable via the OpenSearch
the data access of my application, access to a sandbox. interface of the Platform’s Data
Data discovery and so that my application deployment Agency
access benefits from automated data 2. The Platform’s Data Agency
access mechanisms, whatever the protocol is referencing all
data sources are exploited. available enclosure elements for
the data access and data staging
operations
3. The sandbox tool ‘opensearch-
client’ is providing the
mechanisms to deliver enclosure
references to the data staging
functions
Identifiers of
Functionality
Tested
tested
FMWK-VTS-04 App reusability CORESYF-FMWK-CBE-4 As a Developer user on Terradue Co-ReSyF online platform 1. The Application can be bundled
Cloud Platform, I want to save my available, with a valid user with in a single package (in RPM
Application processor integration as a Cloud access to a sandbox. format) containing the
Integration template, so that I can publish and
application resources and the
expose that service on a
Marketplace for producer partners dependencies specification.
Application 2. User can install the Application
to exploit it on a selected Cloud
Packaging under the /application path,
provider infrastructure, for massive
processing deployments. using the Maven installation
procedure.
Identifiers of
Functionality
Tested
tested
FMWK-VTS-16 Usage statistics CORESYF-FMWK-CBE-5 As a Geoportal administrator, I Cloud-backend API and 1. The Cloud-Platform can expose
want to monitor the Cloud documentation for the usage of via a dedicated API the
backend resources usage Portal developers informations related to the cloud
(processing jobs, processed backend resources consumed by
datasets...) taking in account the the processing jobs and the
variety of users processed datasets
2. Third-party developers working
with the Cloud Platform tools
and services can access the
documentation and integrate the
provided information in their
Portal Admin pages (e.g. for the
usage of Portal Admin users)
- END OF CLOUD BACK-END REQUIREMENTS -
Identifiers of
Functionality
Tested
tested
FMWK-VTS-05 Missions catalogue CORESYF-FMWK-API-1 As a developer I want to be able to Co-ReSyF online platform 1. The collections accessible are:
access data from different missions available, with a valid user with ● Sentinel-1
in order to query their catalogue access to the Catalogue client ● Sentinel-2
Discovery
based on geographic areas, dates, ● Sentinel-3
Mechanisms ● Radarsat-2
types of products and other
● TerraSAR-X
metadata (e.g. cloud cover) and
Data Gateway ● Envisat
download the data for use in my ● Cosmo-SkyMed
application. ● Landsat
● WorldView
● MODIS (TERRA/AQUA)
● ERS-1
● ERS-2
● Jason-1
● Jason-2
● Jason-3
● Cryosat-2
● SARAL/AltiKa
● Odyssea
2. With inclusion of browse image
references in the T2 catalogue, when
available online already from the data
provider
Identifiers of
Functionality
Tested
tested
FMWK-VTS-06 Auxiliary data CORESYF-FMWK-API-2 As a developer I want to be able to Co-ReSyF online platform 1. The datasets accessible for the
catalogue access data from online archives available, with a valid user with Bathymetry (LNEC/IH) RA are:
RA-1 LNEC from services like meteorological, access to the Catalogue client ● Bathymetry EMODNET
ship locations, land maps, digital (http://www.emodnet-
Data Gateway hydrography.eu/content/content.asp?men
elevation models, tides and others
u=0040000_000000) - ASCII CSV, ESRI
in order to support the processing
Extensibility and ASCII, netCDF (CF), GeoTIFF and
of my application. Fledermaus SD file formats
Data Resources
Evolution ● Wave buoys data - source depends on case
study site location
● Meteo data (winds) - no source and file
format identified
● Land Mask -
(http://www.viewfinderpanoramas.org/de
m3.html#nasa) - HGT file format
● Mean free-surface elevation level (tidal
level) - no source and file format identified
Identifiers of
Functionality
Tested
tested
FMWK-VTS-07 Auxiliary data CORESYF-FMWK-API-2 As a developer I want to be able to Co-ReSyF online platform 1. The datasets accessible for the
catalogue access data from online archives available, with a valid user with Bathymetry, benthic classification and
RA-2 ACRI from services like meteorological, access to the Catalogue client water quality (ACRI) RA are:
ship locations, land maps, digital ● Tides - no source and file format identified
Data Gateway (source depends on case study site
location)
Extensibility and ● Bathymetry -no source and file format
of my application. identified (source can be the same as
Data Resources
Evolution LNEC/IH)
● Land Mask - no source and file format
identified (source can be the same as
LNEC/IH)
Identifiers of
Functionality
Tested
tested
FMWK-VTS-08 Auxiliary data CORESYF-FMWK-API-2 As a developer I want to be able to Co-ReSyF online platform 1. The datasets accessible for the Vessel
catalogue access data from online archives available, with a valid user with detection & Oil Spill Detection (UCC) RA
RA-3 UCC from services like meteorological, access to the Catalogue client are:
ship locations, land maps, digital ● Land Map
Data Gateway ● SRTM 5 minute DEM
(http://www2.jpl.nasa.gov/srtm/) -
Extensibility and Geotiff format
of my application. ● 1 km USGS land/sea mask
Data Resources
Evolution (http://edc2.usgs.gov/1KM/land_sea
_mask.php) - Geotiff format
● Meteo, namely wind speed and direction
and possibly the precipitation events.
● NCDC
(http://www.ncdc.noaa.gov/data-
access/marineocean-data) - station
and gridded data, various formats,
usually, ASCII or CSV text formats
are available
● Wind - Copernicus Marine
Environment Monitoring Service
(CMEMS)
(http://marine.copernicus.eu/web/6
9-interactive-catalogue.php) -
NETCDF file format
● Global Precipitation Climatology
Centre
(http://www.esrl.noaa.gov/psd/data
/gridded/data.gpcc.html) - netCDF
file format
● AIS data
● EXACTEARTH
(http://www.exactearth.com/produ
cts/exactais-archive) - CSV format
● MarineTraffic AIS archive
(http://www.marinetraffic.com/it/p/
ais-historical-data) - XML and CSV
formats
● EMSA CleanSeaNet
(http://www.emsa.europa.eu/csn-
menu.html) data complemented by
vessel detection SafeSeaNet data -
no file format identified
● Oil spill archive - EMSA CleanSeaNet
(http://www.emsa.europa.eu/csn-
menu.html) - no file format identified
Identifiers of
Functionality
Tested
tested
FMWK-VTS-09 Auxiliary data CORESYF-FMWK-API-2 As a developer I want to be able to Co-ReSyF online platform 1. The datasets accessible for Time series
catalogue access data from online archives available, with a valid user with processing for hyper temporal optical
RA-4 UCC from services like meteorological, access to the Catalogue client data (UCC) RA are:
ship locations, land maps, digital ● ST Front data (extracted using
Data Gateway separate algorithms) - no source of
file format identified
Extensibility and ● Flow through data from ocean
of my application. transects - Marine Institute
Data Resources
Evolution (http://www.marine.ie/Home/) - no
file format identified
Identifiers of
Functionality
Tested
tested
FMWK-VTS-10 Auxiliary data CORESYF-FMWK-API-2 As a developer I want to be able to Co-ReSyF online platform 1. The datasets accessible for the Ocean and
catalogue access data from online archives available, with a valid user with Coastal altimetry (NOC) RA are:
RA-5 NOC from services like meteorological, access to the Catalogue client ● Instrumental corrections (provided by space
ship locations, land maps, digital agencies with raw data) - no file format
Data Gateway
elevation models, tides and others identified
● Updated Atmospheric and surface effect
Extensibility and corrections RADS archive
of my application.
Data Resources (http://rads.tudelft.nl/rads/rads.shtml) -
Evolution netCDF format
● Small tide gauge dataset for validation.
Possible sources
● Permanent Service Mean Sea Level
(http://www.psmsl.org/data/obtaining/)
- semi-colon delimited values
● The Global Sea Level Observing System
(http://www.gloss-
sealevel.org/data/#.VwZZ5Ktlq1E) -
maybe there are other formats but semi-
colon delimited values are available
● Système d'Observation du Niveau des
Eaux (http://www.sonel.org/-Tide-
gauges,29-.html) - tab delimited txt
format
● Mean Sea Level climate projections
● IPCC AR5 (available through
https://pcmdi.llnl.gov/projects/esgf-llnl/)
- results from many models available
from sample all in netCDF format
● UK Climate Projections (UKCP09)
(http://www.metoffice.gov.uk/climatech
ange/science/monitoring/ukcp09/downl
oad/) - available in comma delimited text
file format
Identifiers of
Functionality
Tested
tested
FMWK-VTS-11 External data access CORESYF-FMWK-API-3 The platform should be able to Co-ReSyF online platform 1. The Platform’s Data Agency provides
and search search and access for the other available, with a valid user with a brokered access to selected
types of data (as mentioned access to the Catalogue client external data catalogues
EO Data resources above), from other websites, for 2. The Platform’s Data Agency provides
Types the study region using technologies a brokered access to selected
such as OpenDAP or similar external data repositories
3. Inclusion of level 3 data products is
EO Data resources
provided for:
Provisioning
○ Ocean color
■ ESA CCI Ocean Color
project, hosted on CEDA
NEODC servers
○ Sea level
■ ESA CCI Sea Level project,
hosted on CEDA NEODC
servers
○ Sea Surface Temperature (SST)
■ ESA CCI SST project, hosted
on CEDA NEODC servers
Identifiers of
Functionality
Tested
tested
FMWK-VTS-17 User access to CORESYF-FMWK-API-4 The Platform should allow users Co-ReSyF online platform 1. Back-end capacity to be accessed
personal catalog to make their high quality output available, with a valid user with via Terradue Cloud Platform’s
index and data products available on the data access to the Catalogue client Data API, queried from the Co-
storage on the catalogue for others to use, and ReSyF Geoportal front-end
Cloud Platform to be able to download their
output processing results (to
examine data on their own
desktop tools)
- END OF DATA API REQUIREMENTS -
Identifiers of
Functionality
Tested
tested
FMWK-VTS-18 Dataset creation CORESYF-FMWK-FRONT-1 As a user I want to be able to Co-ReSyF online platform 1. After logging into the Co-ReSyF
create a dataset composed of my available, with a valid user. platform the user can access the
own data and data from the Co- Data Search Centre
ReSyF catalogue in order to be 2. The user is able to create a data
able to use the dataset as input package
to the application that I want to 3. The user is able to perform a
run. data search into the Co-ReSyF
catalogue
4. The user is able to add the results
of that search to a data package
5. The user is able to access the
Application Centre
6. The user is able to run
successfully until the end an
application that uses the
products included in the created
data package
Identifiers of
Functionality
Tested
tested
FMWK-VTS-19 Catalogue search CORESYF-FMWK-FRONT-2 As a user I want to be able to Co-ReSyF online platform 1. After logging into the Co-ReSyF
location filter filter the Co-ReSyF catalogue available, with a valid user. platform the user can access the
data by a geographic area in a Data Search Centre
world map in order to easily find 2. The user is able to perform a
the data relevant to the area of data search into the Co-ReSyF
interest for my study. catalogue after defining a
geographic area either by
bounding box/polygon or by
input the box coordinates
3. The platform shows the correct
results for the defined
geographic area
Identifiers of
Functionality
Tested
tested
FMWK-VTS-20 Catalogue CORESYF-FMWK-FRONT-3 As a user I want to be able to Co-ReSyF online platform 1. After logging into the Co-ReSyF
search apply a set of filters to the Co- available, with a valid user. platform the user can access the
additional filters ReSyF catalogue data in order to Data Search Centre
be able to choose a set of 2. The user is able to perform a
missions, time span, data search into the Co-ReSyF
instruments, types of data, and catalogue defining the mission,
other metadata (e.g. cloud the instrument, data type, the
cover, quality degradation). time interval and the cloudiness
(in case of optical data)
3. The search results are correct
according to the parameters
inputted by the user
Identifiers of
Functionality
Tested
tested
FMWK-VTS-21 Application CORESYF-FMWK-FRONT-4 As a user I want to be able to Co-ReSyF online platform 1. After logging into the Co-ReSyF
execution select a dataset and an available, with a valid user. platform the user is able to
application in order to process create a data package with the
the data and obtain some necessary data to run an
outputs which I want to analyse. application
2. The user can access the
Application Centre, access the
required application from the
application list, define the
corresponding input parameters
and run the application
3. The user is able to see that the
application has ran successfully
until the end in the Job
Monitoring interface
4. The user is able to download the
results and see that they match
what he expected
5. The expert user is able to check
criteria 2 to 4 but in in the
Workflow Manager
Identifiers of
Functionality
Tested
tested
FMWK-VTS-22 Application editing CORESYF-FMWK-FRONT-5 As a user I want to be able to Co-ReSyF online platform 1. After logging into the Co-ReSyF
create a new application using a available, with a valid user. platform the user is able to
diagram and connecting boxes access the Workflow Manager
(simulink style) which I take from 2. The user is able to access the Edit
a pool of available tasks in Co- Workflows interface and choose
ReSyF in order to define a new the Processing Components he
application from scratch or to requires to define a new
modify an existing application. application workflow
3. The user is able to run the newly
defined application using a
created data package
until the end
5. The user is able to download the
results and see that they match
what he expected
Identifiers of
Functionality
Tested
tested
FMWK-VTS-25 Maps display CORESYF-FMWK-FRONT-8 As a user I want to be able to Co-ReSyF online platform 1. After logging into the Co-ReSyF
send data from my console into available, with a valid user. platform the user is able to
a world map in order to see the access the Data Visualisation
data with geographical Centre
information and combining 2. The user is able to see the
different outputs into one single outputs of all its previous
map. applications listed as layers to be
visualised
3. The user is able to select the
layers he wants to visualise and
when he does he will be able to
see them combined on a world
map
Identifiers of
Functionality
Tested
tested
FMWK-VTS-26 Maps Layer control CORESYF-FMWK-FRONT-9 As a user I want to be able to Co-ReSyF online platform 1. After logging into the Co-ReSyF
have different data in the world available, with a valid user. platform the user is able to
map as layers in order to be able access the Data Visualisation
to see or hide different layers in Centre
an interactive manner and 2. The user is able to see the
control the aspect of each layer outputs of all its previous
(e.g. colour table, labels, applications listed as layers to be
contours, etc...). visualised
layers he wants to visualise and
when he does he will be able to
see them combined on a world
map
4. The user is able to see or hide
different layers in an interactive
manner and control the style of
each layer (colour table,
contours, transparency)
Identifiers of
Functionality
Tested
tested
FMWK-VTS-27 Data selection CORESYF-FMWK-FRONT-10 As a user i want to be able to Co-ReSyF online platform 1. After logging into the Co-ReSyF
select manually the images available, with a valid user. platform the user is able to
from the result of the access the Data Visualisation
application of data filters that I Centre
want to include in my work 2. The user is able to see the
environment outputs of all its previous
applications listed as layers to be
visualised
layers he wants to filter from his
work environment
4. The user is able to hide the
selected layers
5. The user is able to add the
deleted layers back to its work
environment
Identifiers of
Functionality
Tested
tested
FMWK-VTS-28 Restricted access to CORESYF-FMWK-FRONT-11 As a user I want to be able to Co-ReSyF online platform 1. The user is able to access the
work environment have access to a restricted available, with a valid user. login page of the Co-ReSyF
work environment where I platform
have/run my research work 2. The user is able to login with a
materials (e.g. datasets, valid user
applications) 3. After logging into the Co-ReSyF
platform the user is able to see
only the data packages he
created, the application runs he
ordered and the result datasets
from those application runs
Identifiers of
Functionality
Tested
tested
FMWK-VTS-29 Work environment CORESYF-FMWK-FRONT-12 As a user I want to be able to Co-ReSyF online platform 1. After logging into the Co-ReSyF
sharing provide access to my work available, with a valid user. platform the user is able to
environment to external provide to another user access to
collaborators specific data packages,
application runs and results
datasets
2. The second user is able to access
the shared data packages,
application runs and results
datasets.
Identifiers of
Functionality
Tested
tested
FMWK-VTS-30 Session datasets CORESYF-FMWK-FRONT-13 As a user I want to be able to Co-ReSyF online platform 1. After logging into the Co-ReSyF
and workflows store at least the different input available, with a valid user. platform the user is able to see
storage and output datasets and the data packages he created,
workflows that I used/created past application runs and results
in a specific sesssion to reuse at dataset. That information is
a later time. always available to the user
whenever he logs into the
platform
2. The expert user is able to do the
same in the Workflow Manager
Identifiers of
Functionality
Tested
tested
FMWK-VTS-31 Data export CORESYF-FMWK-FRONT-14 As a user I want to be able to Co-ReSyF online platform 1. After logging into the Co-ReSyF
export my data to the desktop available, with a valid user. platform the user is able to
namely, raster and vector access the list of past application
imagery, table data, printable runs export/ download the
images of maps or plots, videos results from those runs.
other processing function
outputs (e.g. linear model or
cluster function, associated
model statistics)
Identifiers of
Functionality
Tested
tested
FMWK-VTS-32 Compilation of CORESYF-FMWK-FRONT-15 The platform shall enable the Co-ReSyF online platform 1. After logging into the Co-ReSyF
images in video compilation of an image available, with a valid user. platform the user is able to
format dataset into a video format and access the Data Visualisation
its visualization Centre
2. The user is able to see the
outputs of all its previous
applications listed as layers to be
visualised
3. For a specific output dataset
corresponding to a time series
the user is able to access a
animation panel and setup an
animation by defining its start
and end time
4. The animation runs successfully
in the data Visualisation Centre
Identifiers of
Functionality
Tested
tested
FMWK-VTS-33 Distance CORESYF-FMWK-FRONT-16 As a user I want to be able to Co-ReSyF online platform 1. After logging into the Co-ReSyF
measurements select two points in a map with available, with a valid user. platform the user is able to
data displayed and get the access the Data Visualisation
distance between the two Centre
points 2. The user is able to select a
Distance Measurement Tool
3. The user is able to define two
points in the world map interface
correct distance value between
these two points
Identifiers of
Functionality
Tested
tested
FMWK-VTS-35 Help Access from CORESYF-FMWK-FRONT-18 As a user I want to be able to Co-ReSyF online platform 1. After logging into the Co-ReSyF
the geoportal access the help pages available, with a valid user. platform the user is able to
(Knowledge Base/User access a button that will provide
manual/Tutorials) from the access to the platform
main page of the geoportal, in Knowledge Base
order to be able to learn how to 2. After clicking the button the user
use the geoportal. Having two is redirected to the Knowledge
windows open would help in Base
doing a step by step tutorial.
- END OF “FRONT-END” REQUIREMENTS -
Identifiers of
Functionality
Tested
tested
FMWK-VTS-36 Identification of CORESYF-FMWK-ORCH-1 As a user I want to be able to see Co-ReSyF online platform 7. After logging into the Co-ReSyF
status of the in a form of a diagram the available, with a valid user. platform the user can access the
processing current step at which my Application Centre
processing currently is in relation 8. The user is able to run an
to the whole processing chain in application with an appropriate
order to quickly assess if I am at data package
the beginning, middle or end of 9. The user is able to monitor the
the processing. processing step and the
percentage of processing of the
application in the Job monitoring
interface
10. The expert user can access the
Workflow Manager, run an
application and see the
processing status log in the
Workflows interface, including
information on the percentage
already processed, the outcome
of the steps already processed
and the status of the current step
Identifiers of
Functionality
Tested
tested
FMWK-VTS-37 Summary of CORESYF-FMWK-ORCH-2 As a user I want to be able to Co-ReSyF online platform 1. After logging into the Co-ReSyF
applications status access the history of the available, with a valid user. platform the user can access the
and history applications that I have executed Application Centre
and the ones that are currently 2. The user is able to see all the
executing in order to see what is past and current application
their status. runs, their status, see the
parameterization used in each
run and access the outputs
Workflow Manager and see all
the current and past application
runs, see their status and check
the error log in the Workflows
interface
Identifiers of
Functionality
Tested
tested
FMWK-VTS-38 Failure notification CORESYF-FMWK-ORCH-3 As a user I want to be notified if Co-ReSyF online platform 1. After logging into the Co-ReSyF
a step in the processing fails and available, with a valid user. platform the user can access the
my application is aborted in Application Centre
order to check as quickly as 2. The user is able to run an
possible the error and re-execute application with an appropriate
my application. data package
warning of a processing job
failure in the Job monitoring
interface
Workflow Manager and see the
processing status log for on-going
application runs and see the
warning of processing failure as
soon as it occurs
Identifiers of
Functionality
Tested
tested
FMWK-VTS-39 Time-out CORESYF-FMWK-ORCH-4 As a user I want to be able to Co-ReSyF online platform 1. After logging into the Co-ReSyF
configuration configure a time-out, in terms of available, with a valid user. platform the user can access the
hours, for the execution of my Application Centre
Abort of the application in order to set a limit 2. The user is able to setup a time
application in the time that the application out parameter in the
can be running in order to parameterization of an
process the data. application
3. The user is able to confirm that
the process stopped when the
time exceeds the value inputted
in the time out configuration.
Identifiers of
Functionality
Tested
tested
FMWK-VTS-40 Abort of the CORESYF-FMWK-ORCH-5 As a user I want to be able to Co-ReSyF online platform 1. After logging into the Co-ReSyF
application cancel an application that is available, with a valid user. platform the user can access the
being executed in the Co-ReSyF Application Centre
platform in order to correct for a 2. The user is able to stop an on-
mistake when launching an going application by pressing a
application. button in the Job Monitoring
Interface
3. The user is able to confirm that
the process stopped.
Identifiers of
Functionality
Tested
tested
FMWK-VTS-41 Automatic setup of CORESYF-FMWK-ORCH-6 As the front end I want to be Co-ReSyF online platform 1. After logging into the Co-ReSyF
application able to pass the configuration of available, with a valid user. platform the user can access the
the application done by the user Application Centre
to the orchestration engine so 2. The user is able to access any
that the setup of the VM can be application list, define the
done automatically by the corresponding input parameters
orchestration engine. and run the application
4. The expert user is able to do the
same in the Workflow Manager
Identifiers of
Functionality
Tested
tested
FMWK-VTS-42 Output processing CORESYF-FMWK-ORCH-7 As a user I want to be able to Co-ReSyF online platform 1. After logging into the Co-ReSyF
metadata have automatically associated to available, with a valid user. platform the user can access the
the metadata file of the output Application Centre
products all the information on 2. The user is able to access any
the processing performed on the application list, define the
data and the characteristics of corresponding input parameters
the output data (e.g. date, and run the application
spatial resolution) 3. The user is able to see that the
4. after the job ends the user is able
to download the output and
check that the metadata file is
there
5. The user checks if all information
that he requires is there
Identifiers of
Functionality
Tested
tested
FMWK-VTS-43 Application CORESYF-FMWK-ORCH-8 As a user I want to have a set of Co-ReSyF online platform 1. After logging into the Co-ReSyF
Modules metadata clear concise and contextual available, with a valid user. platform the user can access the
module metadata associated to Workflow Manager
each processing module that 2. The user is able to see the
fully describes it in order to different Processing Components
provide to the user full list, choose one of them to
traceability of all image compose a workflow and run it
processing jobs (e.g. author, successfully with the appropriate
version, algorithm, bibliography) parameters.
3. In the end of the processing the
output metadata must include all
metadata required by the user to
be able to trace the output to the
corresponding processing
module.
- END OF ORCHESTRATION MANAGER REQUIREMENTS -
Identifiers of
Functionality
Tested
tested
FMWK-VTS-12 Replay application CORESYF-FMWK-EXPT-1 As a user I want to re-run any of Co-ReSyF online platform 1. The user can select an existing
with different the core applications but with my available, with a valid user with application, modify its default
parameters elected AOI and parameter set access to the Expert Center parameter values in an input
form, and submit the newly
PaaS Environment configured application workflow
for execution
Identifiers of
Functionality
Tested
tested
FMWK-VTS-13 Expert center on CORESYF-FMWK-EXPT-2 As I user I want to use a framework Co-ReSyF online platform 1. Document resources are
how to run an tool and need guidance available, with a valid user with accessible online to support
application with access to the Expert Center users on how to run an
user defined ROI application with user defined ROI
and parameters and parameters
2. Collaborative tools are accessible
Document online to support users on how
Resources to run an application with user
defined ROI and parameters
Collaboration Tools
Identifiers of
Functionality
Tested
tested
FMWK-VTS-14 Application CORESYF-FMWK-EXPT-3 As a user I have approached the Co-ReSyF online platform 1. The workflow viewer on the
Integration framework as a means to research available, with a valid user with Expert Center dashboard reflects
and just want to use tools but access to the Expert center the actual workflow definition
define my own application (jobs and DAG sequence).
2. User can execute his workflow
using the Expert Center tools
3. The workflow run correctly
reports success or eventual
failure in the workflow steps
Identifiers of
Functionality
Tested
tested
FMWK-VTS-15 Guidance about CORESYF-FMWK-EXPT-4 As a user I have an interest in using Co-ReSyF online platform 1. Document resources are
procedures, a particular tool, processing chain available, with a valid user with accessible online to support
processing chains or application and would like to access to the Expert Center users on a particular tool,
and tools read information about it processing chain or application
2. Collaborative tools are accessible
Document online to support users on a
Resources particular tool, processing chain
or application
Collaboration Tools
Identifiers of
Functionality
Tested
tested
FMWK-VTS-44 Quality feedback on CORESYF-FMWK-EXPT-5 As a user I want to be able to see Co-ReSyF online platform 1. The knowledge base links to
the available for a module that I am interested available, with a valid user with appropriate instructions in the
modules on what are the ratings given by access to the Expert Center SDK documentation pages and/or
the community on the quality of third-party sources
the results for that module List of the Co-ReSyF modules in 2. Users can provide ratings on the
scope quality of the results
3. Users can view ratings provided
by the community
Identifiers of
Functionality
Tested
tested
FMWK-VTS-45 Modules Essential CORESYF-FMWK-EXPT-6 As a user I want to be able to see Co-ReSyF online platform 1. The Expert Center links to
information the following information for each available, with a valid user with appropriate knowledge base
module in the platform: access to the Expert Center instructions for the SDK
(documentation pages and/or
1. What does the module do? List of the Co-ReSyF modules in third-party sources)
2. How does it do it? scope
3. What is the purpose of the
module?
4. Who made it?
5. Who should be credited?
6. How should the module be
used?
7. What is the underpinning
literature?
8. What is the peer-derived quality
ranking of the module?
9. What are the key topic areas
within which the module could be
applied?
Identifiers of
Functionality
Tested
tested
FMWK-VTS-46 Modules Additional CORESYF-FMWK-EXPT-7 As a user I want to be able to see Co-ReSyF online platform 1. The Expert Center links to
information the following information for each available, with a valid user with appropriate knowledge base
module in the platform: access to the Expert Center instructions for the SDK
(documentation pages and/or
1. report on sensor changes; List of the Co-ReSyF modules in third-party sources)
2. flag information; scope
3. processing steps and
processing implementation info;
4. quality control information,
including information on validation
efforts, and uncertainty
quantification;
5. any module DOI link for users to
deploy;
6. input data/module DOI links to
be incorporated;
7. information on funding
attribution.
Identifiers of
Functionality
Tested
tested
FMWK-VTS-47 Success Stories CORESYF-FMWK-EXPT-8 As a user I want to be able to see in Co-ReSyF online platform 1. Template for success stories
Dissemination the Knowledge Base some available, with a valid user with defined
examples of success stories, from access to the Expert Center 2. Success stories available online
people using the platform, so that I for Co-ReSyF users and the
get inspired to do my work on the general public
platform and have confidence in it.
Identifiers of
Functionality
Tested
tested
FMWK-VTS-48 Scientific CORESYF-FMWK-EXPT-9 As a user I want to have a board Co-ReSyF online platform 1. Scientific Whiteboard tool
Whiteboard where I can post some idea for a available, with a valid user with deployed online and configured
research activity, that everyone can access to the Expert center for the Co-ReSyF community
see and where others can propose 2. Examples available (e.g. as
to collaborate with me, in order to defined with the help of the Co-
find the suitable skills to carry out ReSyF partners and/or Advisory
the research activity. Board members)
- END OF EXPERT CENTER REQUIREMENTS -
5.3 Acceptance Test Procedures

The procedures for the Acceptance tests will be defined in the Verification and Validation Report
document according to the template presented in Annex I (Section 8).
Each acceptance test procedure will cover one or more test cases and their respective requirements,
and will have a unique ID.
Each step of the procedure will be numbered (so that it can be referenced in the VCM using the test
procedure ID with the step number). The possible results for a test step are either PASS or FAIL, no
other value is allowed. In the case that the step is verifying a requirement the Pass/Fail criteria will
need to be specified (this is mandatory) and will be used to assess the result of the step. On cases
where no P/F criteria is specified the result of the step is assessed by the ability to execute the step.
6 Verification Control Matrix

The results of the verification and validation activities shall be recorded in a Verification Control
Matrix, which the first version (including only the requirements and the traceability to the test case
ID where it is verified) is included below.
7 References
● Co-ReSyF. (2016a). GRANT AGREEMENT-687289. European Commission, Research Executive
Agency.
● Co-ReSyF (2016b). System Requirements Document – Framework, issue 1.0. European

Commission, Research Executive Agency.
● Deimos (2016a). VERIFICATION AND VALIDATION PROCEDURE, EDG-CMS-PRO16-E, Issue 2.0.

ELECNOR DEIMOS CORPORATE MANAGEMENT SYSTEM.
● Co-ReSyF (2016c). Project Management Plan, issue 1.0. European Commission, Research
Executive Agency.
● Deimos (2016b). NON-CONFORMANCE MANAGEMENT PROCEDURE, EDG-CMS-PRO12-E, Issue

3.0. ELECNOR DEIMOS CORPORATE MANAGEMENT SYSTEM.
8 Annex I : Template for the Test Procedures
TEST PROCEDURE
VTP Id.: Id of Associated VTS:
Functionality
to be Tested:
Required Test Environment:
Overview of the test procedure:
Detailed description of the test procedure, including how to observe and verify the results:
Step Description Result Requirement(s) P/F Criteria Comments

Nb. Verified
Date of execution:
END OF DOCUMENT

Attachment 0

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Attachment 0

Uploaded by

Copyright:

Available Formats

Ref.

Coastal Waters Research Synergy Framework

Verification and Validation Plan

Delivery milestone: CDR-2 meeting (T0+28)

Prepared by Hervé Caumont WP2 Leader

Reviewed by Nuno Grosso WP3 Leader

Approved by Miguel Terra-Homem Executive Board Chair

Signatures and approvals appear on original

Project start date: 01/01/2016

5.2 Acceptance Test Specifications 13

Table 5-1 : V1 Acceptance Tests Specifications 13

No table of figures entries found.

Acronyms and Abbreviations

1.1 Purpose and Scope

1.2 Document Structure

● Chapter 2 : describes the Verification approach.

2 SOFTWARE VERIFICATION PLAN

2.1 Software Verification Process Overview

2.1.2 Master Schedule

2.1.3 Techniques and Methods

2.1.4 Standards, Practices and Conventions

2.1.5 Resource Summary

2.2 Verification Activities

2.2.1 Software Validation Process Verification

2.2.2 Software Delivery and Acceptance Process Verification

2.3 Software Verification Reporting

3 SOFTWARE VALIDATION PLAN

3.1.2 Master Schedule

3.1.3 Techniques and Methods

3.1.4 Standards, Practices and Conventions

3.1.5 Resource Summary

3.2 Software Validation Test Facilities

3.3 Software Validation Test Reporting

4 GENERAL V&V ADMINISTRATIVE PROCEDURES

4.1 Anomaly Report and Resolution

4.2 Task Iteration Policy

4.3 Deviation Policy

4.4 Control Procedures

A test case is specified using the following fields:

5.2 Acceptance Test Specifications

Table 5-1 : V1 Acceptance Tests Specifications

- END OF CLOUD BACK-END REQUIREMENTS -

- END OF DATA API REQUIREMENTS -

- END OF “FRONT-END” REQUIREMENTS -

- END OF ORCHESTRATION MANAGER REQUIREMENTS -

- END OF EXPERT CENTER REQUIREMENTS -

5.3 Acceptance Test Procedures

6 Verification Control Matrix

● Co-ReSyF (2016b). System Requirements Document – Framework, issue 1.0. European

● Deimos (2016a). VERIFICATION AND VALIDATION PROCEDURE, EDG-CMS-PRO16-E, Issue 2.0.

● Deimos (2016b). NON-CONFORMANCE MANAGEMENT PROCEDURE, EDG-CMS-PRO12-E, Issue

8 Annex I : Template for the Test Procedures

VTP Id.: Id of Associated VTS:

Required Test Environment:

Overview of the test procedure:

Step Description Result Requirement(s) P/F Criteria Comments

You might also like