Jorge Barreiros
ABSTRACT
Implementation of feature-oriented systems is typically made by creating an admissible configuration, according to a specified feature diagram, that dictates what artifacts are to be composed to create the desired solution. These artefacts are typically grouped according to the feature they concern. However, some artefacts may be related not to a specific feature, but to a combination of them. Also, multiple alternate implementations of a single feature may exist, and the preferred one may be dependent on the specific configuration that is being composed. We propose a graphic model to represent configuration knowledge that is able to address such concerns.
- "Pure::Variants (http://www.pure-systems.com)".Google Scholar
- D. Batory, "Feature-Oriented Programming and the AHEAD Tool Suite," in 26th International Conference on Software Engineering, 2004. Google ScholarDigital Library
- K. Czarnecki and M. Antkiewicz, "Mapping Features to Models: A Template Approach Based on Superimposed Variants," in 4th International Conference on Generative Programming and Component Engineering (GPCE) Tallin, Estonia, 2005. Google ScholarDigital Library
- P. Jayaraman, J. Whittle, A. M. Elkhodary, and H. Gomaa, "Model Composition in Product Lines and Feature Interaction Detection using Critical Pair Analysis" in 10th International Conf. on Model Driven Engineering Languages and Systems (MoDELS 2007) Nashville, 2007. Google ScholarDigital Library
- J. Kienzle, W. A. Abed, and J. Klein, "Aspect-Oriented Multi-View Modeling," in AOSD'09 Charlottesville, Virginia, USA, 2009. Google ScholarDigital Library
- J. Barreiros and A. Moreira, "Reusable Model Slices," in 14th International Workshop on Aspect-Oriented Modeling Denver, 2009.Google Scholar
- P. Borba, "Software Product Line Refactoring tutorial," in GTTSE'09 Summer School Braga, Portugal, 2009.Google Scholar
- E. Figueiredo, N. Cacho, C. SantíAnna, M. Monteiro, U. Kulesza, A. Garcia, S. Soares, F. Ferrari, S. Kan, and F. Filho, "Evolving software product lines with aspects: An empirical study on design stability," in ICSE New York, USA, 2008. Google ScholarDigital Library
- K. Czarnecki and U. Eisenecker, Generative Programming: Methods, Tools, and Applications: Addison-Wesley Professional, 2000. Google ScholarDigital Library
- K. Pohl, G. Böckle, and F. v. d. Linden, Software Product Line Engineering: Springer, 2005. Google ScholarDigital Library
- "AMPLE Project Webpage (www.ample-project.net)," 2009.Google Scholar
Index Terms
- A model-based representation of configuration knowledge
Recommendations
Verifying feature-based model templates against well-formedness OCL constraints
GPCE '06: Proceedings of the 5th international conference on Generative programming and component engineeringFeature-based model templates have been recently proposed as a approach for modeling software product lines. Unfortunately, templates are notoriously prone to errors that may go unnoticed for long time. This is because such an error is usually exhibited ...
Configuration Knowledge Representation Using UML/OCL
UML '02: Proceedings of the 5th International Conference on The Unified Modeling LanguageToday's economy is exhibiting a growing trend towards highly specialized solution providers cooperatively offering configurable products and services to their customers. In this context, knowledge based configurators which support the configuration of ...
Feature dependencies as change propagators
ContextA Software Product Line (SPL) is a set of software systems that share common functionalities, so-called features. When features are related, we consider this relation a feature dependency. Whenever a new feature is added, the presence of feature ...
Reviews
Vladimir Stantchev
Barreiros and Moreira describe a graphical model for the representation of configuration knowledge-"graphical" means that you should not expect any formal definitions. The paper deals with feature descriptions and the differences between a model and an implementation, and proposes a model that can help match them. The model presented is rather sketchy, and there are no references for the definitions of the notations. In fact, it is more of a notation than a model; it appears to be some type of unified modeling language (UML) class diagram with its standard relations: association, composition, and inheritance. Section 4, "Related Work," discusses only a small subset of available works and fails to represent the state of the art. The paper's motivation is unclear, since it lacks a discussion of the benefits of the proposed model as compared to standard UML techniques. Furthermore, the general applicability of the notation presented is not discussed, and there is no evaluation part to back the proposed model. Overall, it is impossible to evaluate the model with regard to its applicability and correctness. The presentation of the model is very brief, and there is little new information to interest readers familiar with UML and object orientation. Online Computing Reviews Service
Access critical reviews of Computing literature here
Become a reviewer for Computing Reviews.
Comments