Requirement Prioritization Techniques: An Empirical Study

Abstract

In requirements prioritization primary concern is to identify the largest part of significant requirements and their importance for a system. There are many methodologies, techniques that are used in requirements prioritization as we will highlight here in latter sections of this work. Requirement prioritization is an essential part of software engineering which helps to make good decisions regarding software designing and implementation. All requirements cannot be enforce at same time, requirements are and have to be prioritize to be implemented to give solution as early as possible in phases (stages) as scheduled in incremental design and evolution. These prioritization techniques are good for high quality software. In requirements prioritization decisions are made by the stakeholders with respect to the product (attributes) and in contingency to external attributes such as time to market, deadlines, and usability thus it is important to prioritize requirements. Our goal in this work is to comprehensively describe ant take account of the different prioritization techniques from an empirical study with respect to different prioritization methodologies (attributes). Latter thorough comprehensive evaluation it is further anticipated that we can easily identify, mark which requirements (functional or non-functional or any other) are better in plight of accuracy, easy to use, and time it takes.