International Journal of Software Engineering & Applications (IJSEA), Vol.3, No.3, May 2012 DOI : 10.5121/ijsea.2012.3305 51              Nilofar Mulla 1 and Sheetal Girase 2 1 Department of Information Technology, MIT Pune 38, Maharashtra, India nilofar_mulla2005@yahoo.co.in 2 Asst.Prof. Department of Information Technology, MIT Pune 38, Maharashtra, India sheetal.girase@mitpune.edu.in ABSTRACT The customers' needs in a software project are identified in the process of Software requirements elicitation. For building a software system this process is considered as one of the most important parts. In this part it is decided precisely what will be built. A close interaction between developers and end-users of the system is needed by requirements’ gathering. Meetings can be costly, inconvenient and infrequent if developers and end-users are in different organizations or different cities. The quality of the elicited requirements can greatly be impacted if there is a problem of communication. Requirement elicitation is a process difficult to scale to large software projects with many stakeholders which involves identifying and prioritizing requirements. A stakeholder is an individual or a group who can influence or be influenced by the success or failure of a project. Existing methods to identify and prioritize requirements do not scale well to large projects. Large projects tend to be beset by three problems: information overload, inadequate stakeholder input, and biased prioritization of requirements. Existing methods to identify and prioritize requirements do not scale well to large projects. Existing requirements prioritization methods require substantial efforts from the requirements engineers when there are many requirements. To address the problems Stakeholder recommender model will contain steps:-Identify the large project, Analysis of requirements, Identify and prioritize stakeholders, Predict requirements, Prioritize requirements. For making predictions, our approach will use one of the most well known algorithms that is k-Nearest Neighbor (kNN) algorithm. KNN is used to identify like-minded users with similar rating histories in order to predict ratings for unobserved users-item pairs. A unique subset of the community for each user is found out by KNN by identifying those with similar interests. To do so, every pair of user profile is compared to measure the degree of similarity. A neighbourhood is created for each user by selecting the k most similar users. The similarity between each pair of user profiles for users in the neighbourhood is used to compute predicted ratings. Finally, the predicted ratings for the items are sorted according to the predicted value, and the top-N items are proposed to the user as recommendations, where N is the number of items recommended to the user. KEYWORDS Requirements Elicitation, Stakeholder, k-Nearest Neighbour 1. INTRODUCTION The most important activity in software project development is the requirements engineering. For a computer based system, activities involved in discovering, documenting, and maintaining a set of requirements are covered by requirements engineering. due to wrong requirements, numbers of