Understanding the use of an electronic process guide

Abstract This paper presents a case study of the installation and use of an electronic process guide within a small-to-medium software development company. The purpose of the study is to better understand how software engineers use this technology so that it can be improved and better used to support software process improvement. In the study the EPG was used to guide new processes in a software improvement programme. The use of the EPG was studied over a period of 8 months with data collected through access logs, by questionnaires and by interviews. The results show that the improvement programme was successful in improving project documentation, project management and the company's relationship with its customers. The EPG contributed to the improvement programme by providing support for the creation of templates for key project documentation, assisting with project planning and estimation and providing a forum for discussion of process and work practices. The biggest improvements that could be made to the EPG would be to provide better navigation tools including a graphical overview of the process, provide tailoring facilities, include examples and experience and link to a project management tool.

[1]  Mark C. Paulk,et al.  The Capability Maturity Model: Guidelines for Improving the Software Process , 1994 .

[2]  Ivar Jacobson,et al.  Object-oriented software engineering - a use case driven approach , 1993, TOOLS.

[3]  Khaled El Emam,et al.  Spice: The Theory and Practice of Software Process Improvement and Capability Determination , 1997 .

[4]  S. B. Kiselev,et al.  The capability maturity model: guidelines for improving the software process , 1995 .

[5]  P. Krutchen,et al.  The Rational Unified Process: An Introduction , 2000 .

[6]  R. Yin Case Study Research: Design and Methods , 1984 .

[7]  Gregory D. Schumacher,et al.  IEEE Guide for Developing System Requirements Specifications , 1999 .

[8]  William E. Riddle,et al.  Process Guides: Effective Guidance for Process Participants , 1998 .

[9]  A. Strauss,et al.  The discovery of grounded theory: strategies for qualitative research aldine de gruyter , 1968 .

[10]  K. Beck,et al.  Extreme Programming Explained , 2002 .

[11]  John D'Ambra,et al.  Practical software process improvement - the IMPACT project , 2001, Proceedings 2001 Australian Software Engineering Conference.

[12]  U. Becker-Kornstaedt,et al.  The V-Modell guide: experience with a Web-based approach for process support , 1999, STEP '99. Proceedings Ninth International Workshop Software Technology and Engineering Practice.

[13]  Philippe Kruchten,et al.  The Rational Unified Process: An Introduction , 1998 .

[14]  Robert J. Knapper,et al.  Guidelines for Tailoring DOD-STD-2167A for SDS (Strategic Defense System) Software Development , 1988 .

[15]  Carolyn B. Seaman,et al.  Qualitative Methods in Empirical Studies of Software Engineering , 1999, IEEE Trans. Software Eng..

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

[17]  Martin Verlage,et al.  Support for the Process Engineer: The Spearmint Approach to Software Process Definition and Process Guidance , 1999, CAiSE.

[18]  A. Strauss,et al.  Basics of qualitative research: Grounded theory procedures and techniques. , 1992 .

[19]  Pamela Jordan Basics of qualitative research: Grounded theory procedures and techniques , 1994 .