Deliverable D9.2: Specification of Pilot project applications and design of trials

Abstract

The classical waterfall software life cycle model with feedback loops was presented in deliverable D1.4, Project Quality Plan and Procedural Handbook as the guiding approach for software development activities in the SPIKE project. At the end of the design phase in this approach, the development of a system evaluation plan which has to be applied at system integration test phase is required The preceding deliverable D9.1 contained the common trial evaluation strategy. In this strategy The scope and the responsibilities for the evaluation plan definition and execution tasks were defined.

This deliverable, D9.2 consists of four detailed evaluation plans, one for each application case, which cover the whole functionality of the SPIKE platform, and one to combine all application cases into an integrated showcase. Each evaluation plan is enriched with developer’s and cross-testing partner annotations.

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.2. Specification of Pilot project applications and design of trials

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