Skip to main navigation Skip to search Skip to main content

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

  • Jaekeun Shim
  • , Jongdae Han
  • , Jindae Kim
  • , Byungjeong Lee
  • , Jaewon Oh
  • , Chisu Wu
  • Seoul National University
  • The Catholic University of Korea

Research output: Chapter in Book/Report/Conference proceeding › Conference contribution › peer-review

5 Scopus citations

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.

Original languageEnglish
Title of host publication26th Annual ACM Symposium on Applied Computing, SAC 2011
PublisherAssociation for Computing Machinery
Pages155-161
Number of pages7
ISBN (Print)9781450301138
DOIs
StatePublished - 2011
Event26th Annual ACM Symposium on Applied Computing, SAC 2011 - TaiChung, Taiwan, Province of China
Duration: 21 Mar 2011 → 24 Mar 2011

Publication series

NameProceedings of the ACM Symposium on Applied Computing

Conference

Conference26th Annual ACM Symposium on Applied Computing, SAC 2011
Country/TerritoryTaiwan, Province of China
CityTaiChung
Period21/03/11 → 24/03/11

Keywords

  • SaaS
  • configuration
  • configuration requirements
  • design pattern

Fingerprint

Dive into the research topics of 'Patterns for configuration requirements of Software-as-a-Service'. Together they form a unique fingerprint.

Cite this