PuLSE-BEAT — A Decision Support Tool for Scoping Product Lines

  • Klaus Schmid
  • Michael Schank
Part of the Lecture Notes in Computer Science book series (LNCS, volume 1951)


Determining the scope of a product line is a core activity in product line development, as it has a major impact on the economic results of the project. Only recently an approach was proposed that allows to base this decision explicitly on a detailed analysis of the relevant business goals [2]. As the approach requires gathering and evaluating a lot of data, tool support becomes mandatory. In this paper, we describe the tool PuLSE-BEAT, which was specifically developed to address this need.


Product Line Decision Support Tool Quality Function Deployment Software Product Line Business Goal 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Brownsword, L., Clements, P.: A Case Study in Successful Product Line Development. Carnegie Mellon Software Engineering Institute, CMU/SEI-96-TR- 016 (1996)Google Scholar
  2. 2.
    DeBaud, J.-M., Schmid, K.: A systematic approach to derive the scope of software product lines. In: Proceedings of the 21st International Conference on Software Engineering (1999)Google Scholar
  3. 3.
    Briand, L., Differding, C., Rombach, D.: Practical guidelines for measurementbased process improvement. Software Process Improvement and Practice Journal 2(3) (1997)Google Scholar
  4. 4.
    Bayer, J., Flege, O., Knauber, P., Laqua, R., Muthig, D., Schmid, K., Widen, T., DeBaud, J.M.: PuLSE: A methodology to develop software product lines. In: Symposium on Software Reusability 1999 (SSR 1999) (May 1999)Google Scholar
  5. 5.
    Schmid, K.: An Economic Perspective on Product Line Software Development. In: First Workshop on Economics-Driven Software Engineering Research, Los Angeles (May 1999)Google Scholar
  6. 6.
    Cohen, L.: Quality Function Deployment. Addison-Wesley, Reading (1995)Google Scholar
  7. 7.
    Department of Defense — Software Reuse Initiative, Version 3.1. Domain Scoping Framework, Vol. 2, Technical Description (1995)Google Scholar
  8. 8.
    Robertson, D., Ulrich, K.: Planning for product platforms. Sloan Management Review 39(4), 19–31 (1998)Google Scholar
  9. 9.
    Software Productivity Consortium Services Corporation, Technical Report SPC- 92019-CMC. Reuse-Driven Software Processes Guidebook, Version 02.00.03 (November 1993)Google Scholar
  10. 10.
    Software Technology for Adaptable, Reliable Systems (STARS), Technical Report STARS-VC-A025/001/00. Organization Domain Modeling (ODM) Guidebook, Version 2.0 (June 1996)Google Scholar
  11. 11.
    Withey, J.: Investment analysis of software assets for product lines. Technical report CMU/SEI-96-TR-010, Software Engineering Institute, Carnegie Mellon University (1996)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2000

Authors and Affiliations

  • Klaus Schmid
    • 1
  • Michael Schank
    • 2
  1. 1.Fraunhofer Institute for Experimental Software Engineering (IESE)KaiserslauternGermany
  2. 2.Computer Science DepartmentUniversity of Kaiserslautern 

Personalised recommendations