Abstract
Requirement Engineering is the process to gather the software requirements from end-users. Prime objectives of requirement engineering include analysis, documentation, and development of system requirement specification. Prioritization of gathered requirements of a project is an uphill task for justifiable requirement engineering especially at the early phases of the development. Through relevant requirement prioritization, we can identify the exact requirements that must be included in a specific release. The main objective behind requirement prioritization is to decrease the associated risks in the development process. In Agile Software Development processes, it is not a cakewalk to prioritize the relevant requirements because requirements are welcomed even late in development phases in agile methodologies. This paper extracts information on discrete requirement prioritization approaches along with their strength and weaknesses. Through this paper, product owners will be in a condition to finalize a relevant prioritization approach according to the project's behavior and other constraints.
Sign-in/Register to access full text options 
Free) 
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 call
