Requirements prioritization

234Citations
Citations of this article
263Readers
Mendeley users who have this article in their library.
Get full text

Abstract

This chapter provides an overview of techniques for prioritization of requirements for software products. Prioritization is a crucial step towards making good decisions regarding product planning for single and multiple releases. Various aspects of functionality are considered, such as importance, risk, cost, etc. Prioritization decisions are made by stakeholders, including users, managers, developers, or their representatives. Methods are for combining individual prioritizations based on overall objectives and constraints. A range of different techniques and aspects are applied to an example to illustrate their use. Finally, limitations and shortcomings of current methods are pointed out, and open research questions in the area of requirements prioritization are discussed. © 2005 Springer-Verlag Berlin Heidelberg.

Cite

CITATION STYLE

APA

Berander, P., & Andrews, A. (2005). Requirements prioritization. In Engineering and Managing Software Requirements (pp. 69–94). Springer Berlin Heidelberg. https://doi.org/10.1007/3-540-28244-0_4

Register to see more suggestions

Mendeley helps you to discover research relevant for your work.

Already have an account?

Save time finding and organizing research with Mendeley

Sign up for free