Framework for version control & dependency link of components & products in software product line
AIC'04 Proceedings of the 4th WSEAS International Conference on Applied Informatics and Communications
Systematizing pragmatic software reuse
ACM Transactions on Software Engineering and Methodology (TOSEM)
| Hi-index | 0.00 |
The study of software product lines addresses the issues of engineering software system families, or collections of similar software systems [1, 2, 3]. The objective of a software product line is to reduce the overall engineering effort required to produce a collection of similar systems by capitalizing on the commonality among the systems and by formally managing the variation among the systems. This is a classic software reuse problem [4].The primary focus of software product line research has been on domain analysis and modeling, architecture modeling, software reuse repositories, generators, and process definition [5, 6]. In contrast, for engineering single systems, these technologies and techniques provide significant value, while for engineering software product lines the conventional wisdom suggests they are essential.We hypothesize, however, that domain analysis, architecture modeling, software reuse repositories, generators, and process definition are simply compensating for a void in the existing software engineering technology space and that this void can be filled by a more simple, powerful, and concise technology for engineering software product lines. This new technology then redefines the status of domain analysis and the other existing technologies so that they have the same status in software product line development that they do in single system development - valuable engineering technologies but not necessarily requisite.