Requirement Elicitation

Questions: 1. What is requirement Elicitation? 2.Why is it important to define requirement elicitation in business analysis? 3. What are requirement elicitation techniques? Answers: 1.Feasibility is the first step in project management. Afterward, it is prudent to conduct requirement elicitation. It helps to discover all possible needs. After the collection of the requirements, the team comes together and analyses the requirements based on their relevancy. Software engineers communicate to the end-users or customers to find out certain information such as application domain and the expected performance level of the system (Pohl, 2010). The information helps to decide on the constraints of the system. Hence, requirement elicitation is the process of collecting system requirements from the relevant authorities. That can include the users, customers as well as other stakeholders in the system. 2.It is helpful for the business analyst to make it clear to the stakeholders that they have a significant stake in the positive outcome of the project. It is prudent to clarify the expected business values such as cost reduction and revenue improvement to enhance the success of the project. The business analyst interviews key stakeholders to explain their role in requirement elicitation and to validate that project objective aligns with the perceived goals of the team (Pohl and Ulfat-Bunyadi, 2013). That will ensure that the business processes occur in the most efficient manner, thus promoting the success of the project. Most importantly, the process allows the business analyst and the project manager to develop a preliminary prioritization mapping interest levels to stakeholders. There may be project mismatches in the interest levels needed versus the reality. If so, the plan should terminate until the team resolves the conflicts. 3.These involve the methods that help in requirement collection. They contribute to obtaining the needs of the system, thereby promoting the success of the project. They include apprentice, observe, recount and enact. Apprentice involves shading more light on protocols to determine its success in the market. Observation deals with benchmarking of different alternatives to ascertain the success of the project (Mahaux, Gotel, Mavin, Nguyen and Schmid, 2013). Additionally, recounting entails brainstorming to achieve ideas that will promote the success of the project. Lastly, enact technique involves the development of a prototype that will undergo some level of evolution in the market to determine the success of the project. References Mahaux, M., Gotel, O., Mavin, A., Nguyen, L., Mich, L. and Schmid, K., 2013, May. Collaborative creativity in requirements engineering: Analysis and practical advice. In Research Challenges in Information Science (RCIS), 2013 IEEE Seventh International Conference on (pp. 1-10). IEEE. Pohl, K. and Ulfat-Bunyadi, N., 2013. The Three Dimensions of Requirements Engineering: 20 Years Later. In Seminal Contributions to Information Systems Engineering (pp. 81-87). Springer Berlin Heidelberg. Pohl, K., 2010. Requirements engineering: fundamentals, principles, and techniques. Springer Publishing Company, Incorporated.