2012 International Conference on Green and Ubiquitous Technology 2012
DOI: 10.1109/gut.2012.6344158
|View full text |Cite
|
Sign up to set email alerts
|

Variable service process by feature meta-model for SaaS application

Abstract: We observed SaaS developed application by multitenancy to provide flexible customization and introduced many issues in software scalability and dynamic testing. Multitenancy demand to customizing the single instance according variability wishes among many customers. For that we proposed variable service process to customization multitenancy in runtime. It will be realize all benefits of variability concept for SaaS application. And proposed Feature metamodel to implement graphical editor and define all rules a… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

2019
2019
2020
2020

Publication Types

Select...
2

Relationship

0
2

Authors

Journals

citations
Cited by 2 publications
(3 citation statements)
references
References 10 publications
0
3
0
Order By: Relevance
“…SaaS application can be extended by adding custom code to be compiled during runtime (Saleh, Fouad & Abu-Elkheir, 2014;Correia, Penha & Da Cruz, 2013). Furthermore, a set of extension points, which permit a customized service to be plugged in, must be provided Correia, Penha & Da Cruz, 2013;Moens & De Turck, 2014;Salih & Zang, 2012). The SaaS provider should also supply an open platform and an API, which allows developers to compile custom code (replacements for existing objects or extensions to them) into the business object layers of the application (Zhao et al, 2014;Müller et al, 2009).…”
Section: Extension Approachmentioning
confidence: 99%
See 1 more Smart Citation
“…SaaS application can be extended by adding custom code to be compiled during runtime (Saleh, Fouad & Abu-Elkheir, 2014;Correia, Penha & Da Cruz, 2013). Furthermore, a set of extension points, which permit a customized service to be plugged in, must be provided Correia, Penha & Da Cruz, 2013;Moens & De Turck, 2014;Salih & Zang, 2012). The SaaS provider should also supply an open platform and an API, which allows developers to compile custom code (replacements for existing objects or extensions to them) into the business object layers of the application (Zhao et al, 2014;Müller et al, 2009).…”
Section: Extension Approachmentioning
confidence: 99%
“…Ext 1 Custom code insertion Saleh, Fouad & Abu-Elkheir (2014), , Correia, Penha & Da Cruz (2013) Ext 2 Extension points , Correia, Penha & Da Cruz (2013) Ext 3 Runtime extension Moens & De Turck (2014), Salih & Zang (2012) Ext 4 Extension interface Zhao et al (2014), Müller et al (2009) Ext 5 Replacements of existing code Müller et al (2009) Ext 6 Private/public extension Aulbach et al 2011Integration approach…”
Section: Customization Practice Referencesmentioning
confidence: 99%
“…The ultimate goal of SaaS application vendors is the provision of an easy to use, fully coordinated option. However, the management of highly complex software that may entail extremely complicated adaptations may go beyond the capacity of delivery model in a multi-tenancy setting [11].…”
Section: Introductionmentioning
confidence: 99%