A systematic review of domain analysis solutions for product lines
Journal of Systems and Software
The importance of documentation, design and reuse in risk management for SPL
Proceedings of the 28th ACM International Conference on Design of Communication
Architecture evolution in software product line: an industrial case study
ICSR'11 Proceedings of the 12th international conference on Top productivity through software reuse
Managing forked product variants
Proceedings of the 16th International Software Product Line Conference - Volume 1
Managing cloned variants: a framework and experience
Proceedings of the 17th International Software Product Line Conference
Variability management in an unaware software product line company: an experience report
Proceedings of the Eighth International Workshop on Variability Modelling of Software-Intensive Systems
| Hi-index | 0.00 |
Many organizations used Software Product Line Development to improve development efficiency, time-to-market, and product quality. However, a perceived barrier to entry for Product Line Development is that a Product Line Architecture is required to handle variation across the product set. We describe qualitative evidence from industrial experiences with an approach that has allowed the adoption of Product Line Development for a pre-existing product set, without the use of a Product Line Architecture. The approach relies on file-level reuse and variation mechanisms provided by a Configuration Management infrastructure. The approach can reduce the risks and up-front costs of adopting Product Line Development. Although not requiring a Product Line Architecture, the approach is not inconsistent with architectural-level variation mechanisms. It has allowed previously-reported "reactive" and "proactive" styles of architectural evolution to support variation, and also a new "retroactive" style of architectural evolution. Additionally, the approach has provided new options for "working around" change control conflicts on reused Product Line core assets.