A Metamodeling Approach to Tracing Variability between Requirements and Architecture in Software Product Lines

A model for tracing variability from features to product-line architectures: a case study in smart grids

“…[38] defined a Variabiliíy Trace Meíamodel íhaí connecís íwo meíamodels: a meíamodel for requiremenís and a meíamodel for archiíecíure. Ajila eí al.…”

Graph-based traceability: a comprehensive approach

“…However, it has to be noted that these metamodels focus on requirements traceability, thus neglecting traceability of other entities such as architecture components or source code fragments. Other approaches include tracing variability in requirements and architecture in the context of product line engineering [Moo07] and the usage of ontologies for traceability between source code and documentation [Wit07].…”

Handling Variability and Traceability over SPL Disciplines

“…A change in an artifact in a product line may lead to resultant changes in all products developed reusing such an artifact. Hence, it is necessary to define dependency relationships between the relevant artifacts to support consistent change integration (Moon et al, 2007).…”

“…It also based the metamodel in a set of requirements to document requirements variability. Moon et al (2007) introduced two metamodels representing domain requirements and domain architecture with variability, and the traceability between these artifacts are based upon the metamodel.…”

“…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.…”