Getting back to basics: Promoting the use of a traceability information model in practice
Getting back to basics: Promoting the use of a traceability information model in practice
复制标题
回到基础：在实践中推广可追溯信息模型的使用
DOI：
10.1109/tefse.2009.5069578
复制
发表时间：
2009
期刊：
影响因子：
--
通讯作者：
I. Philippow
中科院分区：
文献类型：
--
作者：
Patrick Mäder;O. Gotel;I. Philippow
人们普遍认为，如果您想在软件开发项目中实现和利用可追溯性的好处，那么遵循过程是一件好事。任何这样的过程的核心组成部分是可追溯性信息模型的定义和使用。这样的模型提供了关于那些要收集的软件开发工件和那些要建立的关系的指导，并且被设计为最终支持所需的项目分析。然而，在工业中，可追溯性仍然倾向于以相当临时的方式进行，结果不可预测。我们认为，这种情况的一个原因是，目前的软件开发工具提供很少的支持，从业者建立和使用定制的项目特定的可追溯性信息模型，没有它，即使是最简单的过程是有问题的实施和获得预期的好处。在本文中，我们突出了典型的决策，在创建一个基本的可追溯性信息模型，提出了一个简单的基于UML的表示其定义，并说明其核心作用的建模工具的上下文中。本文的目的是重新关注在实践中应用可追溯性信息模型的非常实用的方法，以鼓励更广泛的采用。
It is widely assumed that following a process is a good thing if you want to achieve and exploit the benefits of traceability on a software development project. A core component of any such process is the definition and use of a traceability information model. Such models provide guidance as to those software development artifacts to collect and those relations to establish, and are designed to ultimately support required project analyses. However, traceability still tends to be undertaken in rather ad hoc ways in industry, with unpredictable results. We contend that one reason for this situation is that current software development tools provide little support to practitioners for building and using customized project-specific traceability information models, without which even the simplest of processes are problematic to implement and gain the anticipated benefits from. In this paper, we highlight the typical decisions involved in creating a basic traceability information model, suggest a simple UML-based representation for its definition, and illustrate its central role in the context of a modeling tool. The intent of this paper is to re-focus attention on very practical ways to apply traceability information models in practice so as to encourage wider adoption.