Salion, Inc.: A Software Product Line Case Study
|
REPORT DOCUMENTATION PAGE |
Form Approved OMB No. 0704-0188 |
||
|
Public reporting burden for this collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. |
|||
|
1. agency use only (leave blank) |
2. report date November 2002 |
3. report type and dates covered Final |
|
|
4. title and subtitle Salion, Inc.: A Software Product Line Case Study |
5. funding numbers C — F19628-00-C-0003 |
||
|
6. author(s) Paul C. Clements & Linda M. Northrop |
|||
|
7. performing organization name(s) and address(es)
Software Engineering Institute |
8. performing organization
CMU/SEI-2002-TR-038 |
||
|
9. sponsoring/monitoring agency name(s) and address(es)
HQ ESC/XPK |
10. sponsoring/monitoring
ESC-TR-2002-038 |
||
|
11. supplementary notes |
|||
|
12.a distribution/availability statement Unclassified/Unlimited, DTIC, NTIS |
12.b distribution code |
||
|
13. abstract (maximum 200 words)
This report is another in a series
of Software Engineering Institute (SEISM) case studies of organizations that
have adopted the software product line approach for developing systems. It
details the story of Salion, Inc., an enterprise software company providing
Revenue Acquisition Management solutions tailored to the unique needs of
automotive suppliers. Salion's solutions enable suppliers to organize and
manage their disparate customer-interfacing activities as one coordinated
business process, resulting in higher revenues, profit margins, and customer
satisfaction.
This case study is unique in that
Salion did not have substantial experience in its application area, although
its key designers and strategists were knowledgeable about related domains.
Salion pursued a reactive approach to its product line that let it respond
flexibly to spontaneous business opportunities and that significantly lowered
the cost of adopting the product line paradigm to its software system
development. This case study describes relevant dimensions of Salion's
context, how it approached several product line practice areas that were key
to its strategy, the benefits gained through its product line, lessons
learned, and the major thematic aspects of the Salion story.
SM SEI is a service mark of Carnegie Mellon University.
|
|||
|
14. subject terms software product lines, product line practice, product line practice framework, product line case study |
15. number of pages |
||
|
|
16. Price Code |
||
|
17. security classification UNCLASSIFIED |
18. security classification UNCLASSIFIED |
19. security classification UNCLASSIFIED |
20. limitation of abstract UL |
|
NSN 7540-01-280-5500 |
Standard Form 298 (Rev. 2-89) Prescribed by ANSI Std. Z39-18 298-102 | ||