Software requirement prioritization based on non-functional requirements

Requirements can be characterized as needs or demands. In software, requirements are a portrayal of what a system is ought to do. Software requirements describe what must be produced and delivered [1]. System may have few to many requirements. In case of shortage of time or budget prioritizing requirements become a necessity. It not only helps the developer comprehend, which requirements are essential, important or urgent but also proves to be useful in decision making in every phase of software development lifecycle. A lot of techniques have emerged over time to prioritize requirements, each with a set of strengths and weaknesses. In this paper, we present an approach by combining a few of existing techniques that will help the software engineers prioritize requirements.