首页> 外文期刊>Computers in Human Behavior >A systematic literature review on agile requirements engineering practices and challenges
【24h】

A systematic literature review on agile requirements engineering practices and challenges

机译:关于敏捷需求工程实践和挑战的系统文献综述

获取原文
获取原文并翻译 | 示例

摘要

Unlike traditional software development methods, agile methods are marked by extensive collaboration, i.e. face-to-face communication. Although claimed to be beneficial, the software development community as a whole is still unfamiliar with the role of the requirements engineering practices in agile methods. The term "agile requirements engineering" is used to define the "agile way" of planning, executing and reasoning about requirements engineering activities. Moreover, not much is known about the challenges posed by collaboration-oriented agile way of dealing with requirements engineering activities. Our goal is to map the evidence available about requirements engineering practices adopted and challenges faced by agile teams in order to understand how traditional requirements engineering issues are resolved using agile requirements engineering. We conducted a systematic review of literature published between 2002 and June 2013 and identified 21 papers, that discuss agile requirements engineering. We formulated and applied specific inclusion and exclusion criteria in two distinct rounds to determine the most relevant studies for our research goal. The review identified 17 practices of agile requirements engineering, five challenges traceable to traditional requirements engineering that were overcome by agile requirements engineering, and eight challenges posed by the practice of agile requirements engineering. However, our findings suggest that agile requirements engineering as a research context needs additional attention and more empirical results are required to better understand the impact of agile requirements engineering practices e.g. dealing with non-functional requirements and self-organising teams. (C) 2014 Elsevier Ltd. All rights reserved.
机译:与传统的软件开发方法不同,敏捷方法的特点是广泛的协作,即面对面的交流。尽管自称是有益的,但整个软件开发社区仍然不熟悉需求工程实践在敏捷方法中的作用。术语“敏捷需求工程”用于定义需求工程活动的计划,执行和推理的“敏捷方式”。而且,对于面向协作的敏捷方法处理需求工程活动所带来的挑战知之甚少。我们的目标是收集有关采用的需求工程实践和敏捷团队面临的挑战的可用证据,以了解如何使用敏捷需求工程解决传统的需求工程问题。我们对2002年至2013年6月之间发表的文献进行了系统回顾,确定了21篇讨论敏捷需求工程的论文。我们在两个不同的回合中制定并应用了具体的纳入和排除标准,以确定与我们的研究目标最相关的研究。审查确定了17种敏捷需求工程实践,5种可追溯到传统需求工程的挑战(敏捷需求工程克服了这些挑战)以及8种挑战,这些需求是敏捷需求工程实践所提出的。但是,我们的发现表明,将敏捷需求工程作为研究背景需要更多的关注,并且需要更多的经验结果才能更好地理解敏捷需求工程实践的影响,例如:处理非功能性需求和自组织团队。 (C)2014 Elsevier Ltd.保留所有权利。

著录项

相似文献

  • 外文文献
  • 中文文献
  • 专利
获取原文

客服邮箱:kefu@zhangqiaokeyan.com

京公网安备:11010802029741号 ICP备案号:京ICP备15016152号-6 六维联合信息科技 (北京) 有限公司©版权所有
  • 客服微信

  • 服务号