论文标题
情绪智力在处理需求变化中的作用软件工程的变化
The Role of Emotional Intelligence in Handling Requirements Changes in Software Engineering
论文作者
论文摘要
背景：需求更改（RCS）在软件工程中不可避免。研究表明，情绪智力（EI）应与RC处理过程中的敏捷性和认知智能一起使用。目的：我们想研究RC处理过程中EI深入的作用。方法：我们对来自澳大利亚，新西兰，新加坡和斯里兰卡的十八位软件从业人员进行了社会技术扎根理论研究。调查结果：我们发现因果状况（软件从业人员处理RC），中间状况（工作方式），原因（意识到自己的情绪，意识到他人的情绪），直接后果（调节自己的情绪，管理情绪，管理关系），扩展后果，扩展的后果（维持生产力，设置和维持团队的目标和策略），并在策略中进行策略，并在策略中进行策略，并在策略中进行策略，并在策略中进行策略，并进行策略，并且需要行动，并且是策略，并在策略中进行策略，并且需要行动，并且是行动，并且是策略（策略），并且是在策略（策略），并且是在策略（策略），并且是在策略（策略），并且是在策略（策略），并且是在策略和策略（处理。我们还发现了协方差，策略与原因和直接后果共同融为一体，并轻松/难以执行策略与中间条件共同变化。结论：在RC处理过程中，开放和常规沟通是EI的关键。据我们所知，我们在本文中提出的框架是有关软件工程研究中EI的第一个理论框架。我们提供建议，包括针对意外情况的原因，直接后果和工作方式的形式的问题解决图表：在RC处理期间要考虑的软件从业人员的策略以及未来的研究方向。
Background: Requirements changes (RCs) are inevitable in Software Engineering. Research shows that emotional intelligence (EI) should be used alongside agility and cognitive intelligence during RC handling. Objective: We wanted to study the role of EI in-depth during RC handling. Method: We conducted a socio-technical grounded theory study with eighteen software practitioners from Australia, New Zealand, Singapore, and Sri Lanka. Findings: We found causal condition (software practitioners handling RCs), intervening condition (mode of work), causes (being aware of own emotions, being aware of others' emotions), direct consequences (regulating own emotions, managing relationships), extended consequences (sustaining productivity, setting and sustaining team goals), and contingencies: strategies (open and regular communication, tracking commitments and issues, and ten other strategies) of using EI during RC handling. We also found the covariances where strategies co-vary with the causes and direct consequences, and ease/ difficulty in executing strategies co-vary with the intervening condition. Conclusion: Open and regular communication is key to EI during RC handling. To the best of our knowledge, the framework we present in this paper is the first theoretical framework on EI in Software Engineering research. We provide recommendations including a problem-solution chart in the form of causes, direct consequences, and mode of work against the contingencies: strategies for software practitioners to consider during RC handling, and future directions of research.
