2009 IEEE International Conference on Cloud Computing 2009
DOI: 10.1109/cloud.2009.69
|View full text |Cite
|
Sign up to set email alerts
|

A Method to Support Variability of Enterprise Services on the Cloud

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
3
0

Year Published

2010
2010
2022
2022

Publication Types

Select...
5
1
1

Relationship

0
7

Authors

Journals

citations
Cited by 14 publications
(4 citation statements)
references
References 19 publications
0
3
0
Order By: Relevance
“…• The business-process layer (services orchestration and composition): The approaches proposed [15], [6], [8] try mainly to extend the business-process execution language (BPEL) [12] in order to support its run-time adaptation, especially that BPEL is recognized as a standard in the web services world. • The service layer (functional layer represented as a set of invoked services): The approaches proposed [10], [22], [13] provide different adaptation mechanisms and patterns, making these individual (atomic) services more reusable in different run-time context. • The interface layer (intermediate layer between business-processes and services): The approaches proposed [20], [14] try mainly to identify the conflict problems and the services interfaces mismatch at their input and output types, which is generally produced after a dynamic services replacement at the businessprocess layer.…”
Section: Background and Problemmentioning
confidence: 99%
“…• The business-process layer (services orchestration and composition): The approaches proposed [15], [6], [8] try mainly to extend the business-process execution language (BPEL) [12] in order to support its run-time adaptation, especially that BPEL is recognized as a standard in the web services world. • The service layer (functional layer represented as a set of invoked services): The approaches proposed [10], [22], [13] provide different adaptation mechanisms and patterns, making these individual (atomic) services more reusable in different run-time context. • The interface layer (intermediate layer between business-processes and services): The approaches proposed [20], [14] try mainly to identify the conflict problems and the services interfaces mismatch at their input and output types, which is generally produced after a dynamic services replacement at the businessprocess layer.…”
Section: Background and Problemmentioning
confidence: 99%
“…It can occur in number of states like in design, compilation of software, linking to other software, and runtime. Variability concerns affect both the service interface and the service provider implementation and hence are crosscutting in nature [14]. Multi-tenancy demand to customizing the single instance according variability wishes among many customers [1].…”
Section: Introductionmentioning
confidence: 99%
“…Software as a Service (SaaS) applications are cloud-based applications that are mostly service-oriented, and are provisioned to different customers (they are multi-tenant). Since a SaaS provider provides a family of applications with many commonalities, service-oriented product lines are considered a proper solution for SaaS applications [4] [5] [6].…”
Section: Introduction To the Problemmentioning
confidence: 99%