Lubers et al fourd that many organizations believe that it is important to assign priorities to

requirement and to take decisions about them according to rational, quantitative data. (5)
The chaos story 2009 (6) shows that deficiency of uses interest, confined resources, astonishing
results vibrant nature of requirement and requirement priority, results the future project to
decline. RP also helps to eliminate the disparity amongst the different stakeholders. Karlsson and
Ryan are of the view that requirement priority suggest Stakeholders to assign resources to
requirement on the basic of the priorities (7). Karlsson, Wohlin and Rgnell say that requirement
priority support about the knowledge of the problems in the requirement such as
misinterpretation of the requirement or any vogue requirement so that it does not causes problem
later on (8). Karlsson et al think it help priorities of the requirement. Halton say that requirement
priority is very important now a day in s/w development for the expansion of projects in order to
minimize the fiasco of the projects (9). Karlsson et al think it helps stakeholders to allocate
resources based on the priorities of the requirements (2), detect requirements defect requirement
defects, such as misunderstanding or ambiguous requirement (10) and reduce the number of
changes to requirements and specifications in the later stage of projects.
As sound basis for prioritizing s/w requirements is the approach provided by the
analytical hierarical process, AHP (11). In AHP, decision pair wise compare the requirements to
determine which of two is more important and to what extent. There has been little progress to
data, either theoretical prioritizing s/w requirement. AHP has only been used in few applications
in the s/w industry. Finnie et al (12) for example used AHP to prioritize s/w development factors.
Other application of AHP include a telecommunications quantity. Study performed by pouligeris
and pereirel (13) and s/w requirement priority in a commercial development project by Karlsson
(14).
Different approaches have been proposed which adopts a common model for the requirement
priority process. This paper provides an investigation of 10 basic techniques for sof requirement
prioritization.
To study these techniques, we systematically applied all techniques to prioritize a set if 13
quantity requirements. We there categorized the techniques from user perspective according to
five criteria such as care of use total time taken, scalability, accuracy, and total number of
comparisons required to make decisions.