 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
 |
|
||||||||||||||
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
Transition stages: The sequence of incremental steps in Engenio’s transition to software product line practice followed these five primary stages:
- Validate the approach. Engenio embarked on a 6-week pilot project to validate the strategic benefits of BigLever’s Gears in the Engenio environment. After only two weeks, the pilot had exceeded expectations and Engenio made the immediate decision to embrace Gears as its software product line engineering solution, purchasing licenses for its staff of 100 firmware engineers
- Transition the infrastructure from conventional configuration management and builds to first class software product line variation management, configuration management and automated production.
- Transition from team organization by products to team organization by core assets.
- Transition from development processes defined by product releases to development process defined by feature releases.
- Transition from validation and quality assurance for individual products to validation and quality assurance for all of the software product line assets.
Software Product Line Results
"As an OEM supplier to many leading storage vendors, our partners depend on us to provide them with differentiated solutions under aggressive development schedules. This leads to a complex software development challenge. By transitioning to a software product line approach, we were able to leverage our core competency in storage system software to efficiently create, evolve and maintain an entire product line of many differentiated products." -- Bill Brant, Engenio VP of Engineering.
Rapid adoption: Engenio’s transition to a software product line practice demonstrated that a development organization with a large legacy code base can make the transition without a major upfront investment – and without disrupting ongoing production schedules. By investing only four developer-months of effort upfront, and 12 developer-months overall, Engenio incrementally transitioned 23 products, each comprising 1 million lines of code, and 135 developers to a sophisticated software product line practice. (This is less than 1% of effort previously reported for legacy software product line transition efforts.)
Simplified development: The initial code base for the Engenio products was comprised of 3300 files, 1000 of which had anywhere from 2 to 16 branches. Branch complexity is measured using a file branch factor metric, defined as the total number of file branches normalized by the number of products. The initial branch factor prior to the software product line transition was 34% and the final branch factor after core asset consolidation was 0%.
< Previous page . . 1 2 3 4 5 . . Next page >
 |
|
|
Development Tools
and Methods for Software Product Lines Special Seminar from Telelogic and BigLever Software. MDD for Software Product Lines |
|