Voice of the users: an extended study of software feedback engagement

Tizard, James; Rietz, Tim; Liu, Xuanhui; Blincoe, Kelly

doi:10.1007/s00766-021-00357-1

Cited by 14 publications

(2 citation statements)

References 28 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In the software engineering area, one stream of studies focussed on the engagement level in software development teams' communication and whether greater engagement can improve team performance [19][20][21]. In recent years, scholars have begun to focus on engagement in team collaboration [22], team productivity [23], developer productivity [24], requirement documents [25], and software architecture [26]. However, there is limited study that focusses on the engagement level in development activities such as coding and testing.…”

Section: Related Work and Hypothesis Developmentmentioning

confidence: 99%

Test‐driven development, engagement in activity, and maintainability: An empirical study

Ren

Barrett

2023

IET Software

View full text Add to dashboard Cite

The software engineering community aims to achieve and maintain high-efficient software engineering practical activities. One of the techniques used for this purpose is Test-Driven Development (TDD), which is a cyclic and test-centered development method positively related to maintainability, which may vary depending on the context and application. Previous research has indicated that TDD's benefits on maintainability may be due to the improved focus on coding and testing activities. However, limited research has investigated the role of engagement in software quality. Therefore, this study investigates the relationship between TDD methods, engagement level in development activities, and maintainability. The primary research questions addressed in this study are does following TDD methods improve the engagement level in development activities? And does a higher engagement level leads to better maintainability? The study employs a statistical analysis technique, regression analysis to explore the research questions. The results show that TDD behaviours improve the engagement level, and engaging in development activities has a significant positive impact on maintainability. Additionally, the study finds that the positive impact of focussing on testing, such as writing more test cases, is more pronounced compared to coding activities. Our study adds to current software engineering literature that not only personal expertise but the engagement level in the development process are associated with software quality and calls for the emphasis on developer's engagement. K E Y W O R D Ssoftware engineering, software management, software process improvement, software quality | INTRODUCTIONThis is an open access article under the terms of the Creative Commons Attribution-NonCommercial-NoDerivs License, which permits use and distribution in any medium, provided the original work is properly cited, the use is non-commercial and no modifications or adaptations are made.

show abstract

Section: Related Work and Hypothesis Developmentmentioning

confidence: 99%

Test‐driven development, engagement in activity, and maintainability: An empirical study

Ren

Barrett

2023

IET Software

View full text Add to dashboard Cite

show abstract

“…A demographic study [ 30 ] of user engagement in app stores shows some difficulties with this feedback channel, for users (i) are mostly review readers rather than review authors, (ii) find it easier to switch to a competing app instead of providing feedback, and (iii) perceive that resolving their issues would take too long. While interesting, this channel is only applicable to apps that are made available publicly on an app store.…”

Section: Background and Related Workmentioning

confidence: 99%

Crowd-based requirements elicitation via pull feedback: method and case studies

Wouters¹,

Menkveld²,

Brinkkemper

et al. 2022

Requirements Eng

View full text Add to dashboard Cite

Crowd-based Requirements Engineering (CrowdRE) promotes the active involvement of a large number of stakeholders in RE activities. A prominent strand of CrowdRE research concerns the creation and use of online platforms for a crowd of stakeholders to formulate ideas, which serve as an additional input for requirements elicitation. Most of the reported case studies are of small size, and they analyze the size of the crowd, rather than the quality of the collected ideas. By means of an iterative design that includes three case studies conducted at two organizations, we present the CREUS method for crowd-based elicitation via user stories. Besides reporting the details of these case studies and quantitative results on the number of participants, ideas, votes, etc., a key contribution of this paper is a qualitative analysis of the elicited ideas. To analyze the quality of the user stories, we apply criteria from the Quality User Story framework, we calculate automated text readability metrics, and we check for the presence of vague words. We also study whether the user stories can be linked to software qualities, and the specificity of the ideas. Based on the results, we distill six key findings regarding CREUS and, more generally, for CrowdRE via pull feedback.

show abstract

Elicitation Revisited for More Inclusive Requirements Engineering

Tizard,

Rietz,

Blincoe

2024

Equity, Diversity, and Inclusion in Software Engineering

View full text Add to dashboard Cite

James Tizard, Tim Rietz, and Kelly BlincoeTo create inclusive software, development teams need to consider how they identify inclusive requirements for a software product. Requirements elicitation is the first stage in the process of developing the requirements of a software system. Elicitation is about describing the functionality, reliability, efficiency, and usability of the system to be developed, so that it suits the end users’ needs [12].Recent research has found that both traditional elicitation techniques (e.g., user interviews) and newer online crowd-based approaches may have challenges in gathering the views of a diverse set of users. In particular, there are significant challenges in eliciting requirements from users with cognitive disabilities, as well as ensuring that the full demographic spectrum (e.g., by gender, age, ethnicity) of a user base is adequately represented.This chapter discusses the motivations for more inclusive requirements elicitation and the challenges that need to be overcome and finally makes recommendations for both requirements engineering practitioners and researchers.

show abstract

Voice of the users: an extended study of software feedback engagement

Cited by 14 publications

References 28 publications

Test‐driven development, engagement in activity, and maintainability: An empirical study

Test‐driven development, engagement in activity, and maintainability: An empirical study

Crowd-based requirements elicitation via pull feedback: method and case studies

Elicitation Revisited for More Inclusive Requirements Engineering

Contact Info

Product

Resources

About