Topics of Interest
- Abstract service models – current service description languages are only up to the task of describing the service interface; what is needed are abstract models to describe the complete behaviour and performance of services, such that model-translation algorithms can generate equivalent services on different platforms.
- Model-driven generation – current software services are designed in vendor-specific ways that prevent them being ported onto different platforms; what is needed are sets of translation algorithms for converting abstract service models into platform-specific applications, or sets of equivalent applications deployed across multi-clouds.
- Service behaviour certification – current quality control is mostly achieved by in-house developer-based testing; what is needed is a means of determining whether alternative services are equivalent, certified by generating standard test sets from functional specifications of services, and grounding these for each of the service protocol technologies described above.
- Service performance monitoring – current service monitoring technology is limited to SLAs for response-times and availability of end-points; what is needed is a more sophisticated data fusion approach, such as complex event processing, with trend prediction, supporting service optimisation and substitution.
- Service optimization – current service platforms offer single-vendor services with failover substitution, or manual selection from several providers; what is needed is a means of offering multi-vendor services on a competitive basis, with automatic arbitrage between different providers, to support constrained optimization of cloud performance.
- Service governance – current services and platforms are developed following in-house software processes; what is needed are explicit standards and methods for governing the whole service lifecycle, ensuring common quality standards and interfaces, supporting convergent service development and service customisation.
This list is not exhaustive; other topics relevant to the Consumer, Provider and Broker roles (NIST definitions) will be considered. Please note that service security is out of scope, being a matter for the Auditor role. Please note also that only design-time adaptation will be considered, since another ESOCC workshop will be devoted to run-time adaptation issues.
We solicit original, previously unpublished papers of two kinds: research papers (12 sides LNCS), or short vision/position papers (6 sides LNCS). Formatting guidelines are according to the Springer LNCS Formatting Guide.
Submission will be via EasyChair, using the link given below. Every paper will receive at least three reviews. It is anticipated that papers will be published in the Springer CCIS series.
EasyChair submission site: https://www.easychair.org/conferences/?conf=csb2014
Accepted papers: Please use the EasyChair submission site above, which has now been enabled for authors of accepted papers to upload revised versions of the papers. The revised page limits for improved and corrected papers are:
- 15 sides LNCS (full research papers)
- 8 sides LNCS (short vision papers)
At least one presenter must register for the workshop, for each accepted paper (see Registration). The ESOCC organisers expect the presenting author to register before the early bird registration deadline, 25 July 2014.
Full Call for Papers
For your convenience, please find the full text of the call for papers below, in PDF and TXT formats: