Service Engineering
|
| v1 - Summary
The focus of this state-of-the-art report is on two critical issues for service developers and providers: (i) Specification: how can services be described so that potential users can make decisions on whether or not these services meet their needs? (ii) Verification: how can the provider convince themselves and potential consumers of the service that the service meets its specification? |
|
| v1 - Summary
This document presents the first version of the SeCSE Service Specifications Structure. It proposes a flexible XML structure that is capable of accommodating changing and emerging standards and the maturing needs of SeCSE users. |
| v2 - Summary
This version refers to the document “A1.D2.2 - Specification language definition, v2″ that discusses the notion of facets on a conceptual level, before providing an instantiation that is to be used within SeCSE. A set of default facets is identified and an XML based specification structure for each is proposed. Examples are provided to illustrate how they would be used. |
| v3 - Summary
This version refers to the document “A1.D2.3 - Specification language definition, final” that presents the latest version of the service description based on facets approach. |
|
| v1 - Summary
This document presents the first version of the testing methods definition adopted in SeCSE and the impact of this in service centric applications |
| v2 - Summary
This version refer to the document A1.D3.2 - Testing method definition, v2 and a summary of this prototype version can be found at this link |
| v3 - Summary
This version refers to the document A1.D3.3 - Testing method definition, v3. The diffusion of service oriented architectures introduces the need for novel testing approaches. On the one side, testing must be able to identify failures in the functionality provided by service. On the other side, it needs to identify cases in which the Service Level Agreement (SLA) negotiated between the service provider and the service consumer is not met. This would allow the developer to improve service performances, where needed, and the provider to avoid promising Quality of Service (QoS) levels that cannot be guaranteed. Our approach proposes the use of Genetic Algorithms to generate inputs for service-oriented systems that cause SLA violations. |
| v4 - Summary
The diffusion of service oriented architectures introduces the need for novel testing approaches. On the one side, testing must be able to identify failures in the functionality provided by service. On the other side, it needs to identify cases in which the Service Level Agreement (SLA) negotiated between the service provider and the service consumer is not met. This would allow the developer to improve service performances, where needed, and the provider to avoid promising Quality of Service (QoS) levels that cannot be guaranteed. |
...more: »