Providing Software Product Line Knowledge to Requirements Engineers – A Template for Elicitation Instructions

  • Sebastian Adam
Part of the Lecture Notes in Computer Science book series (LNCS, volume 7195)

Abstract

[Context & Motivation] Developing new software systems based on a software product line (SPL) in so-called application engineering (AE) projects is still a time-consuming and expensive task. Especially when a large number of customer-specific requirements exists, there is still no systematic support for efficiently aligning these non-anticipated requirements with SPL characteristics early on. [Question/problem] In order to improve this process significantly, sound knowledge about an SPL must be available when guiding the requirements elicitation during AE. Thus, an appropriate reflection of SPL characteristics in process-supporting artifacts is indispensable for actually supporting a requirements engineer in this task. [Principal ideas/results] In this paper, a validated template for elicitation instructions that aims at providing a requirements engineer with knowledge about an underlying SPL in an appropriate manner is presented. This template consists of predefined text blocks and algorithms that explain how SPL-relevant product and process knowledge can be systematically reflected into capability-aware elicitation instructions. [Contribution] By using such elicitation instructions, requirements engineers are enabled to elicit requirements in an AE project more effectively.

Keywords

Requirement Engineering Customer Requirement Software Product Line Requirement Engineer Domain Engineering 
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.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Alves, V., Niu, N., Alves, C., Valenca, G.: Requirements engineering for software product lines. A systematic literature review. In: Information and Software. Elsevier (2010)Google Scholar
  2. 2.
    Clements, P., Northrop, L.: Software Product Lines: Patterns and Practice. Addison Wesley (2001)Google Scholar
  3. 3.
    Deelstra, S., Sinnema, M., Bosch, J.: Product derivation in software product families: a case study. The Journal of Systems and Software 74 (2005)Google Scholar
  4. 4.
    Rabiser, R., Grünbacher, P., Dhungana, D.: Supporting Product Derivation by Adapting and Augmenting Variability Models. In: SPLC. IEEE (2007)Google Scholar
  5. 5.
    Vicente-Chicote, C., Moros, B., Toval, A.: REMM-Studio: an Integrated Model-Driven Environment for Requirements Specification, Validation and Formatting. Journal of Object Technology, ETH Zurich 6(9) (2007)Google Scholar
  6. 6.
    O’Leary, P., Rabiser, R., Richardson, I., Thiel, S.: Important Issues and Key Activities in Product Derivation: Experiences from Independent Research Projects. In: SPLC (2009)Google Scholar
  7. 7.
    Goknil, A., Kurtev, I., van den Berg, K.: A Metamodeling Approach for Reasoning about Requirements. In: Schieferdecker, I., Hartman, A. (eds.) ECMDA-FA 2008. LNCS, vol. 5095, pp. 310–325. Springer, Heidelberg (2008)CrossRefGoogle Scholar
  8. 8.
    Djebbi, O., Salinesi, C.: RED-PL, a Method for Deriving Product Requirements from a Product Line Requirements Model. In: Krogstie, J., Opdahl, A.L., Sindre, G. (eds.) CAiSE 2007 and WES 2007. LNCS, vol. 4495, pp. 279–293. Springer, Heidelberg (2007)CrossRefGoogle Scholar
  9. 9.
    Guelfi, N., Perrouin, G.: A Flexible Requirements Analysis Approach for Software Product Lines. In: Sawyer, P., Heymans, P. (eds.) REFSQ 2007. LNCS, vol. 4542, pp. 78–92. Springer, Heidelberg (2007)CrossRefGoogle Scholar
  10. 10.
    Adam, S.: Towards Faster Application Engineering through Better Informed Elicitation – A Research Preview. In: REEW@RefSQ 2011, Essen (2011)Google Scholar
  11. 11.
    Perrouin, G., Klein, J., Guelfi, N., Jezequel, J.: Reconciling Automation and Flexibility in Product Derivation. In: Software Product Line Conference. IEEE (2008)Google Scholar
  12. 12.
    Rabiser, R., Dhungana, D.: Integrated Support for Product Configuration and Requirements Engineering in Product Derivation. In: SEAA. IEEE (2007)Google Scholar
  13. 13.
    Schmid, K.: Planning Software Reuse - A Disciplined Scoping Approach for Software Product Lines. PhD Theses in Experimental Software Engineering 12. Fraunhofer (2003)Google Scholar
  14. 14.
    Eriksson, M., Börstler, J., Borg, K.: Managing requirements specifications for product lines – An approach and industry case study. Journal of Systems and Software (2009)Google Scholar
  15. 15.
    Sinnema, M., Deelstra, S., Hoekstra, P.: The COVAMOF Derivation Process. In: Morisio, M. (ed.) ICSR 2006. LNCS, vol. 4039, pp. 101–114. Springer, Heidelberg (2006)CrossRefGoogle Scholar
  16. 16.
    Cheng, B., Atlee, J.: Research Directions in Requirements Engineering. In: Proceedings of Future of Software Engineering (FOSE). IEEE Computer Society (2007)Google Scholar
  17. 17.
    Halmans, G., Pohl, K.: Communicating the variability of a software-product family to customers. In: Software and System Modeling 2003/2. Springer, Heidelberg (2003)Google Scholar
  18. 18.
    Pohl, K.: Requirements Engineering – Grundlagen, Prinzipien, Techniken. dpunkt (2007)Google Scholar
  19. 19.
    Bühne, S., Halmans, G., Lauenroth, K., Pohl, K.: Scenario-Based Application Requirements Engineering. In: Software Product Lines. Springer, Heidelberg (2006)Google Scholar
  20. 20.
    Alves, C.: COTS-Based Requirements Engineering. In: Cechich, A., Piattini, M., Vallecillo, A. (eds.) Component-Based Software Quality. LNCS, vol. 2693, pp. 21–39. Springer, Heidelberg (2003)CrossRefGoogle Scholar
  21. 21.
    Alves, C., Franch, X., Carvallo, J.P., Finkelstein, A.: Using Goals and Quality Models to Support the Matching Analysis During COTS Selection. In: Franch, X., Port, D. (eds.) ICCBSS 2005. LNCS, vol. 3412, pp. 146–156. Springer, Heidelberg (2005)CrossRefGoogle Scholar
  22. 22.
    Doerr, J., Paech, B., Koehler, M.: Requirements Engineering Process Improvement Based on an Information Model. In: Requirements Engineering Conference. IEEE (2004)Google Scholar
  23. 23.
    Sommerville, I., Lock, R., Storer, T., Dobson, J.: Deriving Information Requirements from Responsibility Models. In: van Eck, P., Gordijn, J., Wieringa, R. (eds.) CAiSE 2009. LNCS, vol. 5565, pp. 515–529. Springer, Heidelberg (2009)CrossRefGoogle Scholar
  24. 24.
    Adam, S., Doerr, J., Ehresmann, M., Wenzel, P.: Incorporating SPL Knowledge into a Requirements Process for Information Systems. In: PLREQ @ REfSQ 2010. Essen (2010)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2012

Authors and Affiliations

  • Sebastian Adam
    • 1
  1. 1.Fraunhofer IESEKaiserslauternGermany

Personalised recommendations