How do practitioners capture and utilize user feedback during continuous software engineering?

• Verfasst von: Johanßen, Jan Ole [VerfasserIn]
• Verfasst von: Kleebaum, Anja [VerfasserIn]
• Verfasst von: Paech, Barbara [VerfasserIn]
• Titel: How do practitioners capture and utilize user feedback during continuous software engineering?
• Verf.angabe: Jan Ole Johanssen, Anja Kleebaum, Bernd Bruegge, Barbara Paech
• Jahr: 2019
• Umfang: 12 S.
• Fussnoten: Gesehen am 16.12.2019
• Titel Quelle: Enthalten in: IEEE International Requirements Engineering Conference (27. : 2019 : Jeju Island, South Korea)2019 IEEE 27th International Requirements Engineering Conference
• Ort Quelle: Piscataway, NJ : IEEE, 2019
• Jahr Quelle: 2019
• Band/Heft Quelle: (2019), Seite 153-164
• ISBN Quelle: 978-1-72813-912-8
• DOI: doi:10.1109/RE.2019.00026
• Datenträger: Online-Ressource
• Sprache: eng
• Sach-SW: Companies
• Sach-SW: continuous software engineering
• Sach-SW: Encoding
• Sach-SW: interview study
• Sach-SW: Interviews
• Sach-SW: Requirements engineering
• Sach-SW: Software
• Sach-SW: Software engineering
• Sach-SW: Tools
• Sach-SW: usage data
• Sach-SW: usage monitoring
• Sach-SW: user feedback
• K10plus-PPN: 1685676405

Abstract

Continuous software engineering (CSE) evolved as a process for rapid software evolution. Continuous delivery enables developers to frequently retrieve user feedback on the latest software increment. Developers use these insights for requirements validation and verification. Despite the importance of users, reports about user feedback in CSE practice are sparse. We conducted 20 interviews with practitioners from 17 companies that apply CSE. We asked practitioners how they capture and utilize user feedback. In this paper, we detail the practitioners' answers by posing three research questions. To improve continuous user feedback capture and utilization with respect to requirements engineering, we derived five recommendations: First, internal sources should be approached, as they provide a rich source of user feedback; second, existing tool support should be adapted and extended to automate user feedback processing; third, a concept of reference points should be established to relate user feedback to requirements; fourth, the utilization of user feedback for requirements validation should be increased; and last, the interaction with user feedback should be enabled and supported by increasing developer-user communication. We conclude that a continuous user understanding activity can improve requirements engineering by contributing to both the completeness and correctness of requirements.