Interface-driven software requirements analysis

Software requirement elicitation

Online banking services

In the current world, technology has taken over all aspects of the economy. This has not only eased the work but it has also led to the improvement of the product. For example, in the banking sector, technology has led to the introduction of online banking which has eased money transfer and withdrawal without physically visiting the bank. The software can allow a customer to know when any transaction is made on his/her account anywhere in the world. This has greatly improved the banking sector services to customers. In terms of security, the introduction of technology has enabled the tracking of any theft cases. The bank is also able to efficiently and effectively allow the use of biometric scans in accessing safety deposit boxes and accounts which is a great boost to the security of the assets in the bank. Therefore, this project will discuss the requirements elicitation, define them, identify and establish the documentation of the software.

Requirements for a kick-off meeting

For better preparation of the kickoff meeting of the project, some steps need to be taken into consideration. First, the organizer of the meeting should prepare themselves adequately on how they will control the meeting from the start. Then plan for the project to help to be able to explain yourself in the meeting and for smooth running of the meeting. Important aspects like the schedules of the meeting and the entire project, the budgets, and the supporting documents should be given more time for preparation (Klein, 2017).

Liaising with the accounts and any other manager who had the initial idea would be helpful. Talking with the accounts manager will help understand the customer desires and needs for the project since he is the one who talked them into committing to the project. Make sure to avail yourself with the original copies of the project schedule, its budget, and the work schedule. Analyze the customer’s requirements and the timeline for the entire project. Try to understand the customer by talking to him/her or the accounts manager to get their background (Klein, 2017).

It is vital to gather all the documentation required for the project and come up with a drafted risk list, time schedule, and the project’s budget. Have a head start of the project before the meeting even if you don’t have all the relevant information of the project that could help create the definitive version of the project.

For any project that is undertaken, there are expectations. Therefore, write down the project’s goals and results. This will help come up with the best and more important decisions of the project; after that, confirm them with the manager or owner of the project idea.

The project will require expertise and manpower to execute it. Recruit them and allocate them responsibilities to perform. Avail of the required resources for the completion of the project form the technical, operations department, corporate and the management department. Come up with a contact list for the team members which will be distributed during the meeting. At the meeting ensure to ask the team members to confirm resource allocation and their responsibilities.

After gathering all vital information, create a presentation that is professional. Use the statement of work to guide your projects assumptions. Any changes suggested during the meeting will be added to the schedule at the end of the meeting. Create an assumption list with all chosen members of the project.

Schedule the meeting with the inclusion of all the participants and give suggestions of the time for the meeting and the dates. Inform the participants on the time of sending documents b3efore the meeting. so that they can review. After the date and time of the meeting has been confirmed, arrange the conference room and call and prepare for the meals and drinks prior to the meeting. Finally, inform the participants of the length of the meeting and whether meals and drinks will be provided during the meeting.

After the end of the meeting, send a thank you text or email to all the participants and explaining to them how you appreciate their attendance of their meeting and how important their views will be to the success of the project.

Skills required for elicit software requirements and elicitation process

Good interpersonal skills are a very vital asset in eliciting software project requirements. Being open-minded and a good listener, being a team player and able to create and maintain a viable relationship will greatly help in software eliciting. The project manager should be able to communicate effectively about the status of the project and resolve any issues and conflicts that may arise during the project among the stakeholders. This will enhance the chances of success of the project.

The manager should be a critical thinker who is able to think broadly. This will help understand the project well and know what the project will require for its execution. This will help in the identification of cost-effective solutions (Naeem, Waheed & Raza, 2017).

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.