Advertisement

A General Maturity Model and Reference Architecture for SaaS Service

  • Seungseok Kang
  • Jaeseok Myung
  • Jongheum Yeon
  • Seong-wook Ha
  • Taehyung Cho
  • Ji-man Chung
  • Sang-goo Lee
Part of the Lecture Notes in Computer Science book series (LNCS, volume 5982)

Abstract

In today’s dynamic IT environment with increased global competition, enterprises must achieve greater business agility and decrease the TCO (Total Cost of Ownership) of their system for service. As the need for innovative software circulation process emerges, SaaS (Software as a Service) is introduced for integrating software service framework. But most of current ASP (Application Service Provider) Players have difficulties to migrate their systems to SaaS Platform for the lack of maturity model and process. In this paper, we have surveyed several cases of SaaS service, and we identified the common key functions of SaaS service. We contend that the practical maturity model is a key enabler for achieving migration to innovative SaaS service platform. To assist in building our SaaS maturity model, we defined two important axes of maturity model and introduced the detailed components of each phase with the reference architecture which contains the essential activities according to the common functions of SaaS service.

Keywords

SaaS Service ASP Maturity Model Software Business 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Upadhyay, S.: Software as a Service (SaaS). Oracle (2008)Google Scholar
  2. 2.
    Chong, F., Carraro, G.: Architecture Strategies for Catching the Long Tail, MSDN Library. Microsoft Corporation (2006)Google Scholar
  3. 3.
    Ried, S., Rymer, J.R., Iqbal, R.: Forrester’s SaaS Maturity Model. Forrester Research (2008)Google Scholar
  4. 4.
    Ma, D.: The Business Model of Software-As-A-Service. In: IEEE International Conference on Services Computing (SCC 2007), pp. 701–702 (2007)Google Scholar
  5. 5.
    Waters, B.: Software as a service: A look at the customer benefits. Journal of Digital Asset Management 1(1), 32–39 (2005)CrossRefGoogle Scholar
  6. 6.
    Xin, M., Levina, N.: Software-as-a-Service Model: Elaborating Client-Side Adoption Factors. In: 29th International Conference on Information Systems, Paris, France (2008)Google Scholar
  7. 7.
    Sääksjärvi, M., et al.: Evaluating the Software as a Service Business Model: From CPU Time-Sharing to Online Innovation Sharing. In: IADIS International Conference e-Society, Qawra, Malta, pp. 177–186 (2005)Google Scholar
  8. 8.
    Choudhary, V.: Software as a Service: Implications for Investment in Software Development. In: 40th Annual Hawaii International Conference on System Sciences, HICSS 2007 (2007)Google Scholar
  9. 9.
    Greschler, D., Mangan, T.: Networking lessons in delivering ‘Software as a Service’ - part I. International Journal of Network Management 12(5), 317–321 (2007)CrossRefGoogle Scholar
  10. 10.
    Guo, C.J., et al.: A Framework for Native Multi-Tenancy Application Development and Management. In: 9th IEEE International Conference on E-Commerce Technology and (CEC 2007), Tokyo, Japan (2007)Google Scholar
  11. 11.
    Chou, D.C., et al.: Analysis of a new information systems outsourcing practice: software-as-a-service business model. International Journal of Information Systems and Change Management 2(4), 392–405 (2007)CrossRefGoogle Scholar
  12. 12.
    Goth, G.: Software-as-a-Service: The Spark That Will Change Software Engineering? IEEE Distributed Systems Online 9(7), Art.No. 0807-o7003 (2008)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2010

Authors and Affiliations

  • Seungseok Kang
    • 1
  • Jaeseok Myung
    • 1
  • Jongheum Yeon
    • 1
  • Seong-wook Ha
    • 2
  • Taehyung Cho
    • 2
  • Ji-man Chung
    • 2
  • Sang-goo Lee
    • 1
  1. 1.Department of Computer Science and EngineeringSeoul National Univ.SeoulKorea
  2. 2.Q.N.SOLV CorporationSeoulKorea

Personalised recommendations