Patterns for configuration requirements of Software-as-a-Service

Authors:
Jaekeun Shim;Jongdae Han;Jindae Kim;Byungjeong Lee;Jaewon Oh;Chisu Wu
Affiliations:
Seoul National Univ.;Seoul National Univ.;Seoul National Univ.;The Univ. of Seoul;The Catholic Univ. of Korea;Seoul National Univ.
Venue:
Proceedings of the 2011 ACM Symposium on Applied Computing
Year:
2011

Citing 6
Cited 0

Design patterns: elements of reusable object-oriented software

Design patterns: elements of reusable object-oriented software
The Design and Implementation of a Framework for Configurable Software

ICCDS '96 Proceedings of the 3rd International Conference on Configurable Distributed Systems
Software as a Service: Configuration and Customization Perspectives

SERVICES-2 '08 Proceedings of the 2008 IEEE Congress on Services Part II
Configurability in SaaS (software as a service) applications

Proceedings of the 2nd India software engineering conference
Variability modeling to support customization and deployment of multi-tenant-aware Software as a Service applications

PESOS '09 Proceedings of the 2009 ICSE Workshop on Principles of Engineering Service Oriented Systems
A Multi-granularity Customization Relationship Model for SaaS

WISM '09 Proceedings of the 2009 International Conference on Web Information Systems and Mining

Quantified Score

Hi-index	0.00

Visualization

Abstract

Software-as-a-Service is becoming popular in the software business, due to its rapid delivery and cost effectiveness in development and maintenance. Software-as-a-Service should be provided in single code base and operated as a single instance. To meet these constraints and requirements from various customers, Software-as-a-Service must be highly configurable. To develop configurable Software-as-a-Service, it is important to elicit and analyze configuration requirements in the early stages of development. Another issue is that on implementing configuration requirements, there are duplicated and untidy code segments. In our study, configuration requirements are identified and classified. This study introduces design patterns to remove duplicated codes for configuration.