Introducing Traceability to Product Lines

A model-driven traceability framework for software product lines

“…There exists a large body of knowledge related to metamodels for traceability [3,4,9,10,16,19,26,28,48,49,55]. A variety of approaches for storing traceability information are proposed: database schema [6], XML schema [26,49] or metamodels [19,28,46]. We choose an agnostic metamodel representation since we want to address traceability when aspect-orientation, model-driven development and software product line engineering are used in conjunction.…”

Handling Variability and Traceability over SPL Disciplines

“…Although diverse metamodels have been proposed in the literature (Anquetil et al, 2010;Bachmann et al, 2003;Bayer & Widen, 2001;Bühne et al, 2005;Moon et al, 2007;Sinnema et al, 2004;Streitferdt, 2001) in order to address variability and traceability aspects, they generally cover the SPL phases partially or do not treat such issues together through all the SPL disciplines. In this paper, we propose a metamodel which provides support for several SPL aspects, such as scoping, requirements, tests, and project and risk management.…”

Tool support for traceable product evolution

“…user manuals, test material). 1 Term map is defined as the representation of the whole or a part of an area. Representing features the application domain (or part of it), we use term feature map instead of feature graph to underline its role in providing traceability, navigation support and domain coverage.…”

“…This work provides an interesting solution to the problem of managing decisions/assumptions, which again is complementary to our work, as we focus on the relations between features, design solutions and implementation assets. Finally, [1] adds traceability support to the PuLSE method by defining a two step method: first, a general meta-model defines potential traces between model elements; second, the meta-model is specialized for a specific project, to express the project-specific types of traces. The method could be used to generate our three-level model.…”

“…When instead we add new features or modify an existing solution, we currently need to manually define/update all traces. The complexity of automatically supporting evolving features is that (1) to include a new feature in the PF FM we need to decide the feature category and its position in the FM; (2) to update the PF FM to trace product-specific feature solutions is just an implementation matter; instead, to trace the role played by the new feature in the associated Product CM, is again a semantic problem. E.g.…”