Policy Driven Services Coordination for Building Social Networks Based Applications

Abstract

Work-in-Progress Track: Services CoordinationInternational audienceThis paper presents an approach for observing and reacting on the execution of services' coordinations in order to ensure NFP policies specified by the coordination designer. Thanks to policies associated to a services based application running in a Web dynamic environment, it is possible to associate a personalized behaviour: atomic integration of information retrieved from different social network services, automatic generation of an integrated view of the operations executed in different social networks

Supporting Non-functional Requirements in Services Software Development Process: An MDD Approach

“…The π-ServiceProcess meta-model gathers the constraints described in the π-UseCase model into contracts that are associated with services. The π-ServiceComposition meta-model provides the concept of Policy [11] which put together contracts with similar non-functional requirements. For instance, security and privacy restrictions may be grouped into a security policy.…”

Reliable Web Services Composition: An MDD Approach

“…We model non-functional constraints of services' compositions using the notion of A-policy [9], [13], a kind of pattern for specifying A-policy types. In order to represent constraints associated to services compositions, we extended the SOD-M services' composition model with two concepts: RULE and A-POLICY (see blue elements in the π-SCM meta-model in Figure 3).…”

“…If rules belonging to several policies are triggered then policies are also ordered according to an execution plan. The execution of policies is out of the scope of this paper, the interested reader can refer to [9] for further details.…”

“…This work (i) proposes to extend the SOD-M [6] method with the notion of A-Policy [9] for representing non-functional constraints associated to services' based applications; (ii) defines the π-PEWS meta-model providing guidelines for expressing the composition and the A-policies; and finally, (iii) defines model to model transformation rules for generating the π-PEWS model of a reliable services' composition starting from the extended services' composition model; and, model to text transformations for generating the corresponding implementation. As will be shown within our environment implementing these meta models and rules, one may represent both systems' cross-cutting aspects (e.g., exception handling for describing what to do when a service is not available, recovery, persistence aspects) and constraints associated to services, that must be respected for using them (e.g., the fact that a service requires an authentication protocol for executing a method).…”