An evaluation of methods for prioritzing software requirements

The evaluation of six different methods for prioritizing software requirements is described. Based on the quality requirements for a telephony system, all six methods were used on separate occasions to prioritize the requirements. The methods were then characterized according to a number of criteria from a user's perspective. The analytic hierarchy process was found to be the most promising method, although it may be problematic to scale-up. In an industrial follow-up study, the analytical hierarchy process was used to further investigate its applicability. It was found that the process is demanding but worth the effort because of its ability to provide reliable results, promote knowledge transfer and create consensus among project members.