arXivDaily arXiv每日学术速递 周一至周五更新
arXiv 2304.02702cs.SE
收藏

需求工程中的人为错误管理:我们应该修复人、过程还是环境?

Human Error Management in Requirements Engineering: Should We Fix the People, the Processes, or the Environment?

Sweta Mahaju, Jeffrey C. Carver, Gary L. Bradshaw

AI总结:

本文通过对需求工程从业者调查的定性分析,开发了人为错误预防与缓解策略分类法,发现超50%策略需改变过程,为该领域研究提供了系统基础。

摘要:

背景:软件开发以人为中心,容易受到人为错误的影响。人为错误是人类思维过程中的错误。为了确保软件质量,从业者必须了解如何管理这些人为错误。组织经常改变需求工程过程,以防止人为错误发生或减轻这些错误发生时造成的危害。尽管其他学科对人为错误管理有研究,但针对软件工程,特别是需求工程中人为错误预防与缓解的研究仍然有限。软件工程的研究未能提供关于哪些类型的改变在需求工程中最有效的有力结果。目标:本文的目标是基于需求工程专业人员的数据,开发一个人为错误预防与缓解策略的分类法。方法:我们对两项关于需求工程实践的从业者调查进行了定性分析,以识别和分类人为错误预防与缓解策略。结果:我们根据人为错误管理策略主要影响的是人、过程还是环境,将其组织成一个分类法。在每个高级类别中,我们进一步将策略组织为低级类别。超过50%的报告策略需要改变过程,23%需要改变环境,21%需要改变人,其余5%过于模糊无法分类。此外,超过50%的策略侧重于管理活动。结论:人为错误管理分类法为需求工程中人为错误预防与缓解策略提供了系统的分类和组织。这种系统的组织为后续研究提供了基础。

英文摘要:

Context: Software development is human-centric and vulnerable to human error. Human errors are errors in the human thought process. To ensure software quality, practitioners must understand how to manage these human errors. Organizations often change the requirements engineering process to prevent human errors from occurring or to mitigate the harm caused when those errors do occur. While there are studies on human error management in other disciplines, research on the prevention and mitigation of human errors in software engineering, and requirements engineering specifically, are limited. The software engineering studies do not provide strong results about the types of changes that are most effective in requirements engineering. Objective: The goal of this paper is to develop a taxonomy of human error prevention and mitigation strategies based on data from requirements engineering professionals. Method: We performed a qualitative analysis of two practitioner surveys on requirements engineering practices to identify and classify strategies for the prevention and mitigation of human errors. Results: We organized the human error management strategies into a taxonomy based on whether they primarily affect People, Processes, or the Environment. Inside each high-level category, we further organized the strategies into low-level classes. More than 50% of the reported strategies require a change in Process, 23% require a change in Environment, 21% require a change in People, with the remaining 5% too ambiguous to classify. In addition, more than 50\% of the strategies focus on Management activities. Conclusions: The Human Error Management Taxonomy provides a systematic classification and organization of strategies for prevention and mitigation of human errors in requirements engineering. This systematic organization provides a foundation upon which research can build.

机构、总结、中文摘要均由AI分析而来,可能存在错误,请以论文正文为准。

↑