|Service Oriented Architecture|
Lightweight, Context-aware BMP Language
SOA4All concentrates on bringing IT solutions to non-technical users. In the context of lightweight process modelling a new, easy to manage modelling language is required since existing languages are too complex for non-technical users.
Design-time Adaptation and Composition
Business processes in service-oriented environments are being automated and executed by services. These services must be adapted to particular needs in a particular context; and hence configured on a per case basis. Furthermore, various independent services have to be interlinked and composed in order to satisfy the various global process business goals. The adaptation, and even worse the composition of services is a hard problem, particularly when moving towards the heterogeneous, unreliable and open Web. Moreover, composite services are likely to be much more multifaceted, as serially executable services, or have to be re-configured and adapted for various specific uses at a higher level of complexity.
Run-time Adaptation and Composition
In the context of services, the idea of being able to self-manage is very important due to the high dynamics of business relationships and to the continuous evolution of end users expectations and needs. In particular systems that are created by composing services offered by third parties do not have any control on the way the component services are actually offered, therefore, they should be equipped with some self-management capability that would allow them to react to the cases in which these services provide incorrect results or are unresponsive.
Systems can self-adapt before execution to account for the first issue or at runtime to tackle environmental changes and unforeseen faults. In both cases the system has to be designed to be ready for self-adaptation.
Research about service oriented architectures produced, in the last years, some frameworks that enable the development of self-adaptive service compositions supporting dynamic binding (a developer can specify, at design time, an abstract service; at run time a concrete implementation of the abstract service is dynamically selected). SOA4All will futher analyze the problem of runtime adaptation and composition giving especial importance to those aspects that depend on contextual information that can be only acquired during the execution of a service composition(e.g. time and location, user profile, device, usage conditions). SOA4All will develop a context-aware execution infrastructure able to execute those complex services that will be adaptive to environmental changes; and flexible enough to allow its context-dependent self-reconfiguration.