Are software engineers' responses to incomplete requirements related to project characteristics?

Albayrak, Özlem; Albayrak, Duygu; Kilic, Tuna

doi:10.1109/icadiwt.2009.5273869

Cited by 4 publications

(2 citation statements)

References 25 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…As described in the preceding section, four main ISD issues were highlighted and mapped against the components of mindfulness (see Table 3) thereby uncovering the associated mindful/mindless behaviours. It must be stated that while these issues are unique to TexunaTech, they are similar to typical issues encountered by ISD organisations: vague and incomplete requirements (Albayrak et al ., 2009) leading to fire fighting (Blotner, 2002). In addition, buffer time erosion is similar to problems noted by others that risk identification is often an informal process that is performed badly (Ibbs & Kwak, 2000).…”

Section: Case Analysismentioning

confidence: 98%

Using mindfulness to examine ISD agility

McAvoy¹,

Nagle²,

Sammon³

2012

Information Systems Journal

View full text Add to dashboard Cite

As information systems development (ISD) organisations face increasing market demands, strategies such as agile development have been used to help address these demands. Now, as information systems (IS) research in agile development is gaining in theoretical rigour, this study explores the use of mindfulness as a theoretical framework to examine ISD agility. At its core, the mindfulness theoretical concept promotes a focus on 'continuous attention to detail' and 'vigilance to minimise errors and respond effectively to unexpected events'. Incorporating a sixteen month ongoing longitudinal case study of an ISD organisation, this research provides an insight into the practice of what we term 'doing' agile and 'being' agile, while also providing a number of theoretical contributions around the value of mindfulness for ISD agility.

show abstract

Section: Case Analysismentioning

confidence: 98%

Using mindfulness to examine ISD agility

McAvoy¹,

Nagle²,

Sammon³

2012

Information Systems Journal

View full text Add to dashboard Cite

show abstract

“…When software engineers fill the gaps with information not shared and, hence, not confirmed by the user, they have made implicit assumptions, which may be the primary source of many user change requests, reworks, validity problems, and even project failures. Recent research studied various factors related to the assumptions made by the engineers [30,31,32].…”

Section: Introductionmentioning

confidence: 99%

Incomplete Software Requirements and Assumptions Made by Software Engineers

Albayrak

Kurtoglu

Biçakçi³

2009

2009 16th Asia-Pacific Software Engineering Conference

Self Cite

View full text Add to dashboard Cite

Abstract-Many software engineers make implicit assumptions when working with incomplete software requirements. To study assumptions made by software engineers while converting incomplete requirements to software design or to implementation phase deliverables, we conducted an experiment with 251 software engineers from eight companies. The results of this empirical study showed that how software engineers responded (using source code, pseudo code, or prototype) to an incomplete requirement significantly impacted the number of explicit assumptions they made. We studied relationships between the number of explicit assumptions and the engineers' experience and educational backgrounds.On average, non-computer-background engineers made more explicit assumptions than computerbackground graduates. We found a significant relationship between the engineers' experience and the number of explicit assumptions made. We discuss the results and their implications.

show abstract