Advertisement

Requirements Prioritization Challenges in Practice

  • Laura Lehtola
  • Marjo Kauppinen
  • Sari Kujala
Part of the Lecture Notes in Computer Science book series (LNCS, volume 3009)

Abstract

Requirements prioritization is recognized as an important activity in product development. In this paper, we describe the current state of requirements prioritization practices in two case companies and present the practical challenges involved. Our study showed that requirements prioritization is an ambiguous concept and current practices in the companies are informal. Requirements prioritization requires complex context-specific decision-making and must be performed iteratively in many phases during development work. Practitioners are seeking more systematic ways to prioritize requirements but they find it difficult to pay attention to all the relevant factors that have an effect on priorities and explicitly to draw different stakeholder views together. In addition, practitioners need more information about real customer preferences.

Keywords

Product Development Requirement Engineering Case Company Priority Decision Ambiguous Concept 
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.
    Siddiqi, J., Shekaran, M.: Requirements engineering: The emerging wisdom. IEEE Software 2, 15–19 (1996)CrossRefGoogle Scholar
  2. 2.
    Karlsson, J., Ryan, K.: A cost-value approach for prioritizing requirements. IEEE Software 14, 67–74 (1997)CrossRefGoogle Scholar
  3. 3.
    Karlsson, J., Wohlin, C., Regnell, B.: An evaluation of methods for prioritizing software requirements. Information and Software Technology 39, 939–947 (1998)CrossRefGoogle Scholar
  4. 4.
    Regnell, B., Höst, M.: Natt och Dag, J., Beremark, P., Hjelm, T.: An industrial case study on distributed prioritisation in market-driven requirements engineering for packaged software. Requirements Engineering 6, 51–62 (2001)Google Scholar
  5. 5.
    Wiegers, K.E.: Software Requirements. Microsoft Press, Redmont (1999)Google Scholar
  6. 6.
    Harwell, R., Aslaksen, E., Hooks, I., Mengot, R., Ptack, K.: What is a requirement? In: Proceedings of the Third International Symposium of the NCOSE, pp. 17–24 (1993)Google Scholar
  7. 7.
    Lubars, M., Potts, C., Richter, C.: A review of the state of the practice in requirements modelling. In: Proceedings of IEEE Symposium on Requirements Engineering (RE 199́3), IEEE Computer Society Press, Los Alamitos (1993)Google Scholar
  8. 8.
    Aurum, A., Wohlin, C.: The fundamental nature of requirements engineering activities as a decision-making process. Information and Software Technology 45, 945–954 (2003)CrossRefGoogle Scholar
  9. 9.
    Andriole, S.: The politics of requirements management. IEEE Software 15, 82–84 (1998)CrossRefGoogle Scholar
  10. 10.
    Carlshamre, P., Sandahl, K., Lindvall, M., Regnell, B., Natt och Dag, J.: An industrial survey of requirements interdependencies in software product release planning. In: Proceedings of the Fifth IEEE International Symposium on Requirements Engineering (RE 200́1), pp. 84–91 (2001)Google Scholar
  11. 11.
    Regnell, B., Paech, B., Aurum, A., Wohlin, C., Dutoit, A., Natt och Dag, J.: Requirements mean decisions! - research issues for understanding and supporting decision-making in requirements engineering. In: Proceedings of the First Swedish conference on Software Engineering Research and Practice (SERP 200́1), Ronneby, Sweden, pp. 49–52 (2001)Google Scholar
  12. 12.
    Edmunds, H.: The Focus Group Research Handbook. In: NTC Business Books in conjunction with the American Marketing Association, Lincolnwood (Chicago), Illinois (1999)Google Scholar
  13. 13.
    Templeton, J.F.: The Focus Group - A Strategic Guide to Organizing, Conducting and Analyzing the Focus Group Interview. Revised edn. Mc Graw Hill, New York (1994)Google Scholar
  14. 14.
    Oddo, F. (ed.): Coach’s Guide to the Memory Jogger II. GOAL/QPC, Methuen (1995)Google Scholar
  15. 15.
    Yeh, A.C.: Requirements engineering support technique (request) a market driven requirements management process. In: Proceedings of the Second Symposium of Quality Software Development Tools, New Orleans, USA, pp. 211–223 (1992)Google Scholar
  16. 16.
    Sommerville, I.: Software Engineering, 5th edn. Addison-Wesley, Wokingham (1996)Google Scholar
  17. 17.
    Moisiadis, F.: The fundamentals of prioritising requirements. In (Web) Proceedings of Systems Engineering/Test and Evaluation conference, SETE 2002 (2002), http://www.seecforum.unisa.edu.au/Sete2002/ProceedingsDocs/

Copyright information

© Springer-Verlag Berlin Heidelberg 2004

Authors and Affiliations

  • Laura Lehtola
    • 1
  • Marjo Kauppinen
    • 1
  • Sari Kujala
    • 1
  1. 1.Software Business and Engineering InstituteHelsinki University of TechnologyFinland

Personalised recommendations