Traceability in Agile Projects
Traceability in Agile Projects
复制标题
敏捷项目中的可追溯性
DOI：
--
复制
发表时间：
2012
期刊：
影响因子：
--
通讯作者：
J. Cleland
中科院分区：
文献类型：
--
作者：
J. Cleland
敏捷方法正日益成为软件开发的主流方法。它们的特点是具有频繁交付的短迭代、测试驱动的开发、轻量级文档以及与客户的频繁交互。也许不足为奇的是，在敏捷项目中，可追溯性通常被认为是不必要的，因此是不需要的。这是由于创建和维护可追溯性链接的可感知开销，以及敏捷开发人员对项目有足够的了解，可以在没有先前定义的可追溯性链接支持的情况下实现变更的假设。本章探讨了在广泛的敏捷项目中进行跟踪的挑战、好处、技术和过程。
Agile methods are becoming an increasingly mainstream approach to software development. They are characterized by short iterations with frequent deliverables, test-driven development, lightweight documentation, and frequent interactions with the customer. Perhaps unsurprisingly, traceability is often seen as unnecessary and therefore unwanted in agile projects. This is due to the perceived overhead of creating and maintaining traceability links and the assumption that agile developers have sufficient understanding of a project to implement a change without the support of previously defined traceability links. This chapter explores the challenges, benefits, techniques, and processes of tracing across a broad spectrum of agile projects.