Software Engineering Institute Carnegie Mellon

Salion, Inc.: A Software Product Line Case Study

6   Conclusion

The fact that Salion has the following things in common with other successful product line organizations underscores the importance of those things being common denominators of success:

In addition, there are other characteristics of this organization that point to a successful software product line:

  • Salion's team drives for best practices and excellence in software development.

  • Salion enthusiastically embraces metrics and tracking to help it manage its production, uncover areas of high-payoff improvement, and self-diagnose.

  • Salion fosters a culture that is not afraid to try new things, such as state-of-the-art tools or an innovative best-of-breed mix of three different process paradigms.

  • Salion is a self-aware organization that welcomes critical introspection and thoughtful review.

Salion's software product line story is the story of a small, nimble organization that from the beginning recognized that a reactive product line approach was the way to achieve flexibility in an application domain in which the future could not be predicted reliably. How Salion achieved success with this model, evolved its scope, became more concrete over time, skillfully managed an innovative process model, and gathered fundamental insights about customization versus configuration are all parts of Salion's unique story.  

 


[Title Page]    [Abstract]    [Acknowledgments]    [1 Introduction]    [2 Background]    [3 How Salion Builds Its Software Product Line]    [4 Payoffs and Benefits]    [5 Conclusions and Lessons Learned]    [6 Conclusions]    [7 For Further Reading]    [References]   [DTIC Page]    [PDF file]