variability in the architecture models: <<optional>>,
<<variationPoint>> and <<variant>> stereotypes
designate respectively optional, variation points (and
its sub-classes), and variant classes (Clauß, 2001).
Finally, we have already mentioned the works
of Sochos (Sochos et al., 2004), the FORM method
(Kang et al., 1998), the generative approach of
Czarnecky (Czarnecki & Eisenecker, 2000), or the
RSBE method (Griss et al., 1998) as references in
order to populate the feature pattern catalog.
5 CONCLUSIONS
The main contribution of this article is the
identification of patterns in the feature models and
the mapping of these patterns with the correspondent
architectural diagrams. The feature patterns catalog
allows the automated creation of traceability links
between the product line feature and the
architectural models, consequently improving the
product derivation process.
Our approach to product lines is based on the
MDE paradigm, aiming to automate many of the
phases of product line development. In particular
and using the proposed catalog, the UML domain
models can be obtained from feature models using
QVT pattern transformations (though these models
must be manually completed). The implementation
of the transformations as part of a conventional IDE
tool facilitates the work of the product line
developers. And, using its configuration capabilities,
the tool is also useful for the developer in charge of
deriving the final products. A first experience has
allowed the contrast with reality and the obtained
results are encouraging.
As future work, we consider an alternative
configuration process. The design level (instead of
fully implemented) packages can be merged into a
monolithic model (using existing MDE tools). The
resulting (platform independent) model will be used
as input to code generators tools. These tools are
precisely intended to generate the platform specific
models and the final code. We are evaluating some
of the best known tools in order to assess the
practical possibilities of this product line and MDE
alliance.
ACKNOWLEDGEMENTS
This work has been supported by the Junta de
Castilla y León (project VA018A07) and Spanish
MICIINN (project TIN2008-05675).
REFERENCES
Antkiewicz, M., & Czarnecki, K. (2004). Feature
modeling plugin for Eclipse. OOPSLA’04 Eclipse
technology exchange workshop.
Bosch, J. (2000). Design & Use of Software Architectures.
Adopting and Evolving a Product-Line Approach.
Addison-Wesley.
Clauß, M. (2001). Generic modeling using Uml extensions
for variability. Workshop on Domain Specific Visual
Languages at OOPSLA.
Czarnecki, K., & Eisenecker, U. W. (2000). Generative
Programming: Methods, Tools, and Applications.
Addison-Wesley.
Gomaa, H. (2000). Object Oriented Analysis and
Modeling for Families of Systems with UML. IEEE
International Conference for Software Reuse (ICSR6),
(pp. 89–99).
Griss, M. L., Favaro, J., & d'Alessandro, M. (1998).
Integrating feature modeling with the RSEB.
Proceedings of the Fifth International Conference on
Software Reuse, (pp. 76-85).
Halmans, G., & Pohl, K. (2003). Communicating the
Variability of a Software-Product Family to
Customers. Journal of Software and Systems
Modeling , 15--36.
Jacobson, I., Griss, M., & Jonsson, P. (1997). Software
Reuse. Architecture, Process and Organization for
Business Success. ACM Press. Addison Wesley
Longman.
Kang, K. C., Kim, S., Lee, J., & Kim, K. (1998). FORM:
A Feature-Oriented Reuse Method with Domain-
Specific Reference Architectures. Annals of Software
Engineering , 143-168.
Kang, K., Cohen, S., Hess, J., Nowak, W., & Peterson, S.
(1990). Feature-Oriented Domain Analysis (FODA)
Feasibility Study. Technical Report, CMU/SEI-90-
TR-21, Software Engineering Institute (Carnegie
Mellon), Pittsburgh, PA 15213.
Laguna, M. A., González-Baixauli, B., & Marqués, J. M.
(2007). Seamless Development of Software Product
Lines: Feature Models to UML Traceability.
GPCE 07.
Laguna, M. A. & González-Baixauli, B (2008). Feature
Patterns and Product Line Model Transformations.
DSDM’08.
Lau, S. (2006). Domain Analysis of E-Commerce Systems
Using Feature-Based Model Templates”, . MASc
Thesis, ECE Department, University of Waterloo,
Canada.
Schobbens, P.-Y., Heymans, P., & Trigaux, J.-C. (2006).
Feature diagrams: A survey and a formal semantics.
RE , 136–145.
Sochos, P., Philippow, I., & Riebish., M. (2004). Feature-
oriented development of software product lines:
mapping feature models to the architecture. En LNCS
3263 (pp. 138-152).
Yu, Y., Lapouchnian, A., Leite, J., & Mylopoulos, J.
(2008). Configuring Features with Stakeholder Goals.
ACM SAC RE Track.
ICSOFT 2009 - 4th International Conference on Software and Data Technologies
298