Skip to main content

Collaborative Product Line Requirements Engineering Using Rationale

  • Chapter
  • First Online:
Collaborative Software Engineering
  • 1389 Accesses

Abstract

Variability management is the central part of software product line engineering. Due to the separation of domain and application engineering, product line requirements engineering encounters several collaboration problems during variability management. These collaboration problems have an additional layer of complexity, in case, product line organizations are geographically distributed. To address the collaboration problems, we propose a new methodology called issue-based variability management, which is based on the extension of variability management using rationale management. In particular, variability meta-model is viewed as a part of rhetorical rationale model. The methodology is explained and evaluated based on a combination of orthogonal variability model (OVM) and a rationale management approach based on questions, options and criteria (QOC).

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Subscribe and save

Springer+ Basic
$34.99 /Month
  • Get 10 units per month
  • Download Article/Chapter or eBook
  • 1 Unit = 1 Article or 1 Chapter
  • Cancel anytime
Subscribe now

Buy Now

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Similar content being viewed by others

Notes

  1. 1.

    Previously, it was viewed as informal collaboration [26, 27].

References

  1. Berenbach B (2006) Impact of organizational structure on distributed requirements engineering processes: Lessons learned. Proceedings of the 2006 international Workshop on Global Software Development for the Practitioner GSD ’06, May 23, Shanghai, China, pp. 15–19.

    Google Scholar 

  2. Damian D, Marczak S, Kwan I (2007) Collaboration patterns and the impact of distance on awareness in requirements-centred social networks. Proceedings of IEEE RE’ 07, New Delhi. IEEE Digital Library, pp. 59–68.

    Google Scholar 

  3. Damian D, Zowghi D (2007) Requirements engineering challenges in multi-site software development organizations. Requirements Engineering Journal 8: 149–160.

    Article  Google Scholar 

  4. Deelstra S, Sinnema M, Nijhuis J, Bosch J (2004) Experiences in software product families: Problems and issues during product derivation. Software Product Lines, Springer Verlag Lecture Notes on Computer Science Vol. 3154, pp. 65–182.

    Google Scholar 

  5. Dutoit A (2002) Rationale management in requirements engineering. PhD. Dissertation, CMU.

    Google Scholar 

  6. Dutoit A, McCall R, Mistrik I and Paech B (Eds.) (2006) Rationale Management in Software Engineering. Berlin, Heidelberg, New York: Springer.

    Book  Google Scholar 

  7. Fischer R, Ury W (1981) Getting to Yes: Negotiating Agreement Without Giving in, Harward Negotiation Project. Boston, MA: Houghton Mifflin.

    Google Scholar 

  8. Gomaa H (2005) Designing Software Product Lines with Uml: From Use Cases to Pattern-Based Software Architectures. Reading, MA: Addison Wesley Longman Publishing Co.

    Google Scholar 

  9. Gruenbacher P, Seyff N (2006) Requirements Negotiations. Engineering and Managing Requirements. Berlin, Heidelberg, New York: Springer, pp. 143–162.

    Google Scholar 

  10. Hotz L, Krebs T, Wolter K (2004) Using a structure-based configuration tool for product derivation. Proceedings ASE’04 2004 (IEEE Digital Library) pp. 388–391.

    Google Scholar 

  11. John I, Dorr J (2003) Elicitation of requirements from user documentation. Proceedings Ninth International Workshop on Requirements Engineering, Foundation for Software Quality (REFSQ#03), pp. 16–17.

    Google Scholar 

  12. Kang K, Cohen S, Hess J, Nowak W, Peterson S (1990) Feature-oriented domain analysis (FODA) feasibility study. Technical Report, CMU/SEI-90-TR-21, Software Engineering Institute, Carnegie Mellon University.

    Google Scholar 

  13. Kunz W, Rittel R (1970) Issues as elements of information systems, University of California at Berkeley, Institute of Urban and Regional Development.

    Google Scholar 

  14. MacLean A, Young RM, Bellotti VME, Moran TP (1991) Questions, options, and criteria: Elements of design space analysis. Human-Computer Interaction 6: 201–250.

    Article  Google Scholar 

  15. Paech B, Dorr J, and Koehler M (2005) Improving requirements engineering communication in multiproject environments. IEEE Software 22: 40–47.

    Article  Google Scholar 

  16. Paulish DJ (2003) Product line engineering for global development. International Workshop on Product Line Engineering The Early Steps: Planning, Modeling, and Managing, PLEES03.

    Google Scholar 

  17. Pohl K, Boeckle G, van der Linder F (2005) Software Product Line Engineering Foundations, Principles, and Techniques, Berlin, Heidelberg, New York: Springer.

    Google Scholar 

  18. Santos AL, Koskimies K, Lopes A (2006) A model-driven approach to variability management in product-line engineering. Nordic Journal of Computing 13(3): 196–213.

    MATH  Google Scholar 

  19. Subrahmanian E, Konda SL, Levy SN, Reich Y, Westerberg AW, Monarch IA (1993) Equations aren’t enough: Informal modeling in design. AI EDAM 7(4): 257–274.

    Google Scholar 

  20. sysiphus.in.tum.de.

    Google Scholar 

  21. Lago P,  Van Vliet H (2005) Explicit assumptions enrich architectural models. Proceedings 27th International Conference on Software Engineering, ICSE 2005. ACM Digital Library, pp. 206–214.

    Google Scholar 

  22. Lee J (1991) Extending the Potts and Bruns model for recording design rationale. Proceedings ICSE’13, Los Alamitos, CA, pp. 114–125.

    Google Scholar 

  23. Thurimella AK (2009) Issue-Based Variability Modeling: Extending Variability Modeling Based on Rationale Management. Saarbrücken, Germany: VDM Dr. Mueller.

    Google Scholar 

  24. Thurimella AK, Bruegge B (2007) Evolution in product line requirements engineering: A rationale management approach. Proceedings 15th IEEE RE 07, IEEE Computer Society 2007, pp. 254 257.

    Google Scholar 

  25. Thurimella AK, Bruegge B (2007) Empirical evaluation of issue-based variability modeling using the experimental survey technique. Proceedings SEA 2007.

    Google Scholar 

  26. Thurimella AK, Bruegge B, Creighton O (2008) Identifying and exploiting the similarities between rationale management and variability management. Proceedings SPLC 2008, Limerick, Ireland. IEEE Computer Society 2008, pp. 99–108.

    Google Scholar 

  27. Wolf T (2007) Rationale-based Unified Software Engineering Model. Saarbrücken, Germany: VDM Dr. Mueller.

    Google Scholar 

Download references

Acknowledgements

I am grateful to Bernd Bruegge, Allen Dutoit and Guenter Boeckle for their support in my research work. Further, my heartily acknowledgements and dedications to my family members mother, Kumari; father, Uma; wife Padmini and sister Padmaja.

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Anil K. Thurimella .

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2010 Springer-Verlag Berlin Heidelberg

About this chapter

Cite this chapter

Thurimella, A.K. (2010). Collaborative Product Line Requirements Engineering Using Rationale. In: Mistrík, I., Grundy, J., Hoek, A., Whitehead, J. (eds) Collaborative Software Engineering. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-10294-3_18

Download citation

  • DOI: https://doi.org/10.1007/978-3-642-10294-3_18

  • Published:

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-642-10293-6

  • Online ISBN: 978-3-642-10294-3

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics