Though the technique is very effective but with the
automation of "Expert Level Prioritization" the technique
would become more efficient.
In the research [15] an approach is presented to elicit
software requirements and its prioritization using AHP. In
this approach mini software is developed and not a large
scale project is developed as quoted in this research paper
"From this approach we can easily rank the requirements
and can implement it on the basis of the ranking. In this
paper we have developed the Mini Software for Numerical
Integration (MSNI)" [15]. The technique presented by
Muhammad Sadiq at el. is used to improve the
effectiveness and efficiency of the freight transportation
between source and destination using optimization
algorithm. The basic technique which is adopted in the
321
paper for requirements prioritization is AHP about which
we have found in the literature that the technique is suitable
only for limited or small set of requirements and the
techinque is focusing on minimization of the overall
transportation cost [28]. Presently people are busy to
evaluate AHP on small projects and are busy in removing
the limitations of AHP instead of proposing new
techniques that may prove more fruitful for projects with
hundreds of requirements. In another research [2] a
prioritization technique is presented which is for legal
requirements. It is stated that the "Laws and regulations
can make requirements prioritization particularly
challenging due to the high costs of noncompliance and the
substantial amount of domain knowledge needed to make
prioritization decisions" [2]. The very technique proposed
by Aaron K. Massey et al. is focusing the legal
implications of requirements in the domain of healthcare.
The major focus of this technique is HIPP A (Health
Insurance Portability and Accountability Act) which
regulates the Electronic Health Records (EHRs). The
technique is focusing the domain of Healthcare systems
and it's not suitable for all projects.
The literature shows that most of the techniques which
are proposed are only suitable for few requirements and
not suitable when the requirements scaled up in case of
large number of requirements for large projects.
According to the literature evidences the problems with
the existing requirements prioritization techniques can be
summarized as: