The programmer's burden: developing expertise in programming
The psychology of expertise
Communications of the ACM
Proceedings of the Conference on The Future of Software Engineering
Contextual Design: Defining Customer-Centered Systems
Contextual Design: Defining Customer-Centered Systems
Modest_Witness@Second_Millenium.Femaleman_Meets_Oncomouse: Feminism and Technoscience
Modest_Witness@Second_Millenium.Femaleman_Meets_Oncomouse: Feminism and Technoscience
The Social Life of Information
The Social Life of Information
Social Analysis in the Requirements Engineering Process: From Ethnography to Method
RE '99 Proceedings of the 4th IEEE International Symposium on Requirements Engineering
Stakeholder Identification in the Requirements Engineering Process
DEXA '99 Proceedings of the 10th International Workshop on Database & Expert Systems Applications
Archetypal Source Code Searches: A Survey of Software Developers and Maintainers
IWPC '98 Proceedings of the 6th International Workshop on Program Comprehension
Multi-valued symbolic model-checking
ACM Transactions on Software Engineering and Methodology (TOSEM)
View merging in the presence of incompleteness and inconsistency
Requirements Engineering
Revealing actual documentation usage in software maintenance through war stories
Information and Software Technology
Can Requirements Be Creative? Experiences with an Enhanced Air Space Management System
ICSE '07 Proceedings of the 29th international conference on Software Engineering
Security Requirements Engineering: A Framework for Representation and Analysis
IEEE Transactions on Software Engineering
Marginal Notes on Amethodical Requirements Engineering: What Experts Learned from Experience
RE '08 Proceedings of the 2008 16th IEEE International Requirements Engineering Conference
Hi-index | 0.00 |
When analyzing data elicited using the "war stories" technique, previously introduced by Lutters and Seaman (Inf Softw Technol 49(6):576---587, 2007), we encountered unexpected challenges in applying standard qualitative analysis techniques. After reviewing the literature on stories and storytelling, we realized that a richer analysis would be possible if we accorded more respect to the data's structure and nature as stories, rather than treating our participants' utterances simply as textual data. We report on five lessons learned regarding how we can better analyze war stories as stories: 1) war stories tend to be about exceptional situations; 2) war stories tend to be diverse and resistant to being combined into a single grand narrative; 3) the humanities can be a valuable resource for analyzing war stories; 4) war stories are not just text, they are also performances; and 5) war stories are not just data, they are also instructive and evocative.