Tool support for traceable product evolution

Lago, Patricia; Niemelä, Eila; Vliet, Hans van

doi:10.1109/csmr.2004.1281428

Cited by 11 publications

(17 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The knowledge management system is based on REMAP [59], a web-based tool for capturing and maintaining traceability information. Another tool for managing traceability of product families was proposed in [37]. This approach is restricted to feature and product component maps and consists of an extension of a commercial software tool to allow the description of features in an unambiguous and manageable way, selection and management of features, tracing of cross-cutting features, and modelling newly developed and COTS components.…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

XTraQue: traceability for product line systems

Jirapanthong

Zisman

2007

Softw Syst Model

View full text Add to dashboard Cite

Section: Related Workmentioning

confidence: 99%

“…The use of traceability to support product line engineering has been advocated in [4,6,35,37,47,54,62,74]. In [4], the authors advocate that traceability is a key technology for product line infrastructure.…”

mentioning

confidence: 99%

XTraQue: traceability for product line systems

Jirapanthong

Zisman

2007

Softw Syst Model

View full text Add to dashboard Cite

“…Use case diagrams can be associated with use case documents; sequence diagrams implementing the use cases can be linked to the use case diagrams, and class diagrams can be linked to the sequence diagrams. A related approach has been proposed to achieve traceability in software product families [28], linking requirements, architecture, components, and source code. In both works, traceability is based mainly on explicitly created links.…”

Section: Tool Support For Traceabilitymentioning

confidence: 99%

Managing Variability Using Heterogeneous Feature Variation Patterns

Hammouda

Hautamäki

Pussinen

et al. 2005

Fundamental Approaches to Software Engineering

View full text Add to dashboard Cite

Abstract. Feature-driven variability is viewed as an instance of multidimensional separation of concerns. We argue that feature variation concerns can be presented as pattern-like entities -called feature variation patterns -cross-cutting heterogeneous artifacts. We show that a feature variation pattern, covering a wide range of artifact types from a feature model to implementation, can be used to manage feature-driven variability in a software development process. A prototype tool environment has been developed to demonstrate the idea, supporting the specification and use of heterogeneous feature variation patterns. We illustrate the idea with a small example taken from J2EE, and further study the practical applicability of the approach in an industrial product-line.

show abstract

“…View generation and tool support: As described in [16], we developed tool support for representing the knowledge about a software PF, and for supporting traceability from features to code. Further, we implemented an initial solution to view generation: to aid the stakeholder in defining his/her personalized views on the feature representations, we implemented filtering mechanisms that allow to select the featureand association types to be visualized.…”

Section: Classification Of Featuresmentioning

confidence: 99%

“…We defined a notation and developed associated tool support [16] fulfilling the requirements in the following way:…”

Section: Introductionmentioning

confidence: 99%

Observations from the Recovery of a Software Product Family

Lago

Vliet

2004

Software Product Lines

View full text Add to dashboard Cite

Abstract. The problem of managing the evolution of complex and large software systems is well known. Evolution implies reuse and modification of existing software artifacts, and this means that the related knowledge must be documented and maintained. This paper focuses on the evolution of software product families, although the same principles apply in other software development environments as well. We describe our experience gained in a case study recovering a family of six software products. We give an overview of the case study, and report a list of lessons learned, a list of implicit assumptions reconstructed during the case study, and some rules that we think are generally applicable. Our experience indicates that organizing architectural knowledge is a difficult issue. To properly serve the various uses of this knowledge, it needs to be organized along different dimensions. For effective use, tools are required. Our experience also indicates that, next to variability explicitly designed into the product family, there is a "variation creep", caused by different, and evolving, technical and organizational environments of the products. We propose to explicitly model invariabilities, next to variabilities, in software product lines to get a better grip on this variation creep.

show abstract

Tool support for traceable product evolution

Abstract: Abstract

Cited by 11 publications

References 14 publications

XTraQue: traceability for product line systems

XTraQue: traceability for product line systems

Managing Variability Using Heterogeneous Feature Variation Patterns

Observations from the Recovery of a Software Product Family

Contact Info

Product

Resources

About