Software evolution: let's sharpen the terminology before sharpening (out-of-scope) tools
IWPSE '01 Proceedings of the 4th International Workshop on Principles of Software Evolution
Design-time product line architectures for any-time variability
Science of Computer Programming - Special issue: Software variability management
Modeling Product Line Architectures through Change Sets and Relationships
ICSE '07 Proceedings of the 29th international conference on Software Engineering
Issues in mapping change-based product line architectures to configuration management systems
Proceedings of the 13th International Software Product Line Conference
| Hi-index | 0.00 |
A company builds a software system capable of running a diesel engine in a week, and in one case over a weekend, as opposed to the full year that it used to take. Another company builds one of its typical systems with 13 software engineers instead of the more than 100 it once required, and at the same time decreases the systems defect rate ten-fold. Still another increases its software-intensive product offerings from four per year to 50 per year. Imagine being able to use one person to integrate and test 1.5 million source lines of Ada for a real-time command-and-control system onboard a ship, with safety-critical requirements? Or increasing software productivity four-fold over three years, as another company has done? These organizations all achieved their results through strategic software reuse. We software people have been promising the benefits of reuse for decades. Are we finally achieving a reuse strategy that lives up to its hype?