CHOReOS was an FP7 project. It is now fully completed. This website is kept open for information purpose only, it is not updated. Please visit CHOReVOLUTION the project that takes over from CHOReOS.
choreos.eu: The Governance and V&V Framework (Documentation.The_Governance_and_Verification_and_Validation_Framework)

The Governance and V&V Framework

The Governance and V&V Framework provides strategies and tools required for governance, testing and monitoring
for both services and choreographies.

The overall logic architecture of the abstract components that the Governance and V&V Framework defines,
are dealing with the different stages of a choreography lifecycle to which they apply.
In particular, the components belong to three main categories and are accordingly packaged into three main subsystems:

  •  the package Development-time V&V infrastructure collects the components devoted to support
    the testing activities in an off-line setting at design time;
  • the package Run-time Governance and V&V infrastructure collects the components supporting
    the extension of the verification phase along run-time activities. Run-time V&V is pursued both
    through testing and monitoring, and can concern both functional and non-functional aspects. We
    remark that we distinguish between on-line testing, that actively launches test cases and observes
    outcomes, from monitoring, that passively observes how the services spontaneously interact;
  • the package V&V Enabling Components collects those components implementing methods and
    notations that support the above activities, including test case generation and non-functional re-
    quirements specification.

generaloverview-3.png
The Governance and V&V Framework : Overall Logical View

Targeted audience

  • Choreography Designers: people or organizations which are responsible for managing
    the life-cycle of the choreographt specification. As consequence they
    would like to have :
    • means for express requirements, and goals about the QoS
      of the choreographies they are engineering;
    • means for validating offline both the functional, and non-functional propoerties
      exposed by the modeled choreographies;
    • have a place to make the specification they define publicly available.
  • Choreography Governing Boards : organizations establishng and maintaining the policies and
    rules for all the activities related to the choreography and
    service life-cycles. It would benefit from:
    • an infrastructure able to set governance properties and metadata,
      both services and choreghraphies while manageing both services and choreographies;
    • means for monitoring, planning reallocation of resources, turning off some services, or kicking an
      actor and replacing him/her with a different service provider.
    • the continuos check that services behave according to what
      is specified in the choreography; so that, in case misbehaving
      services are detected, they will be put in a place for
      suitable countermeasures;
  • Choreography Users : people or organizations which are mainly interested
    in reaching a goal by using a set of cooperating services. They would
    refer to the feature offered by this framework for :
    • browse and retrive choreography also with respect to non-functional properties coded in SLAs,
      or ranking information from both objective/subjective mesuraments
    • browse and retrive services by their role in choreographies also with respect to non-functional properties coded in SLAs,
      or ranking information from both objective/subjective mesuraments
  • Service Providers : are people or organization that intend to reach their business objective through the provisioning of a service to third parties. Usually, these services are perceived as more valuable if they are able to play a role within one or more choreographies. As consequence, service providers would benefit from:
    • means for express requirements, and goals about the QoS
      of the services they are engineering;
    • means for validating offline both the functional, and non-functional propoerties
      exposed by their services;
    • the continuos check that services behave according to what
      is specified in the choreography; so that, in case misbehaving
      services are detected, they will be put in a place for
      suitable countermeasures;

Detailed Components

Run-time Governance and V&V Infrastructure

Development-time V&V infrastructure

V&V Enabling Components

  • Choerography Testing Strategies
  • QoS Choreography Properties Specification

Contacts


This wiki is licensed under a Creative Commons 2.0 license - Legal Notice
XWiki Enterprise 5.4.6 - Documentation
Site maintained by