Dealing With Ambiguous and Fluctuating Requirements of Embedded System Development: A Case-Study

This paper presents the findings of a case study that investigates how developers and managers deal with ambiguous and fluctuating requirements during an embedded system development in a structured process management environment. In particular, this paper focuses on improvisation and bricolage actions as a coping strategy by software developers and managers. This research adopts an interpretive approach that involves the collection and analysis of qualitative data. In this study, we observed a turbulent environment with situated improvisational and bricolage responses from developers and managers. The organizational structured process management framework was not sophisticated enough to deal with the existing challenges. Moreover, some improvisational and bricolage activities became institutionalized and, hence, became organizational routines of developers and managers. This paper indicates the value of reflexive practices as vital issues for strategic conduct in the event that improvisational and bricolage activities were deployed as a coping strategy.

[1]  Wanda J. Orlikowski,et al.  Improvising Organizational Transformation Over Time: A Situated Change Perspective , 1996, Inf. Syst. Res..

[2]  K. Weick.  Improvisation as a Mindset for Organizational Analysis , 1998 .

[3]  Steve McConnell.  Software Estimation: Demystifying the Black Art , 2006 .

[4]  Barry W. Boehm,et al.  A spiral model of software development and enhancement , 1986, Computer.

[5]  Frank Vahid,et al.  Specification and Design of Embedded Hardware-Software Systems , 1995, IEEE Des. Test Comput..

[6]  Mie Augier,et al.  Networks, cognition and management of tacit knowledge , 1999, J. Knowl. Manag..

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

[8]  Edward A. Lee,et al.  What's Ahead for Embedded Software? , 2000, Computer.

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

[10]  Kyo Chul Kang,et al.  Issues in Requirements Elicitation , 1992 .

[11]  C. Lévi-Strauss.  The Savage Mind , 1967 .

[12]  Didar Zowghi,et al.  A situational method engineering approach to requirements elicitation workshops in the software development process , 2006, Softw. Process. Improv. Pract..

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

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

[15]  Martin Rappl,et al.  Requirements Management for Automotive Systems Development , 2000 .

[16]  W. Orlikowski,et al.  An Improvisational Model of Change Management: The Case of Groupware Technologies , 1996 .

[17]  Hans Toetenel,et al.  Embedded Software Engineering: The State of the Practice , 2003, IEEE Softw..

[18]  Kurt Schneider,et al.  Breaking the ice for agile development of embedded software: an industry experience report , 2004, Proceedings. 26th International Conference on Software Engineering.

[19]  Paul Clements,et al.  The Inevitable Pain of Software Development , Including of Extreme Programming , Caused by Requirements Volatility , .

[20]  Teresa M. Amabile,et al.  A Model of Creativity and Innovation in Organizations , 1988 .

[21]  Ian Sommerville,et al.  Software process models , 1996, CSUR.

[22]  Tammy Noergaard,et al.  Embedded Software , 2009, Encyclopedia of Biometrics.

[23]  Ali E. Akgün,et al.  New product development team improvisation and speed‐to‐market: an extended model , 2002 .

[24]  A. Cockburn,et al.  Agile Software Development: The People Factor , 2001, Computer.

[25]  Alistair Cockburn,et al.  Crystal Clear: A Human-Powered Methodology for Small Teams , 2004 .

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

[27]  Wanda J. Orlikowski,et al.  CASE Tools as Organizational Change: Investigating Incremental and Radical Changes in Systems Development , 1993, MIS Q..

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

[29]  Wendy L. Currie,et al.  The organizing vision of application service provision: a process-oriented analysis , 2004, Inf. Organ..

[30]  Anne S. Miner,et al.  Organizational Improvisation and Organizational Memory , 1998 .

[31]  Anne S. Miner,et al.  Organizational Improvisation and Learning: A Field Study , 2001 .

[32]  Francisco A. C. Pinheiro.  Requirements honesty , 2003, Requirements Engineering.

[33]  C. Ciborra.  The Platform Organization: Recombining Strategies, Structures, and Surprises , 1996 .

[34]  Anne S. Miner,et al.  Improvising firms: bricolage, account giving and improvisational competencies in the founding process , 2003 .

[35]  Petri Kettunen,et al.  How to steer an embedded software project: tactics for selecting the software process model , 2005, Inf. Softw. Technol..

[36]  Alan M. Davis,et al.  Requirements elicitation and elicitation technique selection: model for two knowledge-intensive software development processes , 2003, 36th Annual Hawaii International Conference on System Sciences, 2003. Proceedings of the.

[37]  Bashar Nuseibeh,et al.  Requirements engineering: a roadmap , 2000, ICSE '00.

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

[39]  Andrew C. Corbett,et al.  Proclivity for Improvisation as a Predictor of Entrepreneurial Intentions , 2006 .

[40]  J. Innes,et al.  Consensus Building as Role Playing and Bricolage , 2007 .

[41]  Uday R. Kulkarni,et al.  Critical success factors for software projects , 1998, ICIS '98.

[42]  Gert Goossens,et al.  Embedded software in real-time signal processing systems: design technologies , 1997, Proc. IEEE.

[43]  Christine Moorman,et al.  The Convergence of Planning and Execution: Improvisation in New Product Development , 1998 .

[44]  Roger Jianxin Jiao,et al.  Customer Requirement Management in Product Development: A Review of Research Issues , 2006, Concurr. Eng. Res. Appl..