Realizing an MDA and SOA Marriage for the Development of Mobile Services

Abstract

Abstract. The paper presents an approach for developing composite telecommunication services running on mobile phones which takes advantage of the use of model driven techniques as well as the loose coupling paradigm in SOA. A domain-specific UML dialect named SPATEL has been developed which serves as the basis for generating applications that can be deployed in distinct terminals and servers technologies. The composite services typically combines telecommunication enablers -like SMS sending and GSM localisation -with traditional IT components accessible over the internet, such as a Yellow Page facility. This work has been conducted in the context of the IST SPICE European collaborative project.

Towards automated composition of convergent services: A survey

“…Telecom services are fundamentally different from Web services based on SOA or REST [17]. Next the most remarkable differences are analysed:…”

“…Several approaches have appeared to fully automate the composition of services available in the Web from both academia [9] [10] [11] [12] [13] [14] and industry [15] [16]. Similarly, some research has revolved around fully automation of communication service composition, coming mainly from European Projects [17] [18]. Considering the evolution of service composition in the Telecom and Web domains, we raise the first research question addressed in this paper: Which is the level of automation that has been achieved to date from previous service composition approaches ?.…”

Service Composition Quality Evaluation in SPICE Platform

“…This formalism, named SPATEL [6], meaning SPICE Advanced language for Telecommunication services, can essen-tially, be seen as a customization of the UML language for expressing the definition of service interfaces and service composition logic more suitable for the telecom domain. In contrast with most IT web services, telecom services are generally transactional, asynchronous, stateful and sometimes long-running processes, thus it is important to define constraints on the service interface such as the ordering of operation invocations.…”

“…In figure 3, an example of SPATEL notation for a composed service is shown, and more details on the graphical notation are described in [6]. …”

“…In the following section the architecture of SPICE SEE is described, followed by a description of the SPICE SCE which helps service developer in evaluating the quality of an orchestration of telecom-IT services taking into account non functional properties; the usage of such properties is then discussed in an overview section about SPATEL language [6]; finally the aggregation of both static and dynamic non-functional properties is discussed with an example, before drawing conclusions.…”