35040 |
Creator |
eb1a0182e6ea336167735f7009ed60e8 |
35040 |
Creator |
f54e18abddd7129dc881abe5912f493d |
35040 |
Creator |
bdbec689f382b43c2f71f7ec8cc7c309 |
35040 |
Creator |
e78fb76e28392daa1faea2ef11c875ca |
35040 |
Date |
2012-06 |
35040 |
Is Part Of |
repository |
35040 |
abstract |
Software rarely works as intended when it is initially written. Things go wrong, and
developers are commonly understood to form theories and strategies to deal with them.
Much of this knowledge relates to ephemeral flaws rather than reported bugs, and is
not captured in the software record. As a result, these flaws and understanding about
them are neglected in software engineering research. In this paper we describe a study
designed to elicit stories from software developers about problems they encounter
in their daily work. We also offer preliminary thoughts about the utility of retrospective
interviewing in getting at information about ephemeral flaws. |
35040 |
authorList |
authors |
35040 |
presentedAt |
ext-20d974e9fe8414ec516ef19581b9e9cf |
35040 |
status |
peerReviewed |
35040 |
type |
AcademicArticle |
35040 |
type |
Article |
35040 |
label |
Lopez, Tamara ; Petre, Marian and Nuseibeh, Bashar (2012). Getting at ephemeral
flaws. In: Cooperative and Human Aspects of Software Engineering (CHASE), 2012 5th
International Workshop on, 2 Jun 2012, Zurich. |
35040 |
label |
Lopez, Tamara ; Petre, Marian and Nuseibeh, Bashar (2012). Getting at ephemeral
flaws. In: Cooperative and Human Aspects of Software Engineering (CHASE), 2012 5th
International Workshop on, 2 Jun 2012, Zurich. |
35040 |
Title |
Getting at ephemeral flaws |
35040 |
in dataset |
oro |