The development of new software is always considered to be a high-risk effort with a high failure probability. The process of developing software is a dynamic activity. The process of developing software is a dynamic activity. During the lifecycle of a project's development, the requirements that the various stakeholders have continually changed. The software industry recognizes this change in requirements as a significant risk element that might occur during the system development process. Requirement It has been discovered that changes have a major impact on the overrun of both schedule and expense in software projects. Requirement Change is necessary to make the software more usable and to raise its economic value, but it may also be a key cause of project failure due to a lack of knowledge of the reasons for change and an inability or unwillingness to handle this requirement change properly. On the flip side, requirements changes are inevitable and must be efficiently managed till the customer reject the product for not meeting his expectations. The importance of prioritizing requirements is widely acknowledged in the area of requirement engineering. The main aim of requirements prioritizing is to identify the most vital requirements that can be applied and, Consequently, give the client the best value possible. Mostly prioritization of the given requirement is done after the elicitation phase. To improve the chances of a successful project development, each requirement change in the requirement should be taken on priority basis. This study uses a fuzzy approach to develop a requirement prioritizing technique from the standpoint of its four measures. This approach emphasizes to the requirement change request.