Software Continues

Also known as requirements gathering, this stage in the requirements development stage involves the collection of system requirements from the stakeholders and will include a number of techniques to successfully collect the requisite requirements for the project. These will include interviews, brainstorming, and facilitated application specification technique (FAST) among others (Olson, 2014). 

During the kickoff meeting, the client will outline their basic vision for the project, including what they hope it can accomplish once it is done. For this reason, the team will get prepared to create use case diagrams as well as how to quickly develop a basic prototype for an initial user interface for the online banking solution. The kickoff meeting should establish an initial baseline that should lay the ground for the requirements process.

The requirements elicitation process is a normally fraught process, given how it involves two parties trying to agree on a single thing. While ideally the client’s need to be the primary focus, there are times when the developers will find themselves having to disagree with the client, especially if the client’s vision and suggestions are deemed impractical.

The developers will need to develop great communication skills so as essentially act as the guide to the vision of the client. Whenever situations arise, they find themselves in disagreement, it will be the responsibility of the developer to steer back to the right path.

Some of the software elicitation techniques will need a great deal of teamwork, especially between the developer and the client. Hence, the capabilities and skills of successfully working in a team environment will be necessary. The Facilitated Application Specification Technique (FAST) for example is one requiring a team-oriented approach to coming up with the specifications for the project (Olson, 2014).

After initial interviews and questionnaires, the development team teamed with the client to come up with a requirement outline. The process involved first identifying all the potential stakeholders for the solution, then listing the requirements intended for the product. Next involved sharpening the list by eliminating redundancies and then grouping them according to their importance in the final solution (Olson, 2014).

Among the requirements that were elicited for the online banking solution include the following.

· The ability of a new customer to open an account from the product.

· The capability of a current bank user to access their account and view details on the account like their transaction history, current balance and even receive a bank statement for a specific period of time.

· The ability for customers of the bank to make transactions from the online solution, including transferring funds to a different account, making deposits to the account, as well as withdrawal from the account to an authorized virtual wallet.

· The customer should be able to receive regular notifications on activities on their account, like receiving money, withdrawals and so forth, to not only promote convenience but also prevent fraud.

The product should allow customers to view exchange prices in real time

Olson, D. (2014). Information systems project management. Business Expert Press.