COSMO: A conceptual framework for service modelling and refinement

Abstract

This paper presents a conceptual framework for service modelling and refinement, called the COSMO (COnceptual Service MOdelling) framework. This framework provides concepts to model and reason about services, and to support operations, such as composition and discovery, which are performed on them at design and run-time. In particular, the framework should facilitate the use of different service description languages tailored to different service aspects, such as the behaviour of a service and the information it manipulates, or design tasks, such as modelling, analysis and implementation. The idea is that models produced by these languages can be mapped onto the concepts of the framework, thereby facilitating one to relate these models, e.g., to verify consistency. Therefore, a requirement on the framework is to provide concepts that capture all elementary and generic service properties that are relevant during the service development process. We capture these properties by analysing existing service definitions and from earlier experience. Furthermore, we want the same concepts to be applicable throughout the service development process when modelling and refining services at successive abstraction levels. The framework distinguishes three generic abstraction levels, and describes an approach to assess the conformance between the service models produced at these abstraction levels.

Interaction Patterns for Refining Behaviour Specifications of Context-Aware Mobile Services

“…Particularly, A-MUSE DSL is a specialization of ISDL and both languages are based on the COSMO framework [23], which is a framework used in the A-MUSE project as a conceptual basis for modelling services. By using A-MUSE DSL and ISDL we can support a broad spectrum of abstraction levels, from the highest level of abstraction of our approach, namely the service specification level, to the lowest level of platform-independence, namely the service design level.…”

Foundational MDA Patterns for Service-Oriented Computing .

“…In this regard it has more in common with COSMO [Qea07] and Service Component Architecture (SCA) [Edw14]. The big difference between these approaches and the approach presented in this article is that they do not explicitly distinguish between client-developer and service-provider views of service-oriented systems.…”

Towards a Commitment-Based Reference Ontology for Services

“…For example, Quartel et al [1] propose that at a high-level of abstraction, a service can be considered as a single interaction between a "service user" and a "provider". They further propose that at a lower level of abstraction, a service can be regarded as "as multiple related interactions between a service user and provider."…”

“…Several authors from different disciplines have attempted to define this notion under various perspectives, leading to a variety of characterizations for "services", each emphasizing different aspects. For example, the service as interaction perspective focuses on the interactions among service participants to achieve results or generate effects [1]; service as value cocreation focuses on services as the basis of economic exchange [2][3] [4]; service as capability focuses on the capability of a provider to produce benefits to customers (e.g., [5] [6]); service as application of competences focuses on the manifestation of the capability of one party to act in benefit of another party [2]; finally, service as software focuses on pieces of software that can be accessed through well-defined interfaces [7].…”