Information Technology Reference
In-Depth Information
The System administrator is the only DC Profile that can use the second
ontology.
This is used during the upgrade procedure.
20.5.2 Testbed Checks
20.5.2.1 Introduction
The ESA testbed is divided into three logical phases:
•
CASPAR system setup - configuration, modules creation, profile creation;
•
Access, Ingestion and browsing;
•
Software processing preservation - update procedure.
The third part - Software processing preservation - is the testbed focus.
This is the reason for which - while the system setup, the ingestion, the search
and retrieve parts of the scenario are validated by performing and then analyzing
(and evaluating of) the correct implementation of CASPAR functionalities (e.g. pro-
file creation, data ingestion, search and retrieval, Representation Information, etc.)
- the update procedure needed a more specific validation methodology. The present
chapter focuses on the testbed checks performed on the Update Procedure.
20.5.2.2 Purpose
Update procedure validation activities have been carried out in order to demonstrate
two main scenarios:
1.
Library change
: an object external to the system currently needed by the
processor is out of date due to the release of a new version (e.g. a new library).
2.
OS Change
: the processor needs to be run on a new Operating System
In both cases the scenario purpose is to preserve the ability to process a Level 1B
product generating a Level 1C. In case of a change the following functionalities
have to be granted:
•
Allow the CASPAR user to notify an alert concerning the processor;
•
Help the System Administrator to create, test and validate, upload and install a
new processor version;
•
Link the new processor version to the previous ones;
•
Notify all users about the change.
20.5.2.3 Environment
The following table reports the testbed validation procedure pre-conditions.
