See this document in CiteSeerX!

Guiding Feature Asset Mining for Software Product Line Development  (Make Corrections)  
Thomas Eisenbarth, Daniel Simon



  Home/Search   Context   Related

 
View or download:
iste.unistuttgart.de/ps/...PLEES01.pdf
Cached:  PDF   PS.gz  PS  Image  Update  Help

From:  iste.unistuttgart.de/ps/bauha... (more)
(Enter author homepages)

Rate this article: (best)
  Comment on this article  
(Enter summary)

Abstract: Introduction Software product line architectures promise significant benefits over traditional architectures such as shorter time-to-market, shorter and cheaper development cycles, and higher exploitation of the reuse potential at hand. While the ideas and concepts of product lines are well suited for developing new products, it is not obvious if and how one can apply this technology in the presence of legacy software. Migrating legacy software systems to a product line provides ways for... (Update)

Active bibliography (related documents):   More   All
1.1:   Locating Features in Source Code - Eisenbarth, Koschke, Simon (2003)   (Correct)
0.4:   Concern Graphs: Finding and Describing Concerns - Robillard, Murphy (2002)   (Correct)
0.3:   RIPPLES: Tool for Change in Legacy Software - Chen (2001)   (Correct)

Similar documents based on text:   More   All
0.3:   Aiding Program Comprehension by Static and Dynamic.. - Eisenbarth, Koschke.. (2001)   (Correct)
0.3:   Data Exchange in Bauhaus - Czeranski, Eisenbarth, Kienle.. (2000)   (Correct)
0.2:   Feature-Driven Program Understanding Using Concept.. - Traces Thomas Eisenbarth   (Correct)

BibTeX entry:   (Update)

@misc{ eisenbarth-guiding,
  author = "Thomas Eisenbarth and Daniel Simon",
  title = "Guiding Feature Asset Mining for Software Product Line Development",
  url = "citeseer.ist.psu.edu/671391.html" }
Citations (may not include all citations):
91   Available httpwww (context) - Bauhaus, at et al. - 2001
21   Software Reconnaissance: Mapping Program Features to Code (context) - Wilde, Scully - 1995
17   PuLSE: A Methodology to Develop Software Product Lines (context) - Bayer, Flege et al. - 1999
17   Use of Software Architectures (context) - Bosch - 2000
12   Case Study of Feature Location Using Dependence Graph - Chen, Rajlich - 2000
10   Aiding Program Comprehension by Static and Dynamic Feature A.. - Eisenbarth, Koschke et al. - 2001
8   A Framework for Software Product Line Practice (context) - Northrop - 2001
6   Feature-Driven Program Understanding Using Concept Analysis .. (context) - Eisenbarth, Koschke et al. - 2001
5   A Case Study of Feature Location in Unstructured Legacy Fort.. (context) - Wilde, Buckellew et al. - 2001
3   Derivation of Feature-Component Maps by Means of Concept Ana.. (context) - Eisenbarth, Koschke et al. - 2001
2   Quantifying the Closeness between Program Components and Fea.. - Wong, Gokhale et al. - 2000
1   Herleitung der Feature-Komponenten-Korrespondenz mittels Beg.. (context) - Eisenbarth, Koschke et al. - 2000
1   Mining Existing Software Assets for Software Product Lines (context) - Bergey, O'Brien et al. - 2000
1   Transitioning Legacy Assets to a Product Line Architecture (context) - Bayer, Girard et al. - 1999
1   Can Legacy Systems Beget Product Lines (context) - Weiderman, Bergey et al. - 1998

Documents on the same site (http://www.iste.uni-stuttgart.de/ps/bauhaus/papers/):   More
Finding Components in a Hierarchy of Modules: a Step towards.. - Girard, Koschke (1997)   (Correct)
Hierarchical Re exion Models - Rainer Koschke Daniel   (Correct)
Feature-Driven Program Understanding Using Concept.. - Traces Thomas Eisenbarth   (Correct)

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC