Part III  Continue developing deliverables of a website for a bank that allows customers to manage their finances in Part I and Part II (attached). Go through the major steps of the software development life cycle. Each deliverable should take a minimum of one page. Include citations throughout, as necessary and a reference page.

Part III deliverables are as follows:

1. Risk Assessment
Create a risk assessment that lists risks along with severity and probability.

Notes: Table of all the possible things that could go wrong, be it internal or external to the program. Like stakeholders, you will want to rank them and provide a definition for how you prioritize them.

2. Schedule/Process Overview
Define the process life cycle that should be implemented (for example, Agile). Identify who and how many people should be tasked for each phase.

Notes: Provide a Gantt chart with possible time values and personnel that mirror the different components and modules you outline in the system overview/design.

3. Testing Plan
Create a testing plan that highlights what elements will be tested and how they will be tested. Identify critical components that need the most focus. Include at least four use cases that illustrate steps taken to perform a basic test.

Product Overview
The proposed project will provide banking customers with online banking real time," giving
them access to their bank account via a login, set up bill payments, electronic bill notification,
online deposits, transfers between account or banking institutions and reporting tools. The
banking website will also give access to Branch/ATM Locations, Contacts and Rates and ease of
opening new accounts and applying for various types of credit that are offered by the bank. The
website needs be easy to navigate, be secure, allow for third-party integrations, responsive
design support, analytics tracking and ability to personalize content.
In the online banking market, there are many competitors that will attract the customer due
their offers, policy, and reputation. “Banks must have the scale to invest significantly in new
technology, yet they must also avoid the too big to fail trap, which would put them at odds with
regulators and investors alike", said Mr. Ghizzoni, chief executive of UniCredit, Italy’s largest
bank. To be successful the goals of the customer must be realized so that we can increase
customer engagement and gain loyalty. The online banking solution should be an expansion of
traditional banking; mobile app, online lending platform, management tools, or stored valued
cards. Customers will also expect increased functionality like online deposits, check images and
external transfers. The bank will also need to ensure that the online banking solution is in line
with its strategic goals, reduce operational, enhance revenue growth and superior customer
experiences generation long term loyalty. Stakeholder Overview
Stakeholders that contribute or benefit from the online banking website can be categorized in
four groups; Consumers, Banks, Internet Service Providers and Regulatory Authorities.
Stakeholder Importance
(L, M, H) Consumer
(suppliers, individual customers,
employees, stockholders, management,
and the local community, companies,
organizations) The Bank (CEO, Board, Directors,
managers & employees) H Support
(L, M, H)
M Need/Requirement Expectations Online payment of bills
and Automatic Bill
Payments
Easy Account Creation
ATM Locations near my
location
Electronic Statements
Mobile Check Deposits
Secure Message Alerts
Report & Management
Tools
Desktop Software
Integration
Security of all data
Mobile app
Access to additional
banking products, i.e.
car and loans, rates conveniences and
effectiveness H provide access to most
banking products over
the internet
be able to development
of new product that
would keep internet
banking up to date Internet Service providers Regulatory Authorities provide the required
network on which banks
gain access into
connections to avoid
intruders or hackers having
access into their network
effective governance
and management ensure all the transactions
performed by customers
through the banks are well
delivered to the
destinations which they
needed them
ensures customers are
being protected Requirements Analysis
Functional requirements Possible
Conflicts
none Logon Capabilities
Registration ability
Transaction process and regulations
Database integration
Browser optimization
security
Reporting Non-functional requirements
24/7 availability
Usability- proper user interface, user’s manual, online help
100% access reliability
maintainability, the ability to upgrade the system and firmware
compliance with regulations References
Cornell, A. (2015, December 15). Banking in 2016 – Where are the risks? Retrieved January 29,
2017, from https://bluenotes.anz.com/posts/2015/12/banking-in-2016-where-are-the-risks/
The 7 Best Online Banking Features For Simplifying Your Life. (n.d.). Retrieved January 29,
2017, from http://www.makeuseof.com/tag/7-best-online-banking-features-simplifying-life/
Shead, M. (2007, June 11). Productivity. Retrieved January 27, 2017, from
http://www.productivity501.com/choosing-online-bank/244/
Brown, M. (2014, November 06). 10 Features of Great Banking Websites. Retrieved January 27,
2017, from https://thefinancialbrand.com/42072/bank-credit-union-website-design-tips/

Online Banking System
Kym Bridgers
MGT 5150 – Spring I 2017
February 12, 2017 System Overview
The new online banking system will be interacting with other bank systems that will be utilized
by various bank workers & administrators and outside systems such as ATMs not owned by the
bank, online payment systems and transfer of funds between accounts and outside banks. The
new system has to perform fast enough to
complete the necessary banking tasks and be reliable and secure. The online bank system will include authorization of users, ensuring only users that are
authorized can access the system which are not only the bank's customers and employees.
Security will be one of the most important aspects of the system not only when it comes to
accessing via the web but the ability to withstand many different types of attacks. The online system will provide banking customers with web-based banking, giving them access
to their ledger, set up electronic bill payments and notifications, online banking products,
exchanges between record or managing an account establishments and detailing instruments.
The banking site will offer access to Branch/ATM Locations and information, Contacts, and Rates
and simplicity of opening new accounts and applying for different sorts of credit that are offered
by the bank.
Components to be developed: Client Application Server Database
The system functional and non-functional requirements are shown in the table below: Functional
Logon Capabilities
Registration capabilities
transaction process and regulations
database integration
browser optimization
Security
Reporting Non-functional
24/7 availability
Usability - online help
Access reliability
Maintainability
compliance with regulations The goals of the system are to be able to handle a wide variety of customers financial needs.
Customers need to have confidence that their data is safe as they use the system. The customer
also wants to access the system using a variety of devices such as personal computers,
smartphones, and other mobile devices. This system will eventually be able to handle various
interactions, and the system will have to be easy to develop and expand additional functionality
to service the customer's needs. Security is a primary concern, and we have to ensure that every precaution is taken to ensure
that all data is transmitted securely and the environment of the servers and database are within
a secure environment. With that said we will use the latest methods to increase and monitor
the integrity and security of the online system. System Design
This system architecture will give an overview of the entire system, showing the major static and
dynamic aspects of a system, highlighting the important characteristics and ignoring
unnecessary details. The goal of this section is to provide documentation that is a complete and clear record of the system architect's decisions. The system must be able to handle current and
new technology. This online banking system will be a 3-tiered model that is widely used in online banking
systems. The major components of the system are the client, application server and the
database. The client component will consist of two clients, web-based for customers and one
for administration. The application server takes care of the server script, database connectivity,
and mapping, so that customer and administrator request are fulfilled. The database will store
all relevant customer and bank data. Client
The client architecture is available for various types interfaces and operating systems. There are
utility functions such as print, toolbar, and help functions.
Application Server
The server architecture contains two logical servers, the web server, and the application server.
The web server gives the ability to interface with users by communicating via active server pages and HTML. The application server communicates via TCP/IP protocol. Both the web server
and the application server will interact with the database using SQL.
Database
The system will have data transfers occurring in both directions. Data connects to the system
through the internet, passing through the system’s firewall or the LAN connection. The
connection through the LAN requires validation connected to the application server. The system's UML diagrams below give more details. The first diagram is use case diagram. This
use case diagrams has major components are login, account list, balance enquiry, fund transfer,
update profile, request check book, mini statements, help, and logout. The system
administrator is permitted to sign on to the site as well as can right to use her/his managerial
record through utilizing the client given name and the secret word which determination
afterward be confirmed by the database. The information determination is profoundly
protected using the best and most updated secure technology. The next two diagrams are class diagrams of the system. The class diagram demonstrates one
of the defining ideas of object-oriented programming. The diagrams show the classes and the association between them. The system's UML diagrams below give more details. The first
diagram is use case diagram. This use case diagrams has major components are login, account
list, balance enquiry, fund transfer, update profile, request check book, mini statements, help,
and logout. The system administrator is permitted to sign on to the site as well as can right to
use her/his managerial record through utilizing the client given name and the secret word which
determination afterward be confirmed by the database. The information determination is
profoundly protected using the best and most updated secure technology. The next two diagrams are class diagrams of the system. The class diagram demonstrates one
of the defining ideas of object-oriented programming. The diagrams show the classes and the
association between them.
Case Diagrams Wireframe Prototype
This a visual layout of the online banking website. This will show where each component will
live on the page. A prototype will not be shown as the wireframe will not be interactive. Once
the wireframe becomes interactive with real functionality and clickable navigation, it then
becomes a prototype. The wireframe will serve as a communication tool for the development
team to assist them in creating a more user-focused product. This will also give stakeholders a
visualization of the project as determined by the requirements and goals and give them the
ability to provide feedback and changes early in the project, saving on expensive rework. By
getting on the same page early in the process, we can set the tone for a successful project. References
Alanazi,, H., Alnaqeib,, R., Hmood, A., Zaidan, M., & Al ‐Nabhani, Y. (n.d.). The diffusion of
Internet banking, 2013. Retrieved February 8, 2017, from https://arxiv.org/pdf/1005.4029.pdf
Frank, J., Stanton, V., & Chalmers, D. (n.d.). Design Specification. JVD Software Development Inc.
Retrieved February 8, 2017, from
http://www.engr.sjsu.edu/gaojerry/course/131/SampleProjects/Design_Doc.pdf
JINOR, A. D. (2010). Tables of Contents. Polymer Contents, 27(12), 744-789. doi:10.1016/s0883153x(10)00141-4
Sommerville, I. (2016). Software Engineering (10th ed.). Pearson Education.

• 1493708218-Final Project Part 1.docx

ComputerScienceExpert

(11)

Status NEW Posted 02 May 2017 06:05 AM My Price 11.00

-----------

Attachments

file 1493708225-Solutions file 2.docx preview (51 words )

H-----------ell-----------o S-----------ir/-----------Mad-----------am ----------- Th-----------ank----------- yo-----------u f-----------or -----------you-----------r i-----------nte-----------res-----------t a-----------nd -----------buy-----------ing----------- my----------- po-----------ste-----------d s-----------olu-----------tio-----------n. -----------Ple-----------ase----------- pi-----------ng -----------me -----------on -----------cha-----------t I----------- am----------- on-----------lin-----------e o-----------r i-----------nbo-----------x m-----------e a----------- me-----------ssa-----------ge -----------I w-----------ill----------- be----------- qu-----------ick-----------ly -----------onl-----------ine----------- an-----------d g-----------ive----------- yo-----------u e-----------xac-----------t f-----------ile----------- an-----------d t-----------he -----------sam-----------e f-----------ile----------- is----------- al-----------so -----------sen-----------t t-----------o y-----------our----------- em-----------ail----------- th-----------at -----------is -----------reg-----------ist-----------ere-----------d o-----------n -----------THI-----------S W-----------EBS-----------ITE-----------. ----------- Th-----------ank----------- yo-----------u -----------

Not Rated(0)

• Buy Answer