ACM Home Page
Please provide us with feedback. Feedback
Implementing product line variabilities
Full text PdfPdf (213 KB)
Source Symposium on Software Reusability archive
Proceedings of the 2001 symposium on Software reusability: putting software reuse in context table of contents
Toronto, Ontario, Canada
Pages: 109 - 117  
Year of Publication: 2001
ISBN:1-58113-358-8
Also published in ...
Authors
Critina Gacek  Centre for Software Reliability, Department of Computing Science, University of Newcastle, NE1 7RU Newcastle upon Tyne, United Kingdom
Michalis Anastasopoules  Fraunhofer Institute for Experimental Software Engineering, Sauerwiesen 6, D-67661 Kaiserslautern, Germany
Sponsor
SIGSOFT: ACM Special Interest Group on Software Engineering
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 12,   Downloads (12 Months): 129,   Citation Count: 11
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/375212.375269
What is a DOI?

ABSTRACT

Software product lines have numerous members. Thus, a product line infrastructure must cover various systems. This is the significant difference to usual software systems and the reason for additional requirements on the various assets present during software product line engineering. It is imperative that they support the description of the product line as a whole, as well as its instantiation for the derivation of individual products. Literature has already addressed how to create and instantiate generic product line assets, such as domain models and architectures to generate instance specific ones [1, 2, 3], yet little attention has been given on how to actually deal with this genericity at the code level. This paper addresses the issue of handling product line variability at the code level. To this end various implementation approaches are examined with respect to their use in a product line context.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
Michalis Anastasopoulos, Joachim Bayer, Oliver Flege and Cristina Gacek, A Process for Product Line Architecture Creation and Evaluation PuLSE-DSSA - Version 2.0, Fraunhofer IESE Report No. 038.00/E, June 2000
 
2
Cristina Gacek and Anton Vukovic, "Vital: Representing Software Reference Architectures," in Proceedings of the Fourth International Software Architecture Workshop (ISAW-4), Limerick, Ireland, pp. 105-110, June 2000.
 
3
Joachim Bayer, Cristina Gacek, Dirk Muthig and Tanya Widen, "PuLSE-I: Deriving Instances from a Product Line Infrastructure," in Proceedings of the Seventh IEEE International Conference and Workshop on the Engineering of Computer-Based Systems (ECBS 2000), Edinburgh, Scotland, pp. 237-245, April 2000.
 
4
 
5
David C. Sharp, "Containing and Facilitating Change Via Object Oriented Tailoring Techniques," to appear in Proceedings of The First Software Product Line Conference Denver, Colorado, August, 2000
 
6
Mikael Svahnberg, Variability in Evolving Software Product Lines, Licentiate thesis, Blekinge Institute of Technology, Department of Software Engineering and Computer Science, Karlskrona, Sweden, 2000
 
7
Mira Mezini, Variational Object Oriented Programming, Ph.D. Dissertation, University of Siegen, Germany, 1997
 
8
 
9
Oxford University Computing Laboratory, Programming Tools Group, Intentional Programming Project (http://web.com-lab. ox.ac.uk/oucl/research/areas/progtools/intentional.htm)
 
10
 
11
Gregor Kiczales et al, "Aspect Oriented Programming", Springer-Verlag, 1997, available under http:// www.parc.xerox.com/csl/groups/sda/publications/papers/Kiczales-ECOOP97/
 
12
Homepage of the Subject-oriented Research Project, IBM, Thomas J. Watson Research Center, Yorktown Heights, NY, see http://www.research.ibm.com/sop
 
13
Harold Ossher and Peri Tarr, "Operation-Level Composition: A Case in (Join) Point," in Proceedings of ECOOP 1998 workshop on Aspect-Oriented Programming, Finland, pp 116-120, 1998
 
14
 
15
Paul G. Basset, Framing Software Reuse, Yourdon Press Computing Series, 1997
 
16
 
17
Xavier Pacheco, The Builder Pattern, available under http:// www.delphimag.com
 
18
 
19
Oliver Lewis, Performance Issues of Variability Design in Embedded System Application Families, Ph.D. Dissertation, November, 2000, available under http://www.dcs.napier.ac.uk/ ~bill/oli/

CITED BY  11

Collaborative Colleagues:
Critina Gacek: colleagues
Michalis Anastasopoules: colleagues