Andres Yie
Rubby Casallas
ABSTRACT
A Model-Driven Software Product Line (MD-SPL) uses metamodels, models, and transformations to create a family of products using a Model Refinement Line (MRL). However, an MD-SPL must evolve and provide mechanisms to add new crosscutting concerns, such as security or logging, to the applications. Our problem is that we want to preserve and reuse the original MRL. In this paper, we present the challenges associated with this problem. We illustrate them by evaluating different model-driven approaches to add crosscutting concerns into an application using high-level aspects. Furthermore, we propose an approach to add crosscutting concerns as early aspects and to preserve the original MRL. This approach adds a new MRL that refines a high-level model of the concern. This high-level model is related with the high-level application model in the original MRL. The refinement of the application model and the concern model proceeds in parallel. The presented approach is a work in progress and requires us to tackle several challenges in order to implement and validate the proposal.
- P. Clements, L. Northrop, Software Product Lines: Practices and Patterns, 2002.Google Scholar
- D. C. Schmidt, Guest Editor's Introduction: Model-Driven Engineering, Computer, p25-p31, February 2006, Google ScholarDigital Library
- K. Garcés, C. Parra, H. Arboleda, A. Yie, R. Casallas, Variability Management in a Model-Driven Software Product Line, Revista Avances en Sistemas e Informática, Vol. 4 No. 2, 2007Google Scholar
- AOSD: Aspect-Oriented Software Development Community website: http://www.aosd.net/Google Scholar
- F. Klar, A. Königs, A. Schürr, Model transformation in the large, Proceedings of the 6th joint meeting of the european software engineering conference, Dubrovnik, Croatia, 2007 Google ScholarDigital Library
- D. Basin, J. Doser, T. Lodderstedt, Model-driven security: From UML models to access control infrastructures, ACM Transactions on Software Engineering and Methodology (TOSEM) Vol. 15, No. 1 p39--p91, 2006 Google ScholarDigital Library
- J. Fabry, Modularizing Advanced Transaction Management, Phd Dissertation, Vrije Universiteit Brussel, 2005Google Scholar
- M. A. Cibrán, Connecting High-Level Business Rules with Object-Oriented Applications: An approach using Aspect-Oriented Programming and Model-Driven Engineering, Phd Dissertation, Vrije Universiteit Brussel, 2007Google Scholar
- J. Fabry, T. Cleenewerck, Aspect-oriented domain-specific languages for advanced transaction management, Proceedings of International Conference on Enterprise Information Systems, Miami, USA, 2005Google Scholar
- D. Rebernak, M. Mernik, H. Wu, J. Gray, Domain-Specific Aspect Languages for Modularizing Crosscutting Concerns in Grammars, First Domain-Specific Aspect Languages Workshop, Portland, USA, 2006Google Scholar
- AspectJ website: http://www.eclipse.org/aspectj/Google Scholar
Index Terms
- Multi-step concern refinement
Recommendations
A generic weaver for supporting product lines
EA '08: Proceedings of the 13th international workshop on Early AspectsAspects have gained attention in the earlier steps of the software life-cycle leading to the creation of numerous ad-hoc Aspect-Oriented Modeling (AOM) approaches. These approaches mainly focus on architecture diagrams, class diagrams, state-charts, ...
Model-driven development for early aspects
Currently, non-functional requirements (NFRs) consume a considerable part of the software development effort. The good news is that most of them appear time and again during system development and, luckily, their solutions can be often described as a ...
COMPASS: composition-centric mapping of aspectual requirements to architecture
Transactions on aspect-oriented software development IVCurrently there are several approaches available for aspect-oriented requirements engineering and architecture design. However, the relationship between aspectual requirements and architectural aspects is poorly understood. This is because aspect-...
Comments