Towards Generating Acceptance Tests for Product Lines

  • Birgit Geppert
  • Jenny Li
  • Frank Rößler
  • David M. Weiss
Part of the Lecture Notes in Computer Science book series (LNCS, volume 3107)


Software product-line engineering aims at improving the efficiency and effectiveness of software development by exploiting the product line members’ commonalities and by controlling their variabilities. The duality of commonalities and variabilities holds for all kinds of assets ranging from requirements specifications over design documents to test cases. A decision model controls the way a product can be distinguished from the rest of the family and is used to extract product-specific information (e.g., product requirements) from the family specifications. Though we traditionally employ decision models for generating code, we aim on capitalizing on the investment for designing the decision model by leveraging it to generate test cases. In this paper we focus on acceptance testing of functions and features, and introduce our approach of using the decision model concept to maintain and generate acceptance test cases for one of our major product lines. Preliminary evaluation of this method demonstrates very promising savings of space and effort as compared to conventional methods.


Product Family Software Product Line Generic Test Case Commonality Analysis Description Item 
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.
    Ardis, M., Daley, N., Hoffman, D., Siy, H., Weiss, D.: Software Product Lines: a Case Study. Software Practice and Experience 30(7), 825–847 (2000)zbMATHCrossRefGoogle Scholar
  2. 2.
    Bosch, J.: Design and Use of Software Architectures – Adopting and Evolving a Product- Line Approach. Addison-Wesley, Reading (2000)Google Scholar
  3. 3.
    Bosch, J.: Software Product Lines: Organizational Alternatives. In: 23rd International Conference on Software Engineering, (ICSE) (2001)Google Scholar
  4. 4.
    Clements, P., Northrop, L.: Software Product Lines – Practices and Patterns. Addison-Wesley, Reading (2002)Google Scholar
  5. 5.
    Geppert, B., Roessler, F.: Combining Product-Line Engineering with Options- Thinking. In: Intern. Workshop on Product-Line Engineering: The Early Steps, (PLEES 2001) (2001)Google Scholar
  6. 6.
    Geppert, B., Roessler, F., Weiss, D.: Consolidating Variability Models. In: ICSE Workshop on Variability Management, International Conference on Software Engineering, Portland, OR, USA (2003)Google Scholar
  7. 7.
    Geppert, B., Weiss, D.: Goal-Oriented Assessment of Product-Line Domains. In: 9th International Software Metrics Colloquium, Sydney, Australia (2003)Google Scholar
  8. 8.
    Li, J.J., Wong, W.: Automatic Test Generation from Communicating Extended Finite State Machine (CEFSM)-Based Models. In: Proc. IEEE ISORC (2002)Google Scholar
  9. 9.
    McGregor, J.D.: Testing a Software Product Line. Technical Report CMU/SEI-2001- TR-022, ESC-TR-2001-022Google Scholar
  10. 10.
    Muccini, H., Hoek, A.: Towards Testing Product Line Architectures.Electr. Notes in Theoretical Computer Science 82 No.6 (2003),
  11. 11.
    Parnas, D.: On the Design and Development of Program Families. In: Hoffman, D., Weiss, D. (eds.) Software Fundamentals, Addison Wesley, Reading (2001)Google Scholar
  12. 12.
    Parnas, D., Clements, P., Weiss, D.: The Modular Structure of Complex Systems. In: Hoffman, D., Weiss, D. (eds.) Software Fundamentals, Addison Wesley, Reading (2001)Google Scholar
  13. 13.
    Rapps, S., Weyuker, E.J.: Selecting Software Test Data Using Data Flow Information. IEEE Trans. On Software Engineering SE-11, 367–375 (1985)CrossRefGoogle Scholar
  14. 14.
    Rumbaugh, J., Jabobson, I., Booch, G.: UML Reference Manual. Addison-Wesley, Reading (1998)Google Scholar
  15. 15.
    Weiss, D., Lai, C.T.R.: Software Product-Line Engineering - A Family-Based Software Development Process. Addison-Wesley, Reading (1999)Google Scholar
  16. 16.
    ITU-T Recommendation Z.100, CCITT Specification and Description Language (SDL), International Telecommunication Union (ITU) (2000) Google Scholar
  17. 17.
    ATEG - (April 2004),
  18. 18.
    Testmaster - (April 2004),

Copyright information

© Springer-Verlag Berlin Heidelberg 2004

Authors and Affiliations

  • Birgit Geppert
    • 1
  • Jenny Li
    • 1
  • Frank Rößler
    • 1
  • David M. Weiss
    • 1
  1. 1.Avaya LabsBasking RidgeUSA

Personalised recommendations