Reflections on the Reflexive Activities of Embedded System Development: a Case Study

This paper presents the findings of an in-depth investigation of situated activities of developers and managers during an embedded system development. Previous empirical investigations claim that software design may involve activities outside the continuum of methodologies, such as improvisation or situated activities. Those activities may involve reflexive practices that are purposefully applied by developers and managers. This research provides a better understanding how reflexive behaviors shape the development process by adopting an interpretive approach. The study involved the collection and analysis of qualitative data that were gathered during a 16-month field study carried out in an automotive company. This paper offers insights into everyday actions and practices, the role of reflexivity, and different consciousness levels of reflexive practices of developers and managers. The paper argues that nurturing reflexivity can positively influence information system developments. Furthermore, this paper points out how reflexivity could be encouraged to advance project work and organizational processes.

[1]  Jr. Raymond McLeod.  Information systems concepts , 1994 .

[2]  A. Kellerman,et al.  The Constitution of Society : Outline of the Theory of Structuration , 2015 .

[3]  David E. Avison,et al.  The fiction of methodological development: a field study of information systems development , 1999, Inf. Technol. People.

[4]  M. Cunha.  Bricolage in Organizations , 2005 .

[5]  Wanda J. Orlikowski,et al.  Studying Information Technology in Organizations: Research Approaches and Assumptions , 1991, Inf. Syst. Res..

[6]  Karlheinz Kautz,et al.  The Utilization of Information Systems Development Methodologies in Practice , 2004 .

[7]  David Wastell,et al.  The fetish of technique: methodology as a social defence , 1996 .

[8]  Richard Baskerville,et al.  Amethodical systems development: the deferred meaning of systems development methods , 2000 .

[9]  Ian K. Allison,et al.  Software process improvement as emergent change : a structurational analysis , 2007, Inf. Softw. Technol..

[10]  A. Pinsonneault,et al.  Challenges in Conducting Empirical Work Using Structuration Theory: Learning from IT Research , 2005 .

[11]  Niek F. du Plooy.  Information systems as social systems , 2003 .

[12]  Joyce J. Elam,et al.  Inside a software design team: knowledge acquisition, sharing, and integration , 1993, CACM.

[13]  Jorgen P. Bansler,et al.  Improvisation in Information Systems Development , 2004, Relevant Theory and Informed Practice.

[14]  Geoff Walsham,et al.  Interpreting Information Systems in Organizations , 1993 .

[15]  Claudio U. Ciborra,et al.  The labyrinths of Information , 2002 .

[16]  Bernhard Rumpe,et al.  Assumptions Underlying Agile Software-Development Processes , 2005, J. Database Manag..

[17]  H. V. D. Water,et al.  ISO 9000 series ‐ Certification and performance , 2001 .

[18]  David E. Avison,et al.  INFORMATION SYSTEMS DEVELOPMENT , 2006 .

[19]  Helena Karsten,et al.  Review: Structuration Theory and Information Systems Research , 2003 .

[20]  V. Sambamurthy,et al.  PRIOR LITERATURE : CATEGORIZATION Identification of the Relevant Literature Base , 2007 .

[21]  Richard T. Vidgen,et al.  A framework for understanding how a unique and local IS development method emerges in practice , 2006, Eur. J. Inf. Syst..

[22]  Susan Gasson,et al.  A social action model of situated information systems design , 1999, DATB.

[23]  David E. Avison,et al.  The discipline of information systems: Let many flowers bloom! , 1995, ISCO.

[24]  A. Michael Huberman,et al.  An expanded sourcebook qualitative data analysis , 1994 .