D5.1.1: Description of the validation scenario scenarios and identification of common elements

This deliverable is the first release of a series of three deliverables, aimed at describing and prototyping the usage patterns and example applications (Task T5.1). This first document describes the validation methodology that will be implemented by the validation scenarios. In order to avoid the definition of non-useful validation scenarios and to measure the coverage of the defined ones, some key features are defined as sensitive aspects of the SPECS framework. Furthermore, four user stories are defined to provide general containers of the validation scenarios. The coverage of the defined scenarios has been measured according to some Key Concerns: SLA lifecycle, SPECS users, invocation chains, and target services. Another important Key Concern is the set of the requirements of the SPECS platform as well as the three modules (Enforcement, Negotiation and Monitoring).
Task T5.1spans over the first two years of the project; hence, the deliverable focuses on the definition of the methodology and on the detection of some first validation scenarios. The methodology defined in this document can be considered quite stable: it would be revised according to the changes that could be brought on SPECS. Validation scenarios will be improved by creating new scenarios and by adding implementation details such as the knowledge of the SPECS framework grows and the development of SPECS components enters in the design and implementation phases.
The document also introduces the concept of User Story as a general container and collector of different uses of SPECS related to a single use case and End-User community. This deliverable also addressed a mapping among the user stories here defined, ones described in project documents (DOW) and others used in other WP to gather and elicit requirements.
The next iteration of this deliverable (D5.1.2) will include the coverage of the requirements about negotiation, monitoring and enforcement. Moreover, the next release of this deliverable will also better span validation scenarios on the four defined user stories.
Finally, this deliverable deals with the problem of addressing the choice of the Validation Scenarios which will be actually implemented in the second year of the project. This subset of VSs is chosen according to a prioritization of the SPECS requirements gathered by interacting with End-User communities and industrial partners. According to this prioritization, it is possible to choose the scenarios that will drive the implementation of prototypal applications.
Moreover, the deliverable will also show how the chosen VSs will also be capable of covering as much SPECS requirements as possible. In particular, coverage of more than 70% of the requirements is addressed in this document.