ACM Home Page
Please provide us with feedback. Feedback
Model-driven derivation of product architectures
Full text PdfPdf (780 KB)
Source
Automated Software Engineering archive
Proceedings of the twenty-second IEEE/ACM international conference on Automated software engineering table of contents
Atlanta, Georgia, USA
POSTER SESSION: Posters table of contents
Pages 469-472  
Year of Publication: 2007
ISBN:978-1-59593-882-4
Authors
Goetz Botterweck  University of Limerick, Limerick, Ireland
Liam O'Brien  National ICT Australia, Canberra, Australia
Steffen Thiel  University of Limerick, Limerick, Ireland
Sponsors
ACM: Association for Computing Machinery
SIGACT: ACM Special Interest Group on Algorithms and Computation Theory
SIGSOFT: ACM Special Interest Group on Software Engineering
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 15,   Downloads (12 Months): 115,   Citation Count: 1
Additional Information:

abstract   references   cited by   index terms   review   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/1321631.1321711
What is a DOI?

ABSTRACT

Product Derivation is one of the central activities in Software Product Lines (SPL). One of the main challenges of the process of product derivation is dealing with complexity, which is caused by the large number of artifacts and dependencies between them. Another major challenge is maximizing development efficiency and reducing time-to-market, while at the same time producing high quality products. One approach to overcome these challenges is to automate the derivation process. To this end, this paper focuses on one particular activity of the derivation process; the derivation of the product-specific architecture and describes how this activity can be automated using a model-driven approach. The approach derives the product-specific architecture by selectively copying elements from the product-line architecture. The decision, which elements are included in the derived architecture, is based on a product-specific feature configuration. We present a prototype that implements the derivation as a model transformation described in the Atlas Transformation Language (ATL). We conclude with a short overview of related work and directions for future research


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
ATL Home page. http://www.eclipse.org/m2m/atl/
 
2
xADL 2.0. http://www.isr.uci.edu/projects/xarchuci/
 
3
 
4
Czarnecki, K. and Antkiewicz, M. Mapping Features to Models: A Template Approach Based on Superimposed Variants. GPCE'05. 422--437.
 
5
Czarnecki, K. and Eisenecker, U. W. Generative programming. Addison-Wesley, 2000.
 
6
Czarnecki, K., Helsen, S. and Eisenecker, U. Formalizing Cardinality-based Feature Models and their Specialization. Software Process Improvement and Practice (Best papers from SPLC04), 10 (1). 7--29.
 
7
 
8
 
9
Kang, K., Cohen, S., Hess, J., Novak, W. and Peterson, S. Feature-Oriented Domain Analysis (FODA) Feasibility Study, SEI, Carnegie Mellon University, 1990.
 
10
OMG. UML 2.0 Superstructure Specification, 2005. http://www.omg.org/cgi-bin/doc?formal/05-07-04
 
11
 
12
pure-systems GmbH Variant Management. http://www.pure-systems.com/Variant_Management.49.0.html
 
13
SAE The SAE AADL Standard Info Site. http://www.aadl.info/
 
14
Wagelaar, D. MDE Case Studies, 2007. http://ssel.vub.ac.be/ssel/research:mdd:casestudies



REVIEW

"Mario Kupries : Reviewer"

Software product line engineering (SPEL) seeks to reduce time-to-market development as well as platform and mass customization of software-intensive systems. Under SPEL, the automation of product-specific architecture derivation is the major engin  more...

Collaborative Colleagues:
Goetz Botterweck: colleagues
Liam O'Brien: colleagues
Steffen Thiel: colleagues