Laurent et al. have described the problems related to
software requirements prioritization and according to
them "Lack of an effective prioritization and triage
process can lead to problems such as missed deadlines,
disorganized development efforts, and late discovery of
architecturally significant requirements. Existing
prioritization techniques do not provide sufficient
automation for large projects with hundreds of
stakeholders and thousands of potentially conflicting
requests and requirements" [23]. Most of the software
systems fail or end up because of irrelevant requirements
and they don't fulfill the original requirements so it
resulted in their rejection at early stages [11]. It's also
essential to choose a best suit of requirements, when
resources are limited, in order to get best outcome in terms of customer satisfaction within the specified budget
[17].
The above statements provide the motivation for future
research. As for projects where requirements scale up in
hundreds or even in thousands there is a problem of "late
discovery of architecturally significant requirements"
[23]. So due to "infinite range of candidate requirements"
[17] "many software systems end up being developed
without meeting their requirements and thus cannot be
used as initially expected" [11]. To solve this problem
there is the need to prioritize the requirements in a new
and innovative way. In literature survey we have found
that the "Existing prioritization techniques do not provide
sufficient automation for large projects with hundreds of
stakeholders and thousands of potentially conflicting
requests and requirements" [23]. There is the need to
automate the existing techniques in order to utilize them
fully for better results.