Anonymous Preference Elicitation for Requirements Prioritization

  • Gerald Ninaus
  • Alexander Felfernig
  • Florian Reinfrank
Part of the Lecture Notes in Computer Science book series (LNCS, volume 7661)


Requirements Engineering is a very critical phase in the software development process. Requirements can be interpreted as basic decision alternatives which have to be negotiated by stakeholders. In this paper we present the results of an empirical study which focused on the analysis of key influence factors of successful requirements prioritization. This study has been conducted within the scope of software development projects at our university where development teams interacted with a requirements prioritization environment. The major result of our study is that anonymized preference elicitation can help to significantly improve the quality of requirements prioritization, for example, in terms of the degree of team consensus, prioritization diversity, and quality of the resulting software product.


Requirements Prioritization Group Decision Making 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Zave, P.: Classification of research efforts in requirements engineering. ACM Computing Surveys 29(4), 315–321 (1997)CrossRefGoogle Scholar
  2. 2.
    Hofmann, H., Lehner, F.: Requirements engineering as a success factor in software projects. IEEE Software 18(4), 58–66 (2001)CrossRefGoogle Scholar
  3. 3.
    Felfernig, A., Zehentner, C., Ninaus, G., Grabner, H., Maalej, W., Pagano, D., Weninger, L., Reinfrank, F.: Group Decision Support for Requirements Negotiation. In: Ardissono, L., Kuflik, T. (eds.) UMAP Workshops 2011. LNCS, vol. 7138, pp. 105–116. Springer, Heidelberg (2012)CrossRefGoogle Scholar
  4. 4.
    Yang, D., Wu, D., Koolmanojwong, S., Brown, A., Boehm, B.: Wikiwinwin: A wiki based system for collaborative requirements negotiation. In: HICCS 2008, Waikoloa, Big Island, Hawaii, p. 24 (2008)Google Scholar
  5. 5.
    Firesmith, D.: Prioritizing requirements. Journal of Object Technology 3(8), 35–47 (2004)CrossRefGoogle Scholar
  6. 6.
    Group, G.: Hype cycle for application development: Requirements elicitation and simulation (2011)Google Scholar
  7. 7.
    Aurum, A., Wohlin, C.: The fundamental nature of requirements engineering activities as a decision-making process. Information and Software Technology 45(14), 945–954 (2003)CrossRefGoogle Scholar
  8. 8.
    Regnell, B., Paech, B., Aurum, C., Wohlin, C., Dutoit, A., Ochdag, J.: Requirements means decision! In: 1st Swedish Conf. on Software Engineering and Practice (SERP 2001), Innsbruck, Austria, pp. 49–52 (2001)Google Scholar
  9. 9.
    Davis, A.: The art of requirements triage. IEEE Computer 36(3), 42–49 (2003)CrossRefGoogle Scholar
  10. 10.
    Wiegers, K.: First things first: Prioritizing requirements. Software Development (1999)Google Scholar
  11. 11.
    Pinsonneault, A., Heppel, N.: Anonymity in group support systems research: A new conceptualization, measure, and contingency framework. Journal of Management Information Systems 14, 89–108 (1997)Google Scholar
  12. 12.
    Greitemeyer, T., Schulz-Hardt, S.: Preference-consistent evaluation of information in the hidden profile paradigm: Beyond group-level explanations for the dominance of shared information in group decisions. Journal of Personality & Social Psychology 84(2), 332–339 (2003)CrossRefGoogle Scholar
  13. 13.
    Mojzisch, A., Schulz-Hardt, S.: Knowing other’s preferences degrades the quality of group decisions. Journal of Personality & Social Psychology 98(5), 794–808 (2010)CrossRefGoogle Scholar
  14. 14.
    Cialdini, R.: The science of persuasion. Scientific American 284, 76–81 (2001)CrossRefGoogle Scholar
  15. 15.
    Felfernig, A., Ninaus, G.: Group recommendation algorithms for requirements prioritization. In: Workshop on Recommender Systems for Software Engineering (RSSE 2012), Zurich, Switzerland, pp. 1–4 (2012)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2012

Authors and Affiliations

  • Gerald Ninaus
    • 1
  • Alexander Felfernig
    • 1
  • Florian Reinfrank
    • 1
  1. 1.Institut of Software TechnologyGraz University of TechnologyGrazAustria

Personalised recommendations