Combining qualitative empirical research with method, technique and process improvement

The development of methods tools and process improvements is best to be based on the understanding of the development practice to be supported. Qualitative research has been proposed as a method for understanding the social and cooperative aspects of software development. However, qualitative research is not easily combined with the improvement orientation of an engineering discipline. During the last 6 years, we have applied an approach we call 'cooperative method development', which combines qualitative social science fieldwork, with problem-oriented method, technique and process improvement. The action research based approach focusing on shop floor software development practices allows an understanding of how contextual contingencies influence the deployment and applicability of methods, processes and techniques. This article summarizes the experiences and discusses the further development of this approach based on several research projects in cooperation with industrial partners.

[1]  Alfonso Fuggetta,et al.  Software process: a roadmap , 2000, ICSE '00.

[2]  Kaj Grønbæk,et al.  Informing General CSCW Product Development through Cooperative Design in Specific Work Domains , 2004, Computer Supported Cooperative Work (CSCW).

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

[4]  Bjørnar Tessem,et al.  Human and social factors of software engineering , 2005, Proceedings. 27th International Conference on Software Engineering, 2005. ICSE 2005..

[5]  Yvonne Dittrich,et al.  How agile are industrial software development practices? , 2006, J. Syst. Softw..

[6]  Lucy A. Suchman,et al.  Reflections on a Work-Oriented Design Project , 1996, Hum. Comput. Interact..

[7]  Elmer Sandvad,et al.  The M.A.D. Experience: Multiperspective Application Development in evolutionary prototyping , 1998, ECOOP.

[8]  Heinz K. Klein,et al.  Reflective System Development: A Significant Step Towards Building a Cumulative Tradition in IS Research on Systems Development? , 1998, Scandinavian Journal of Information Systems.

[9]  Lars Mathiassen,et al.  Cultivation and engineering of a software metrics program , 2003, Inf. Syst. J..

[10]  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.

[11]  Peter Naur,et al.  Programming as theory building , 1985 .

[12]  Christiane Floyd,et al.  Software Development and Reality Construction , 1992 .

[13]  Victor R. Basili,et al.  Communication and Organization: An Empirical Study of Discussion in Inspection Meetings , 1998, IEEE Trans. Software Eng..

[14]  Yvonne Dittrich,et al.  Designing for changing work and business practices , 2003 .

[15]  Alistair Cockburn,et al.  Agile Software Development , 2001 .

[16]  Janice Singer,et al.  For the Special issue on Qualitative Software Engineering Research , 2007, Inf. Softw. Technol..

[17]  Yvonne Dittrich,et al.  Can Software Development be too Use Oriented? Going Native as an issue in Participatory Design. , 2001 .

[18]  Yvonne Dittrich,et al.  'Bad practice' or 'Bad methods' are software engineering and ethnographic discourses incompatible? , 2002, Proceedings International Symposium on Empirical Software Engineering.

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

[20]  Lars Mathiassen,et al.  Collaborative Practice Research , 2000, Scand. J. Inf. Syst..

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

[22]  Victor R. Basili,et al.  An Empirical Study of Communication in Code Inspections , 1997, Proceedings of the (19th) International Conference on Software Engineering.

[23]  Thomas R. Kochtanek,et al.  ORGANIZATIONAL and END USER COMPUTING , 2004 .

[24]  Yvonne Dittrich,et al.  Organisation matters: how the organisation of software development influences the development of product line architecture , 2008, ICSE 2008.

[25]  Frederick P. Brooks,et al.  No Silver Bullet: Essence and Accidents of Software Engineering , 1987 .

[26]  Yvonne Dittrich,et al.  Personas is not applicable: local remedies interpreted in a wider context , 2004, PDC 04.

[27]  Arthur H. J. Sale,et al.  Computing as a Human Activity , 1976, Aust. Comput. J..

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

[29]  Lucy A. Suchman,et al.  Making work visible , 1995, CACM.

[30]  Kari Rönkkö,et al.  Making Methods Work in Software Engineering: Method Deployment - as a Social Achievement , 2005 .

[31]  Frada Burstein,et al.  Chapter 8 – System development in information systems research , 2002 .

[32]  Kristen Nygaard,et al.  Program development as a social activity , 1990 .

[33]  Jesper Simonsen,et al.  Participatory IT Design: Designing for Business and Workplace Realities , 2004 .

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

[35]  D. Schoen,et al.  The Reflective Practitioner: How Professionals Think in Action , 1985 .

[36]  Alan Cooper,et al.  The Inmates are Running the Asylum , 1999, Software-Ergonomie.

[37]  Lucy A. Suchman,et al.  Office procedure as practical action: models of work and system design , 1983, TOIS.

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

[39]  Kristen Nygaard,et al.  Program Development as a Social Activity (Invited Paper) , 1986, IFIP Congress.

[40]  Lars Mathiassen,et al.  Mapping situations within a system development project , 1985, Inf. Manag..

[41]  Lars Mathiassen,et al.  Information-centric assessment of software metrics practices , 2005, IEEE Transactions on Engineering Management.

[42]  T.L.J. Ferris,et al.  Participatory IT Design: Designing for Business and Workplace Realities , 2005, IEEE Transactions on Professional Communication.

[43]  Gerhard Schmidt,et al.  STEPS to Software Development with Users , 1989, ESEC.

[44]  Jonathan Grudin,et al.  Personas: practice and theory , 2003, DUX '03.

[45]  Etienne Wenger,et al.  Communities of Practice: Learning, Meaning, and Identity , 1998 .

[46]  Donald A. Schön,et al.  The Reflective Practitioner: How Professionals Think in Action. , 1987 .

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

[48]  Kari Rönkkö,et al.  Interpretation, interaction and reality construction in software engineering: An explanatory model , 2007, Inf. Softw. Technol..