An intelligent tool for re-engineering software modularity
ICSE '91 Proceedings of the 13th international conference on Software engineering
SAAM: a method for analyzing the properties of software architectures
ICSE '94 Proceedings of the 16th international conference on Software engineering
Managing Domain-Specific, Product-Line Development
IEEE Software
A Cliche'-Based Environment to Support Architectural Reverse Engineering
ICSM '96 Proceedings of the 1996 International Conference on Software Maintenance
Finding Components in a Hierarchy of Modules: a Step towards Architectural Understanding
ICSM '97 Proceedings of the International Conference on Software Maintenance
Multi-Valued Constant Propagation for the Reengineering of User Interfaces
ICSM '93 Proceedings of the Conference on Software Maintenance
A metric-based approach to detect abstract data types and state encapsulations
ASE '97 Proceedings of the 12th international conference on Automated software engineering (formerly: KBSE)
WCRE '97 Proceedings of the Fourth Working Conference on Reverse Engineering (WCRE '97)
Using Visualization for Architectural Localization and Extraction
WCRE '97 Proceedings of the Fourth Working Conference on Reverse Engineering (WCRE '97)
Feature-oriented re-engineering of legacy systems into product line assets: a case study
SPLC'05 Proceedings of the 9th international conference on Software Product Lines
Hi-index | 0.00 |
The product line for software systems (PL) approach has been touted recently as one of the most promising development approach for gains in product quality, time to market and cost reduction. The approach is complex and must be tailorable to situations in which its characteristics may be of interest for adoption within a development environment. We first present in this short position paper a succinct overview of the main entry points (context) for PL adoption experienced so far within our technology transfer context. We then put a particular emphasis on the reengineering entry point in which we describe what we think are the main possible adoption scenarios. Throughout the paper we emphasize the contribution of (reference) software architectures so as to highlight the key enabling role it plays for the PL approach.