Getting at ephemeral flaws
conference contribution
posted on 2012-12-04, 09:00 authored by Tamara Lopez, Marian Petre, Bashar NuseibehSoftware 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.
History
Publication
Proceedings of 5th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE 2012) co-located with ICSE 2012;pp. 90-92Publisher
IEEE Computer SocietyNote
peer-reviewedOther Funding information
SFI, Royal Society WolfsonRights
“© 2012 IEEE. Personal use of this material is permitted. Permission from IEEE must be obtained for all other uses, in any current or future media, including reprinting/republishing this material for advertising or promotional purposes, creating new collective works, for resale or redistribution to servers or lists, or reuse of any copyrighted component of this work in other works.Language
EnglishExternal identifier
Usage metrics
Categories
No categories selectedLicence
Exports
RefWorks
BibTeX
Ref. manager
Endnote
DataCite
NLM
DC