Skills required for elicit software requirements and elicitation process

To efficiently and effectively understand the project, requirements and all the resource requirements that will be needed to facilitate the project. A feasibility study will help in collecting all the relevant information required for the project. After the feasibility study, analyze the findings of the study and come up with the relevant cases and brief resolutions of the project. Review all the relevant historical information in relation to the project, what policies the organization has, its standards and any regulations available will have an impact on the project and if they will constrain it in any way. Analyze all the previous projects done by the organization in the same area both the successful and failed ones. Review their specifications and documentation in technical terms to derive some direct and indirect lessons and what the requirements of the projects were. Determine whether there exist any descriptions of the present operations specifically the approved operational concepts and examine any issues that are documented. This information will help identify the types of stakeholders required to facilitate the elicitation of the project. After that, come up with a drafted requirement of the collection plan, approximate resource requirement examines the tools appropriate for the project with the use of the same method. Lastly at this stage identification of the risks that may arise during the collection process of the requirements and come up with strategies through which you will mitigate the risks. Although the project manager will be the overall person in charge of the project, other people will be required to facilitate the planning and execution of the project. This will affect all other people in the organization and the current systems put in place. The effect may be either indirect or direct thus expanding the stakeholder’s list.

Stakeholders are the managers who will sponsor the project and contributor to the requirements of the project. Stakeholders who provide the technical and operational requirements form the primary stakeholders. Those people within the organization who are indirectly affected by the project, for example, the operations and business interfacing personnel, the SMEs like managers and technical and financial experts and others who must be kept in loop form part of stakeholders. Come up with a way that will help in communication across the stakeholders. This can be done through the creation of the project emails, meetings or any other formal presentation.

The person in charge should be able to establish the main reason why the problem exists. This should be done before the commencement of the requirement collection. For the project to effectively address the problem, the SE must be able to answer the question of why the project was chosen. This can be done by conclusively looking and investigating the real and perceived needs of the project through looking in the environment. The process can be facilitated by examining the informational needs through operations and concepts and analyzing them. Make sure all the stakeholders agree on the need to have a straight and outright problem statement that is in relation to the case of business. The ability of the software elicits in solving the problem is very important since some customers may raise the question of how and whether the software elicits will solve their problem with the laid down options. This can only be avoided by giving viable options to the customer with a very clear process (Shah & Jinwala, 2015).