Specification of Service Level Agreements: Problems, Principles and Practices

Software intensive systems (SIS) increasingly influence the ability of enterprises to be competitive in continuously changing market situations. The integration of these systems into organizations, and in particular the subsequent exploitation, maintenance and service activities, have become of utmost importance. Unfortunately the area of exploitation and operation, also known as service management, is still rather immature. Service management covers services such as performance and availability support, end-user and help desk support, education, and maintenance. One of the main concepts of service management is the Service Level Agreement (SLA). The goal of an SLA is to bridge the gap between service provider and users or customers. However, there exist many problems and unsolved questions regarding the specification and the quantification of SLAs. This paper addresses the specification of SLAs on the basis of three well-founded service management principles, respectively: 'continuity in service management,’ the pit/shell principle of a service, and the principle of specifying the quality of both a service process and a service object. Finally, the paper addresses the validation of these principles in practice.

[1]  Rob J. Kusters,et al.  Customer Orientation as a Basis for Computer Supported Technologies in Software Production , 1992, The Impact of Computer Supported Technologies in Information Systems Development.

[2]  A. Parasuraman,et al.  A MULTIPLE-ITEM SCALE FOR MEASURING CUSTOMER PERCEPTIONS OF SERVICE QUALITY , 1988 .

[3]  Douglas McBride,et al.  Toward Successful Deployment Of IT Service Management In The Distributed Enterprise , 1995, Int. CMG Conference.

[4]  J. Bouman,et al.  Specification of service level agreements, clarifying concepts on the basis of practical research , 1999, STEP '99. Proceedings Ninth International Workshop Software Technology and Engineering Practice.

[5]  Aarnout Brombacher,et al.  Nonfunctional requirements as a driving force of software development , 2001 .

[6]  Suzanne Robertson,et al.  Mastering the Requirements Process , 1999 .

[7]  Vanadis Crawford Setting performance expectations for technical communicators , 2003, SIGDOC '03.

[8]  Jjm Jos Trienekens,et al.  Software quality from a business perspective , 1997 .

[9]  Georg Herzwurm,et al.  Joint requirements engineering : QFD for rapid customer-focused software and Internet-development , 2000 .

[10]  Egon Berghout,et al.  The Goal/Question/Metric method: a practical guide for quality improvement of software development , 1999 .

[11]  Geoffrey A. Cross Collective Form: An Exploration of Large-Group Writing 1998 Outstanding Researcher Lecture , 2000 .

[12]  Egon Berghout,et al.  From process improvement to people improvement: enabling learning in software development , 2000, Inf. Softw. Technol..

[13]  Barry W. Boehm,et al.  Theory-W Software Project Management: Principles and Examples , 1989, IEEE Trans. Software Eng..