From literature it is evident that to prioritize software
requirements specifications is not an easy task rather it's
a more complex and brainstorming job. It's not easy to
find out the value of a requirement in its true spirit
because of the readily changeable nature of the
requirements. At this stage we have proposed an
extension in VIRP model for requirements prioritization
322 in order to overcome the shortcomings of existing
software requirements prioritization techniques. Currently
we are working on the proposed extension which will
result in better understanding and translation of
significant requirements and there would be less chances
of error. The VIRP technique will become more time
efficient, scalable and its overall performance will also
increase as compared to the other techniques.