William A. Hetrick
ABSTRACT
Engenio made the transition to software product line practice in order to keep pace with growing business demand for its products. By using an incremental transition strategy, Engenio avoided the typical upfront adoption barrier - the equivalent development effort of 2 to 3 standalone products - which in their case was projected to be 900 to 1350 developer-months. Engenio discovered that by making an upfront investment of only 4 developer-months, they were able to start a chain reaction in which the tactical and strategic incremental returns quickly outpaced the incremental investments, making the transition pay for itself.
- Engenio Information Technologies, Inc., Milpitas, CA. http://www.engenio.comGoogle Scholar
- Paul Clements and Linda Northrop. 2001. Software Product Lines: Practice and Patterns, Addison Wesley, Reading, MA. Google ScholarDigital Library
- Davis Weiss and Chi Tau Robert Lai. 1999. Software Product-line Engineering. Addison-Wesley, Reading, MA. Google ScholarDigital Library
- SoftwareProductLines.com, see Resources section, http://www.SoftwareProductLines.comGoogle Scholar
- BigLever Software, Inc. Austin, TX. http://www.biglever.comGoogle Scholar
- Charles Krueger and Dale Churchett. Eliciting Abstractions from a Software Product Line, in Proceedings of the OOPSLA 2002 PLEES International Workshop on Product Line Engineering. Seattle, Washington. November 2002, pages 43--48Google Scholar
- Ross Buhrdorf, Dale Churchett, Charles Krueger. Salion's Experience with a Reactive Software Product Line Approach. Proceeding of the 5th International Workshop on Product Family Engineering. Nov 2003. Siena, Italy. Springer-Verlag LNCS 3014, p 315.Google Scholar
- Charles Krueger. Variation Management for Software Product Lines, Proceeding of the Software Product Lines 2nd International Conference, SPLC 2, San Diego, CA, Aug 2002, Springer-Verlag LNCS 2379, p 257. Google ScholarDigital Library
- John Kotter. 2002. The Heart of Change, Harvard Business School Press. Cambridge, MA.Google Scholar
Index Terms
- Incremental return on incremental investment: Engenio's transition to software product line practice
Recommendations
Return on Investment of Software Product Line Traceability in the Short, Mid and Long Term
ICEIS 2015: Proceedings of the 17th International Conference on Enterprise Information Systems - Volume 2Several works discuss tracing in Software Product Lines from a technical and architectural points of view, by proposing methods to implement traceability in the system. However, before discussing this field of traceability, we first need to prove the ...
Incremental methods for FSM traversal
ICCD '95: Proceedings of the 1995 International Conference on Computer Design: VLSI in Computers and ProcessorsComputing the set of reachable states of a finite state machine, is an important component of many problems in the synthesis and formal verification of digital systems. The process of design is usually iterative, and the designer may modify and ...
Automatic and Incremental Product Optimization for Software Product Lines
ICST '14: Proceedings of the 2014 IEEE International Conference on Software Testing, Verification, and ValidationSoftware Product Lines (SPLs) have gained popularity in industry as they foster the reuse of artifacts, such as code, and reduce product development effort. Although some SPLs ensure that only valid products are configurable, those products are not ...
Comments