Variability Modeling for Customizable Saas Applications

Shahin, Ashraf A.

doi:10.5121/ijcsit.2014.6503

Cited by 5 publications

(3 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Additionally, a tenant's requirement changes often emerge after the applications and services are developed; therefore, the run-time customization scoped to a specific tenant has to be supported within the same application instance [7], [8], [19], [20], and it does not affect tenant isolation and application availability [7], [19], [20]. Typically, SaaS applications lack the extensibility of licensed products [6].…”

Section: Motivationmentioning

confidence: 99%

A Systematic Mapping Study on the Customization Solutions of Software as a Service Applications

et al. 2019

View full text Add to dashboard Cite

Software as a Service (SaaS) is widely used and depended on by a wide range of applications. Considering this, the SaaS should capacitate itself to offer service to a large number of customers having their own specific requirements, without encountering software quality problems. Therefore, several researchers delved into the SaaS customization, and many customization solutions have been proposed. However, heretofore, no analysis or study explicitly classifies these proposals using different criteria, e.g., the kind of change required, the component of the software requiring changes, and the quality attributes of the SaaS considered in each proposed solution. This paper adopts the systematic mapping approach to methodically investigate the solutions recommended for the SaaS customization problems. These solutions are classified into various categories to create a classification scheme based on the customization types (personalization, configuration, composition, modification, integration, and extension), customization layer (user interfaces, workflows, services, and data), and quality attributes. Our study identified 81 primary studies reporting SaaS customization solutions. The results show that the configuration, composition, and extension received the highest consideration in the proposed solutions. In addition, the majority of the proposed solutions for the SaaS customization are connected with the workflow and service layers. Furthermore, the attributes, such as multi-tenancy, security, functionality, scalability, availability, and efficiency, are considered much more often than other attributes. The classification of the proposed solutions for the SaaS customization and results of this paper can play an important role in creating a framework for the SaaS customization assessment.

show abstract

Section: Motivationmentioning

confidence: 99%

A Systematic Mapping Study on the Customization Solutions of Software as a Service Applications

et al. 2019

View full text Add to dashboard Cite

show abstract

“…Most of current SaaS applications have been developed using service-oriented architecture (SOA) model [1]. In SOA model, each application is a collection of services that are organized in several layers.…”

Section: Introductionmentioning

confidence: 99%

“…SaaS is a software delivery model in which software is delivered to customers as a service [1]. Instead of delivering individual application instance for each tenant, one application instance serves thousands of tenants [2].…”

Section: Introductionmentioning

confidence: 99%

Enhancing Elasticity of SaaS Applications using Queuing Theory

Shahin¹

2017

ijacsa

View full text Add to dashboard Cite

Abstract-Elasticity is one of key features of cloud computing. Elasticity allows Software as a Service (SaaS) applications' provider to reduce cost of running applications. In large SaaS applications that are developed using service-oriented architecture model, each service is deployed in a separated virtual machine and may use one or more services to complete its task. Although, scaling service independently from its required services propagates scaling problem to other services, most of current elasticity approaches do not consider functional dependencies between services, which increases the probability of violating service level agreement. In this paper, architecture of SaaS application is modeled as multi-class M/M/m processor sharing queuing model with deadline to take into account functional dependencies between services during estimating required scaling resources. Experimental results show effectiveness of the proposed model in estimating required resources during scaling virtual resources.

show abstract