Table of Contents
Fetching ...

How do software practitioners perceive human-centric defects?

Vedant Chauhan, Chetan Arora, Hourieh Khalajzadeh, John Grundy

TL;DR

This study introduces human-centric defects (HCDs) as user-difference-driven software defects and investigates how practitioners perceive and manage them. Through a mixed-methods approach (survey of 50 practitioners and 10 in-depth interviews), it reveals gaps in awareness, a subjective nature of HCDs, and limitations in current defect-tracking tools. Key findings show usability as the dominant HCD category, substantial overlap with technical defects in root causes, and the pivotal roles of experience, communication, and organizational culture. The paper proposes a roadmap including taxonomy development, templates and checklists, end-user feedback integration, and tooling automation to improve HCD reporting and resolution, with implications for practice and future research in diverse software environments.

Abstract

Context: Human-centric software design and development focuses on how users want to carry out their tasks rather than making users accommodate their software. Software users can have different genders, ages, cultures, languages, disabilities, socioeconomic statuses, and educational backgrounds, among many other differences. Due to the inherently varied nature of these differences and their impact on software usage, preferences and issues of users can vary, resulting in user-specific defects that we term as `human-centric defects' (HCDs). Objective: This research aims to understand the perception and current management practices of such human-centric defects by software practitioners, identify key challenges in reporting, understanding and fixing them, and provide recommendations to improve HCDs management in software engineering. Method: We conducted a survey and interviews with software engineering practitioners to gauge their knowledge and experience on HCDs and the defect tracking process. Results: We analysed fifty (50) survey- and ten (10) interview- responses from SE practitioners and identified that there are multiple gaps in the current management of HCDs in software engineering practice. There is a lack of awareness regarding human-centric aspects, causing them to be lost or under-appreciated during software development. Our results revealed that handling HCDs could be improved by following a better feedback process with end-users, a more descriptive taxonomy, and suitable automation. Conclusion: HCDs present a major challenge to software practitioners, given their diverse end-user base. In the software engineering domain, research on HCDs has been limited and requires effort from the research and practice communities to create better awareness and support regarding human-centric aspects.

How do software practitioners perceive human-centric defects?

TL;DR

This study introduces human-centric defects (HCDs) as user-difference-driven software defects and investigates how practitioners perceive and manage them. Through a mixed-methods approach (survey of 50 practitioners and 10 in-depth interviews), it reveals gaps in awareness, a subjective nature of HCDs, and limitations in current defect-tracking tools. Key findings show usability as the dominant HCD category, substantial overlap with technical defects in root causes, and the pivotal roles of experience, communication, and organizational culture. The paper proposes a roadmap including taxonomy development, templates and checklists, end-user feedback integration, and tooling automation to improve HCD reporting and resolution, with implications for practice and future research in diverse software environments.

Abstract

Context: Human-centric software design and development focuses on how users want to carry out their tasks rather than making users accommodate their software. Software users can have different genders, ages, cultures, languages, disabilities, socioeconomic statuses, and educational backgrounds, among many other differences. Due to the inherently varied nature of these differences and their impact on software usage, preferences and issues of users can vary, resulting in user-specific defects that we term as `human-centric defects' (HCDs). Objective: This research aims to understand the perception and current management practices of such human-centric defects by software practitioners, identify key challenges in reporting, understanding and fixing them, and provide recommendations to improve HCDs management in software engineering. Method: We conducted a survey and interviews with software engineering practitioners to gauge their knowledge and experience on HCDs and the defect tracking process. Results: We analysed fifty (50) survey- and ten (10) interview- responses from SE practitioners and identified that there are multiple gaps in the current management of HCDs in software engineering practice. There is a lack of awareness regarding human-centric aspects, causing them to be lost or under-appreciated during software development. Our results revealed that handling HCDs could be improved by following a better feedback process with end-users, a more descriptive taxonomy, and suitable automation. Conclusion: HCDs present a major challenge to software practitioners, given their diverse end-user base. In the software engineering domain, research on HCDs has been limited and requires effort from the research and practice communities to create better awareness and support regarding human-centric aspects.
Paper Structure (34 sections, 1 equation, 11 figures, 3 tables)

This paper contains 34 sections, 1 equation, 11 figures, 3 tables.

Figures (11)

  • Figure 1: An example HCD reported in the OpenEMR GitHub Repository
  • Figure 2: Survey process
  • Figure 3: Interview process
  • Figure 4: Theme map for RQ1
  • Figure 5: Mean plot of technical skills of the respondents (in Surveys)
  • ...and 6 more figures