Deliverable D9.4: D9.4 Evaluation of Trial 2 and specification for revision of the SPIKE system

Abstract

This deliverables presents the results from testing of the integrated software components in Trial 2 of the SPIKE system following the strategy and set-up defined in [D9.1] and [D9.2].Trial 2 has been organized in three independent application cases, each focusing on different aspects of the SPIKE components and operated by one of the SPIKE user partners. As a result of Trial 1 specifications of software components as well as semantic ontologies and process models have been modified and complemented. Finally, some changes to the trial evaluation procedure which are required by the changed testing environment and the chosen SPIKE approach are documented. 

The current report is the second document in a series of documents within WP 9 describing all the methodologies and evaluation activities on system integration level for software developed in the SPIKE project.

The evaluation methodology to be applied to evaluate SPIKE, the scope of the trials, and the responsibilities were outlined in deliverable [D9.1]. Deliverable 9.2 is now the “instantiation” of this methodology structured as an evaluation plan. In the requirements specification [D2.2] three application cases were defined by the consortium “user partners” which should cover the vision of SPIKE as a portal which enables the definition, setup, and management of “virtual organizations” (alliances) and offers generic functionality needed in a collaboration such as security mechanisms Identity federation mechanisms to enable cross-border access supported by state-of-the-art workflows)

Service oriented architectures and legacy applications (stand alone and integrated into encryption etc.) Additionally a fourth application case has been developed as a representative demo-case to show a practical and simply understandable example of SPIKE's potential. This fourth application case is the combination of parts of the first three application cases and is outlined in chapter 6.

Each identified application case is decomposed into its use-cases. A use case consists of tasks which form functional building-blocks for the evaluation. The evaluation methodology defines task scenarios as the basic elements to validate each task. A set of scenarios has to be chosen to evaluate all aspects of a task comprehensively. This is the “functional oriented” part of the evaluation which is based on expected (i.e. planned) results. These results are then compared to real measured evaluation results which will be collected during the two trials (described in two upcoming reports D9.3 and D9.4).

Additionally the SPIKE software is evaluated according to a list of quality criteria which aim to collect the general impression the testers acquired during the trial evaluation ranging from the look-and-feel to system responsiveness and many more. Deliverable D9.2 is a composition of different views such as those of the user partners, enriched by aspects brought in by the software engineers. It thereby guarantees an evaluation process of the SPIKE system which at the end should also allow for determining the maturity of the built prototype.

You can download a short version of this document here:

D9.4 Evaluation of Trial 2 and specification for revision of the SPIKE system

In order to obtain the full content of this document, please use the contact form below: