Abstract
Requirements prioritization has been recognized as a critical and essential but challenging activity for product development. The pressure on time-to-market and being able to plan for successive release of the software product has posed many challenges to the software engineering process. Budgetary restrictions and time-tomarket deadline often compel stakeholders to cautiously prioritize requirements. Various requirements prioritization methods are available in literature, but generally practices in companies are found to be informal. This paper evaluates various requirements prioritization methods with different characteristics and proposes a novel technique to select an appropriate method for the application. The aim of our work is to offer a method to guide the engineer through various characteristics such as ease to use, size of project, number of decisions etc. for an application. This approach is illustrated with a case study of the Travel Management Planning Website.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
