From custom applications to domain-specific frameworks
Communications of the ACM
Object-oriented framework and product lines
Proceedings of the first conference on Software product lines : experience and research directions: experience and research directions
Software product lines: practices and patterns
Software product lines: practices and patterns
ACM Transactions on Software Engineering and Methodology (TOSEM)
An Object-Oriented Language-Database Integration Model: The Composition-Filters Approach
ECOOP '92 Proceedings of the European Conference on Object-Oriented Programming
Resolving feature convolution in middleware systems
OOPSLA '04 Proceedings of the 19th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Variability management with feature-oriented programming and aspects
Proceedings of the 12th ACM SIGSOFT twelfth international symposium on Foundations of software engineering
Horizontal decomposition of Prevayler
CASCON '05 Proceedings of the 2005 conference of the Centre for Advanced Studies on Collaborative research
A pattern to design crosscutting frameworks
Proceedings of the 2008 ACM symposium on Applied computing
IEEE Transactions on Software Engineering
An approach to design crosscutting framework families
Proceedings of the 2008 AOSD workshop on Aspects, components, and patterns for infrastructure software
Frameworks Generate Domain-Specific Languages: A Case Study in the Multimedia Domain
IEEE Transactions on Software Engineering
Improving extensibility of object-oriented frameworks with aspect-oriented programming
ICSR'06 Proceedings of the 9th international conference on Reuse of Off-the-Shelf Components
Hi-index | 0.00 |
Frameworks are tools that promote the reuse of pieces of software within specific domains. An intrinsic property of frameworks is the large amount of intertwined code found across its several modules. This configures an architecture whose modules can hardly be decoupled. Consequently, an application derived from a framework usually carries on the full framework architecture, irrespective of the subset of application requirements. This compromises the maintainability, evolution and reusability of both framework and applications derived from it. To deal with this problem, this paper introduces the concept of Framework Product Lines (FPL). In a FPL, each member - or configuration -- is a framework that contains only a subset of the FPL features according to the application requirements and rules that constrain their composition. Thus, this paper presents the framework product lines concept and shows its use for evolving an application framework towards FPL. Results show preliminary gains in terms of reusability and maintainability in both evolved framework and applications derived from it.