Software reuse: metrics and models
ACM Computing Surveys (CSUR)
A cooperative model for cross-divisional product development for a software product line
Proceedings of the first conference on Software product lines : experience and research directions: experience and research directions
A Software Product Line Life Cycle Cost Estimation Model
ISESE '04 Proceedings of the 2004 International Symposium on Empirical Software Engineering
Software Reuse Research: Status and Future
IEEE Transactions on Software Engineering
Transitioning to a Software Product Family Approach - Challenges and Best Practices
SPLC '06 Proceedings of the 10th International on Software Product Line Conference
Dynamic Complexity and the Owen Firmware Product Line Program
SPLC '07 Proceedings of the 11th International Software Product Line Conference
Process fusion: An industrial case study on agile software product line engineering
Journal of Systems and Software
Calculating ROI for Software Product Lines
IEEE Software
Software Engineering: Principles and Practice
Software Engineering: Principles and Practice
Agility and Architecture: Can They Coexist?
IEEE Software
| Hi-index | 0.00 |
In a software development environment where legacy software systems have been successfully deployed, there are tensions that deter the organization from moving towards software product line engineering (SPLE). An example is the effort required to develop a product line architecture versus time-to-market pressure or the lack of evidence to justify the benefits of SPLE. In this report we discuss the tensions that exist in Océ Technologies. A reactive software reuse approach has not yielded the desired long-term benefits of reusability. A proactive approach requires knowledge exchange and coordination between software management and technical staff. We describe how such knowledge sharing can ease the tensions and facilitate a SPLE migration process.