Running Head: SOFTWARE DEVELOPMENT
Online banking refers to the ability of a person to manage money online. This can be done
through the use of a mobile phone or a computer. This is highly flexible since it removes the
need of a person to visit the bank. The person can operate solely at home or anywhere he or she
is. Online banking services, however, usually have high-interest rates. Software engineering
comes in because there is the use of computers and telephones. They also help to set and help
function the programs found in these computers. This paper will help us understand software
development for these online banking services. The first step will be to prepare for the kick-off
meeting. The kick-off meeting is supposed to inspire people so that when the meeting is
adjourned all the groups are on the same page. The following steps are to be followed while
preparing for the kick-off meeting (Fernández-Corugedo, 2011).
Step one- development of the goals and deliverables of the project- This is to help
especially in decision making.
Step two-identifying the projects team into their different responsibilities to help in the
organization of the resources (Li, 2005).
Step three- developing a project assumption list-This will help the project members to be
aware of the assumptions that can be made during the project.
Step four-developing the project plan-This is to basically save time while scheduling
people in their different tasks.
Defining key success factors and lastly, to schedule the kick- off meeting-Defining these
success factors will help in the achievement of goals. It will also help in motivating those
people working for the project.
After the kick-off meeting has taken place, it becomes a requirement for the developer to
have certain skills that help in the software elicitation process. These skills are not always
acquired from the classrooms as some of them cannot be taught (Mei, 2010). It is important to
note that these skills are an asset when it comes to the developers needed in this field. These
skills include the following;
Knowledge of the culture of the potential client- This is to help these software engineers
adapt and learn and be able to communicate with their clients.
Teamwork- This is to help in the distribution of work between different people and
therefore helping in the achievement of these goals faster.
Communication skills- These are usually a problem since most of the clients are usually
found in different geographical locations. Conversational skills, knowledge of languages,
these are some of the factors that help in software engineering.
The main objective of these requirement elicitation process is to help the software developer
identify with all the requirements since all of them cannot be acquired from the client. This is to
enable the software developer to know what he or she is working on all factors considered
Below is an outline of the specification requirement specification.
This is usually to describe the required system.
2. Problem statement
States the problem intended to be solved
3. System personnel
Describes the people working in the project
4. Operational setting
Description of the environment where the system is to be used.
5. Impact analysis
It is an assessment of the impact of the system in the operational setting.
6. Functional requirements
User interface overview
System specific requirements
7. Non- functional requirements
System-related non- functional requirements
Process-related non-functional requirements
Personnel-related non-functional requirements
8. Developer overview
9. Requirements specifications rationale
10. Acceptance tests
Ibe, M., Vogel, M., Schindler, B., & Rausch, A. (2013). Create: A co-modeling approach for
scenario-based requierements and component-based architectures. In International
Conference on Software Engineering Advances (pp. 220-227).
Wang, B., Zhao, H., Zhang, W., Jin, Z., & Mei, H. (2010, November). A problem-driven
collaborative approach to eliciting requirements of internetwares. In Proceedings of the
Second Asia-Pacific Symposium on Internetware (p. 22). ACM.
Li, M. (2005, May). Expanding the horizons of software development processes: A 3-D
integrated methodology. In Software Process Workshop (pp. 54-67). Springer, Berlin,
Yelmo, J., & Fernández-Corugedo, J. (2011). An experience of educational innovation for the
collaborative learning in Software Engineering. International Journal of Emerging
Technologies in Learning (iJET), 6(2), 26-32.
Purchase answer to see full