A Model-driven Approach to Service Policies.

Abstract

A Service represents an underlying capability offered by a service provider. A service description describes two facets of a service -the service functionality (capability onoffer) and the terms at which the service is offered (terms of offer). The capability onoffer satisfies the goal of a service consumer under the constraints of the terms of offer. Service Policies are used to define the terms of offer of a service offering. Policies could potentially apply to service-level, domain-level or technical (infrastructural) aspects. In this paper, we present a systematic model-driven development approach to deal with service policies from the perspective of a service provider. Our approach addresses the entire development spectrum of service policies. It addresses definition of service policies using visual models and attaching these policy models to service capability description models. It also addresses transforming these policy models to executable specifications and finally enforcing these policies during service invocation.

Model-Driven Development of a Web Service-Oriented Architecture and Security Policies

“…Along the same line is the proposal by Jegadeesan and Balasubramaniam [3]. Their model driven development approach is very similar to Ortiz's, dividing aspects in three levéis: service, business, and domain aspects.…”

“…[2], [3], [4]). However, these approaches do not offer thorough support for access control descriptors, code generation, Web Services Descnption Language (WSDL) [5], and WS-Pohcy [6].…”

“…It was necessary to implement it from scratch, as the metamodel obtained from the specification schema was not usable in an editor, and that all other previously existent WSPolicy metamodels (e.g., [3]), do not allow for the use of both "compact" and "normal" WS-Policy mode, as intended.…”