Understanding Undesirable Attributes of Requirements Engineers: Insights from Practitioners

2026-05-31

AI Summary

This study addresses detrimental traits among requirements engineers that impede collaboration and project success. Employing a mixed-methods approach—integrating surveys and semi-structured interviews, complemented by qualitative data analysis and concept mapping—the research systematically identifies 17 critical negative attributes for the first time. These attributes are innovatively categorized into four dimensions: communication, domain knowledge, personality, and technical knowledge, forming a structured and visual conceptual map. The findings not only fill an empirical gap in reflective competence assessment within requirements engineering but also offer practitioners an actionable framework for self-improvement and team capability development.

Abstract

Context. The characteristics of software professionals have been widely investigated in the literature. However, limited attention has been given to undesirable attributes in Requirements Engineering, despite the strong dependence of this activity on stakeholder interaction and collaboration. Objectives. This study investigates the undesirable attributes of requirements engineers' hat may hinder collaboration and project success. Method. We surveyed software practitioners to identify these attributes and conducted interviews to gather supporting evidence. Results. Seventeen undesirable attributes were identified, grouped into four categories (communication issues, lack of domain knowledge, personality, and lack of technical knowledge), and organized into conceptual maps. Conclusion. The maps help requirements engineers reflect on and improve their professional practice by recognizing traits that may hinder collaboration and project outcomes.

Problem

• Requirements Engineering
• undesirable attributes
• collaboration
• software practitioners
• professional characteristics

Innovation

• undesirable attributes
• requirements engineering
• collaboration barriers
• conceptual mapping
• software practitioners