Access the full text.
Sign up today, get DeepDyve free for 14 days.
J. Fitzsimmons, Mona Fitzsimmons, Sanjeev Bordoloi (1997)
Service Management: Operations, Strategy, and Information Technology
L. Ellram, Wendy Tate, C. Billington (2008)
Offshore outsourcing of professional services: A transaction cost economics perspectiveJournal of Operations Management, 26
I. Jacobson, Magnus Christerson, P. Jonsson, Gunnar Övergaard (1993)
Object-oriented software engineering - a use case driven approach
H. Bullinger, K. Fähnrich, T. Meiren (2003)
Service engineering—methodical development of new service productsInternational Journal of Production Economics, 85
A. Donabedian
Explorations in quality assessment and monitoring
J. Bocanegra, J. Peña, A. Ruiz‐Cortés
Interorganizational business modelling: an approach for maintaining traceability between goals, processes and organizational structures
W. Valk, F. Rozemeijer (2009)
Buying business services : towards a structured service purchasing processJournal of Services Marketing, 23
Craig Larman, V. Basili (2003)
Iterative and incremental developments. a brief historyComputer, 36
L. Ellram, Wendy Tate, C. Billington (2004)
Understanding and Managing the Services Supply ChainJournal of Supply Chain Management, 40
Ellen Gottesdiener (2002)
Requirements by Collaboration: Workshops for Defining Needs
Hau Lee (2004)
The triple-A supply chain.Harvard business review, 82 10
R. Jackson, L. Neidell, Dale Lunsford (1995)
An empirical investigation of the differences in goods and services as perceived by organizational buyersIndustrial Marketing Management, 24
S. Robertson, J. Robertson (1999)
Mastering the Requirements Process
Alistair Cockburn (2008)
Using Both Incremental and Iterative Development
A. Roth, L. Menor (2009)
INSIGHTS INTO SERVICE OPERATIONS MANAGEMENT: A RESEARCH AGENDAProduction and Operations Management, 12
Micheal Kelly, Jean-Louis Schaan, H. Joncas (2002)
Managing Alliance Relationships: Key Challenges in the Early Stages of CollaborationIO: Theory
A. Durán
A methodological environment for requirement engineering of information systems
C. Congram, M. Epelman
How to describe your service: an invitation to the structured analysis and design technique
Carole Congram, M. Epelman (1995)
How to describe your serviceInternational Journal of Service Industry Management, 6
F. Wynstra, B. Axelsson, W. Valk (2006)
An application‐based classification to understand buyer‐supplier interaction in business servicesInternational Journal of Service Industry Management, 17
Pär Åhlström, Fredrik Nordin (2006)
Problems of establishing service supply relationships: Evidence from a high-tech manufacturing companyJournal of Purchasing and Supply Management, 12
R. Johnston (2005)
Service operations management: from the roots upInternational Journal of Operations & Production Management, 25
L. Zomerdijk, C. Voss (2011)
NSD processes and practices in experiential servicesJournal of Product Innovation Management, 28
I. Sommerville, P. Sawyer (1997)
Requirements Engineering: A Good Practice Guide
L. Smeltzer, Jeffrey Ogden (2002)
Purchasing Professionals' Perceived Differences between Purchasing Materials and Purchasing ServicesJournal of Supply Chain Management, 38
P. Matthyssens, K. Vandenbempt (1998)
Creating competitive advantage in industrial servicesJournal of Business & Industrial Marketing, 13
Alistair Cockburn (2000)
Writing Effective Use Cases
Alistair Cockburn (2000)
Structuring Use Cases with Goals
Dan Andersson, A. Norrman (2002)
Procurement of logistics services—a minutes work or a multi-year project?European Journal of Purchasing & Supply Management, 8
H. Mossel, W. Valk (2008)
Securing customer satisfaction through component service specifications : purchasing maintenance for social rented housingJournal of Purchasing and Supply Management, 14
Purpose – The specification of business services (BS) is one of the key factors for success in service provision. Researchers and practitioners have identified a set of problems in BS specification, namely: communication problems between providers and buyers, inaccurate specifications and changes in requirements. These problems were identified in the software engineering (SE) field many years ago, resulting in the development of many techniques and tools to address them. Given the similarities between the two fields, the purpose of this paper is to identify the main lessons learned in SE and to propose how they can be adapted to the BS field. Design/methodology/approach – The paper takes the form of a literature study and presents a conceptual solution. Findings – To address communications problems and inaccuracies in BS specification, a formal requirements specification stage is required. Requirements should be set out in a well‐structured written, definition, document which can be used at a subsequent stage for design of the service (the definition of the solution). A requirements document for BS is proposed based on BS literature and SE methods. This document is based on the approaches used in the SE field for improving communication and reducing inaccuracies and covers the information needed in the BS field for specifying a business service. Second, a life cycle approach is proposed based on SE practice. It is shown that different lifecycle sequences can be used depending on the degree of fluidity in the communication between buyer and provider, the complexity of the BS and the stability of their requirements, with a repetitive process where specification and design are revisited iteratively and/or incrementally often being the most appropriate. This approach helps to stabilise requirements and to avoid inaccuracies being made in the specification. Research limitations/implications – This paper is literature based. Although still untested empirically in the BS field, the recommended approach has been intensively proved in the SE field. Originality/value – Requirements specification is a necessary (monetary, time and resource) cost for successful BS provision. The BS industry must realise that requirements have to be set down in writing and agreed upon with customers before initiating the design of the service.
Journal of Service Management – Emerald Publishing
Published: Mar 9, 2012
Keywords: Software engineering; Customer requirements; Specifications; Business planning; Business services
Read and print from thousands of top scholarly journals.
Already have an account? Log in
Bookmark this article. You can see your Bookmarks on your DeepDyve Library.
To save an article, log in first, or sign up for a DeepDyve account if you don’t already have one.
Copy and paste the desired citation format or use the link below to download a file formatted for EndNote
Access the full text.
Sign up today, get DeepDyve free for 14 days.
All DeepDyve websites use cookies to improve your online experience. They were placed on your computer when you launched this website. You can change your cookie settings through your browser.