Nothing Special   »   [go: up one dir, main page]

Skip to main content

Parameters for Service Level Agreements Generation in Cloud Computing

A Client-Centric Vision

  • Conference paper
Advances in Conceptual Modeling (ER 2012)

Part of the book series: Lecture Notes in Computer Science ((LNISA,volume 7518))

Included in the following conference series:

Abstract

Current Service Level Agreements are lacking completeness. They often leave out parameters that are important for the consumer. In addition, SLAs are predefined by the service providers and the consumer does not have a say in them. The goal of this paper is to find the important parameters that should initially be included in a Service Level Agreement between a cloud service provider and a cloud service consumer. In this paper we are showing a client-centric view of the SLA. Some examples for SLAs of services in the market are illustrated, in order to show the need to specify, which parameters should be included in the SLAs.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Subscribe and save

Springer+ Basic
$34.99 /Month
  • Get 10 units per month
  • Download Article/Chapter or eBook
  • 1 Unit = 1 Article or 1 Chapter
  • Cancel anytime
Subscribe now

Buy Now

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 39.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Similar content being viewed by others

References

  1. ISO/IEC 9126. Software engineering, Product quality -Part 1: Quality model

    Google Scholar 

  2. Armbrust, M., Fox, A., Griffith, R., Joseph, A.D., Katz, R.H., Konwinski, A., Lee, G., Patterson, D.A., Rabkin, A., Stoica, I., Zaharia, M.: Above the clouds: A berkeley view of cloud computing. Technical report (2009)

    Google Scholar 

  3. Becha, H., Amyot, D.: Non-Functional Properties in Service Oriented Architecture A Consumer’s Perspective (2011)

    Google Scholar 

  4. Bergholtz, M., Andersson, B., Johannesson, P.: Abstraction, Restriction, and Co-creation: Three Perspectives on Services. In: Trujillo, J., Dobbie, G., Kangassalo, H., Hartmann, S., Kirchberg, M., Rossi, M., Reinhartz-Berger, I., Zimányi, E., Frasincar, F. (eds.) ER 2010. LNCS, vol. 6413, pp. 107–116. Springer, Heidelberg (2010)

    Chapter  Google Scholar 

  5. Botella, P., Burgues, X., Franch, X., Huerta, M., Salazar, G.: Modelling Non-Functional Requirements. In: Proc. of Jornadas Ingeniera de Requisitos Aplicados, JIRA (2001)

    Google Scholar 

  6. Brownsword, L., Carney, D., Fisher, D., Lewis, G., Meyers, C., Morris, E.J., Place, R.H.: Current perspectives on interoperability. Technical report, Carnegie Mellon Software Engineering Institute (2004)

    Google Scholar 

  7. Chung, L., Leite, J.C.S.P.: On Non-functional requirements in the Software Engineering. Software Quality Journal 5(4), 285–294 (2009)

    Google Scholar 

  8. Google App Engine. Service Level Agreement

    Google Scholar 

  9. Software Engineering and IEEE Standards Committee. IEEE Recommended Practice for Software Requirements Specifications 1993 (1993)

    Google Scholar 

  10. Advancing Open Standards for the Information Society (OASIS). Web Services Quality Factors Version 1.0, pp. 1–29, (July 2011)

    Google Scholar 

  11. Galster, M., Bucherer, E.: A Taxonomy for Identifying and Specifying Non-Functional Requirements in Service-Oriented Development. In: 2008 IEEE Congress on Services - Part I, pp. 345–352 (July 2008)

    Google Scholar 

  12. Gartner and IBM. Explore PaaS with a video from Gartner and IBM

    Google Scholar 

  13. Glinz, M.: On Non-Functional Requirements. In: 15th IEEE RE Conf. (2007)

    Google Scholar 

  14. Grimshaw, D.J., Draper, G.W.: Non-functional requirements analysis: deficiencies in structured methods. Information and Software Technology 43(11), 629–634 (2001)

    Article  Google Scholar 

  15. Jaakkola, Thalheim: Framework for high-quality software design and development: a systematic approach. IET Software 42, 105–118 (2010)

    Article  Google Scholar 

  16. Ludwig, H., Keller, A., Dan, A., King, R.P., Franck, R.: Web Service Level Agreement (WSLA) Language Specification. pp. 1–110 (2003)

    Google Scholar 

  17. Mairiza, D., Zowghi, D., Nurmuliani, N.: An Investigation into the Notion of Non-Functional Requirements. In: Proceedings of the 2010 ACM Symposium on Applied Computing, SAC 2010, p. 311 (2010)

    Google Scholar 

  18. O’Brien, L., Merson, P., Bass, L.: Quality Attributes for Service-Oriented Architectures. In: International Workshop on Systems Development in SOA Environments (SDSOA 2007: ICSE Workshops 2007), p. 3 (May 2007)

    Google Scholar 

  19. University of California. Privacy and Confidentiality (retrieved: March 2012)

    Google Scholar 

  20. Amazon Web Services. AWS Customer Agreement and Service Level Agreement

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2012 Springer-Verlag Berlin Heidelberg

About this paper

Cite this paper

Rady, M. (2012). Parameters for Service Level Agreements Generation in Cloud Computing. In: Castano, S., Vassiliadis, P., Lakshmanan, L.V., Lee, M.L. (eds) Advances in Conceptual Modeling. ER 2012. Lecture Notes in Computer Science, vol 7518. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-33999-8_3

Download citation

  • DOI: https://doi.org/10.1007/978-3-642-33999-8_3

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-642-33998-1

  • Online ISBN: 978-3-642-33999-8

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics