For the Special issue on Qualitative Software Engineering Research

Almost twenty years have passed since the first qualitative research study in software engineering was published [14]. Using qualitative methods and a qualitative analytical framework, Curtis, et al. found communication and cooperation to be critical factors in developing large-scale software systems. Given the importance of this study, it is perhaps surprising that research publications using qualitative methods are still scarce. Therefore, our goal in creating this special issue is to make existing qualitative research more visible and further the understanding of qualitative research and its importance in the software engineering community. Qualitative research has its main strength in exploring and illuminating the in situ practice of software engineering. This is the everyday practice where software engineers interpret, appropriate, and implement the methods, techniques and processes of the trade. A better understanding of these in situ methods can – in turn – provide a base for their improvement. From 23 submissions we selected eleven articles. The articles represent a diverse set of theoretical frameworks and methods, while focusing on a wide range of software engineering activities from requirements engineering, project management to software process improvement. The selected articles illustrate the richness of existing research and showcase important and applicable results which will further the discussion of qualitative methods – not only about the concrete results but importantly so, on the value of qualitative research in software engineering in general. To make the papers more accessible to an audience that may not be used to qualitative research, we introduce this special issue more thoroughly than what is normally seen. By doing so we answer a number of questions related to the practice of qualitative research in the software engineering domain. In turn, each article selected for this special issue addresses some or all of the questions in the context of real research problems. The editorial proceeds as follows. First qualitative research is introduced and related to the tradition of software engineering. Then we present an overview of the different discourses in which qualitative research on software engineering is published followed by a discussion of potential quality criteria for qualitative research. We end with an introduction to the articles published in this special issue. There is no 'one way' of doing qualitative research. The only common denominator of qualitative research is that it is based on qualitative data. Some see the possibility to develop an understanding of the software engineering process from a …

[1]  David F. Redmiles,et al.  On the relationship between software dependencies and coordination: field studies and tool support , 2005 .

[2]  Helen Sharp,et al.  The Characteristics of XP Teams , 2004, XP.

[3]  Michele Marchesi,et al.  Extreme Programming and Agile Processes in Software Engineering , 2003, Lecture Notes in Computer Science.

[4]  Tom Rodden,et al.  Moving out from the control room: ethnography in system design , 1994, CSCW '94.

[5]  Martin P. Robillard,et al.  How effective developers investigate source code: an exploratory study , 2004, IEEE Transactions on Software Engineering.

[6]  Daniela E. Damian,et al.  An Industrial Case Study of Immediate Benefits of Requirements Engineering Process Improvement at the Australian Center for Unisys Software , 2004, Empirical Software Engineering.

[7]  James D. Herbsleb,et al.  Splitting the organization and integrating the code: Conway's law revisited , 1999, Proceedings of the 1999 International Conference on Software Engineering (IEEE Cat. No.99CB37002).

[8]  Rebecca E. Grinter Supporting articulation work using software configuration management systems , 1996, Computer Supported Cooperative Work (CSCW).

[9]  Wes Sharrock,et al.  Occasioned practices in the work of software engineers , 1994 .

[10]  Toni Robertson,et al.  Embodied actions in time and place: The cooperative design of a multimedia, educational computer game , 1996, Computer Supported Cooperative Work (CSCW).

[11]  Philip Kraft,et al.  Software Practice Is Social Practice , 2002, Social Thinking - Software Practice.

[12]  Bill Curtis,et al.  A field study of the software design process for large systems , 1988, CACM.

[13]  Helen Sharp,et al.  A Distributed Cognition Account of Mature XP Teams , 2006, XP.

[14]  A. Strauss,et al.  The Discovery of Grounded Theory , 1967 .

[15]  Victor R. Basili,et al.  Software process evolution at the SEL , 1994, IEEE Software.

[16]  Yvonne Dittrich,et al.  Agile Processes Enhancing User Participation for Small Providers of Off-the-Shelf Software , 2004, XP.

[17]  Jesper Simonsen,et al.  Http Log Analysis: An Approach to Studying the Use of Web-Based Information Systems , 2004, Scand. J. Inf. Syst..

[18]  Brad A. Myers,et al.  An Exploratory Study of How Developers Seek, Relate, and Collect Relevant Information during Software Maintenance Tasks , 2006, IEEE Transactions on Software Engineering.

[19]  Yvonne Dittrich,et al.  How use-oriented development can take place , 2004, Inf. Softw. Technol..

[20]  Tracy Hall,et al.  De-motivators for software process improvement: an analysis of practitioners' views , 2003, J. Syst. Softw..

[21]  Audris Mockus,et al.  Formulation and preliminary test of an empirical theory of coordination in software engineering , 2003, ESEC/FSE-11.

[22]  Yvonne Dittrich,et al.  Social Thinking - Software Practice , 2002, Social Thinking - Software Practice.

[23]  Helen Sharp,et al.  Organisational culture and XP: three case studies , 2005, Agile Development Conference (ADC'05).

[24]  Austen Rainer,et al.  Key success factors for implementing software process improvement: a maturity-based analysis , 2002, J. Syst. Softw..

[25]  Jan Chong,et al.  Social behaviors on XP and non-XP teams: a comparative study , 2005, Agile Development Conference (ADC'05).

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

[27]  Gerhard Schmidt,et al.  Out of Scandinavia: Alternative Approaches to Software Design and System Development , 1989, Hum. Comput. Interact..

[28]  Tracy Hall,et al.  Motivators of Software Process Improvement: an analysis of practitioners' views , 2002, Journal of Systems and Software.

[29]  Robert R. Kessler,et al.  The collaborative software process(sm) , 2000 .

[30]  Aaron Tay CSCW '94 , 1995, SGCH.

[31]  Kent Beck,et al.  Extreme Programming Explained: Embrace Change (2nd Edition) , 2004 .

[32]  Bjørnar Tessem,et al.  Human and social factors of software engineering: workshop summary , 2005, SOEN.

[33]  Helen Sharp,et al.  An Ethnographic Study of XP Practice , 2004, Empirical Software Engineering.

[34]  Helen Sharp,et al.  The role of story cards and the wall in XP teams: a distributed cognition perspective , 2006, AGILE 2006 (AGILE'06).

[35]  Janice Singer,et al.  An examination of software engineering work practices , 1997, CASCON.

[36]  P. Checkland,et al.  Action Research: Its Nature and Validity , 1998 .

[37]  James E. Tomakyo,et al.  Human Aspects of Software Engineering , 2005 .

[38]  Gail C. Murphy,et al.  Questions programmers ask during software evolution tasks , 2006, SIGSOFT '06/FSE-14.

[39]  Robert L. Glass,et al.  The software-research crisis , 1994, IEEE Software.

[40]  Lars Mathiassen,et al.  Reflective Systems Development , 1998, Scand. J. Inf. Syst..

[41]  F. Maurer,et al.  Human and social factors of software engineering , 2005, Proceedings. 27th International Conference on Software Engineering, 2005. ICSE 2005..

[42]  A. Strauss,et al.  Grounded Theory in Practice , 1997 .

[43]  Peter H. Carstensen,et al.  Development and Use of Web-Based Information Systems , 2004 .

[44]  Jorgen P. Bansler,et al.  A reappraisal of structured analysis: design in an organizational context , 1993, TOIS.

[45]  Kent L. Beck,et al.  Extreme programming explained - embrace change , 1990 .

[46]  Frank Maurer,et al.  Foundations of Agile Decision Making from Agile Mentors and Developers , 2006, XP.

[47]  Hilda Tellioglu,et al.  Negotiating Boundaries. Configuration Management in Software Development Teams , 1997, Computer Supported Cooperative Work (CSCW).

[48]  L. Suchman,et al.  Understanding practice: Artificial intelligence as craftwork , 1993 .

[49]  Jørgen P. Bansler,et al.  The nature of software work. Systems development as labour process , 1991 .

[50]  Rebecca E. Grinter Recomposition: Coordinating a Web of Software Dependencies , 2003, Computer Supported Cooperative Work (CSCW).

[51]  Victor R. Basili,et al.  The role of experimentation in software engineering: past, current, and future , 1996, Proceedings of IEEE 18th International Conference on Software Engineering.

[52]  Yvonne Dittrich,et al.  When Plans do not Work Out: How Plans are Used in Software Development Projects , 2005, Computer Supported Cooperative Work (CSCW).

[53]  Martyn Hammersley,et al.  Ethnography : Principles in Practice , 1983 .

[54]  FitzgeraldBrian,et al.  Customising agile methods to software practices at Intel Shannon , 2006 .

[55]  Colin Potts,et al.  Collaborative conceptual design: A large software project case study , 1996, Computer Supported Cooperative Work (CSCW).

[56]  B SeamanCarolyn Qualitative Methods in Empirical Studies of Software Engineering , 1999 .

[57]  Helen Sharp,et al.  The Social Side of Technical Practices , 2005, XP.

[58]  Peter Axel Nielsen,et al.  Accessing Software Processes: Low Maturity or Sensible Practice , 2001, Scand. J. Inf. Syst..

[59]  Wes Sharrock,et al.  Project work: The organisation of collaborative design and development in software engineering , 1996, Computer Supported Cooperative Work (CSCW).

[60]  Adrian Mackenzie,et al.  From Cards to Code: How Extreme Programming Re-Embodies Programming as a Collective Practice , 2004, Computer Supported Cooperative Work (CSCW).

[61]  L. Williams The Collaborative Software Process , 1999 .