M. Soumya Krishnan

Every IT companies start off with their project by prioritizing the RFPs received from their client. These requirement prioritization techniques are practiced to diagnose and categorize the momentous requirements that are put forward by each client. Based on this prioritization strategy, the products are delivered to the client on a timely and needy basis. It is found that, IT
companies are following and practicing a number of prioritization techniques as it is considered as a decisive stair. These techniques are chosen purely based on the functional and non-functional requirements of the project indicated in the RFPs supplied by the clients. But the real issue arises when more than one technique get overlapped in many situations. RFPs incorporate both functional and non-functional requirements. A software engineer feels jumbled in prioritizing these requirements. But functional requirement becomes obligatory. So, the only confusion is related with categorizing the nonfunctional requirements such as cost, dependency, time, risk, benefit, value and effort. The categorization of these requirements
becomes dubious and challenging for a software engineer since lot of techniques already is in existence. At this stage, a model can be suggested to avoid confusion in prioritizing the requirements without any misperception. Through this paper, I have tried to put forward and expound a model as a solution to this problem which can be thoughtlessly followed in undergoing the procedure of prioritizing these non-functional requirements in a most simple and effectual manner. This solution model considers all the pre mentioned non-functional elements by providing a perfect way to follow and select a suitable technique to conduct
requirement prioritization