Synthesizing Components with Sessions from Collaboration-Oriented Service Specifications

Abstract

A fundamental problem in the area of service engineering is the so-called cross-cutting nature of services, i.e., that service behavior results from a collaboration of partial component behaviors. We present an approach for model-based service engineering, in which system component models are derived automatically from collaboration models. These are specifications of sub-services incorporating both the local behavior of the components and the necessary inter-component communication.The collaborations are expressed in a compact and self-contained way by UML collaborations and activities. The UML activities can express service compositions precisely, so that components may be derived automatically by means of a model transformation. In this paper, we focus on the important issue of how to coordinate and compose collaborations that are executed with several sessions at the same time. We introduce an extension to activities for session selection. Moreover, we explain how this composition is mapped onto the components and how it can be translated into executable code.

Performance Evaluation of Distributed System Using SPN

“…Hereby collaborations of Figure 2 are modeled by a call behavior action referring to the activity describing the behavior of the corresponding collaboration [10]. Activity diagram presents complete behavior in a quite compact form and may define connections to other behaviors via input and output pins [6].…”

Foraging for Better Deployment of Replicated Service Components

“…The updating function is modeled by four collaboration uses called update, each specifying the alignment of data between the two linked components. Although SPACE offers specification of multiple instances of a collaboration [8], for clarity only four instances of update are used here. SPACE models can be embellished with additional non-functional requirements that can be exploited by our deployment logic, i.e., the execution costs assigned to components or costs that are specific to each collaboration between replicas.…”

Using Composition Policies to Manage Authentication and Authorization Patterns and Services

“…From this example, we see that it is also important to describe constraints that must be satisfied or events that must occur in order to trigger the transition from the execution of one service collaboration to another. Our approach is different from [3,11] in its use of policies to govern service composition.…”

“…It has been shown in [3,11] that the ordering of collaborations can be described globally using UML2.1 activity diagrams in a way that enables realization problems to be detected and design components to be derived automatically. However, interactions between concurrent collaborations may need additional attention.…”