On Exploiting End-User Feedback in Requirements Engineering

Requirements elicitation is a relevant research area in Requirements Engineering(RE) since elicitation is a key task that must be performed in any project [12].Elicitation usually involves different types of stakeholders (e.g. analysts, man-agers, users, etc.) who provide information that may turn into requirements.Over time, several elicitation techniques have been proposed to gather require-ments. But how and when end-users express their expectations about a softwareis an issue that has been mainly explored within the user experience researchcommunity [7], and it is only recently that RE is looking at it [22]. User feedbackis recognised as a source for changes in a system [6] (i.e. changes in requirements,new ones, etc.).We define end-user feedback as meaningful information provided by end-usersof widely used software applications with the purpose of suggesting improvementsto such applications (i.e. new needs, modifications, or strategic behaviours).End-user feedback in discussion forums seems to be helpful for developers in evolvingapplications. Specifically, the continuous management of fansites (e.g. blogs, dis-cussion forums, etc.) of an online game (i.e. Habbo Hotel

[1]  Saif Mohammad,et al.  Colourful Language: Measuring Word-Colour Associations , 2011, CMCL@ACL.

[2]  Jörg Rech,et al.  Wiki-Based Stakeholder Participation in Requirements Engineering , 2007, IEEE Software.

[3]  J. Hattie,et al.  The Power of Feedback , 2007 .

[4]  Michael W. Godfrey,et al.  The past, present, and future of software evolution , 2008, 2008 Frontiers of Software Maintenance.

[5]  John Mylopoulos,et al.  Analysis of Multi-Party Agreement in Requirements Validation , 2009, 2009 17th IEEE International Requirements Engineering Conference.

[6]  Neil A. M. Maiden,et al.  Using Mobile RE Tools to Give End-Users Their Own Voice , 2010, 2010 18th IEEE International Requirements Engineering Conference.

[7]  Alistair G. Sutcliffe,et al.  Experience with user-centred requirements engineering , 2011, Requirements Engineering.

[8]  Mathias Funk,et al.  Model-driven design of self-observing products , 2011 .

[9]  Joemon M. Jose,et al.  Affective feedback: an investigation into the role of emotions in the information seeking process , 2008, SIGIR '08.

[10]  Anna Perini,et al.  Revealing the obvious?: A retrospective artefact analysis for an ambient assisted-living project , 2012, 2012 Second IEEE International Workshop on Empirical Requirements Engineering (EmpiRE).

[11]  Dewayne E. Perry,et al.  Software Evolution and Feedback: Theory and Practice , 2006 .

[12]  E. Mory Feedback research revisited. , 2004 .

[13]  Peter Sawyer,et al.  BEST PAPERS OF RE’10: REQUIREMENTS ENGINEERING IN A MULTI-FACETED WORLD Relevance-based abstraction identification: technique and evaluation , 2022 .

[14]  Kurt Schneider Focusing spontaneous feedback to support system evolution , 2011, 2011 IEEE 19th International Requirements Engineering Conference.

[15]  Walid Maalej,et al.  When users become collaborators: towards continuous and context-aware user input , 2009, OOPSLA Companion.

[16]  Antonella De Angeli,et al.  Using affect to evaluate user engagement , 2012, CHI Extended Abstracts.

[17]  Roel Wieringa,et al.  Design science as nested problem solving , 2009, DESRIST.

[18]  Sampsa Hyysalo,et al.  Lessons for participatory designers of social media: long-term user involvement strategies in industry , 2012, PDC '12.

[19]  Anna Perini,et al.  Where Did the Requirements Come from? A Retrospective Case Study , 2012, ER Workshops.

[20]  Anna Perini,et al.  Satisfying User Needs at the Right Time and in the Right Place: A Research Preview , 2011, REFSQ.

[21]  Anna Perini,et al.  Analysing User Feedback and Finding Experts: Can Goal-Orientation Help? , 2013, iStar.

[22]  Mary Shaw,et al.  Engineering Self-Adaptive Systems through Feedback Loops , 2009, Software Engineering for Self-Adaptive Systems.

[23]  Amy J. Ko,et al.  How power users help and hinder open bug reporting , 2010, CHI.