E Banking System

E-Banking System
Version 1.0
System/Subsystem/Software Requirements
Date of Document Generation

Revision A (If Needed)
Prepared for:
Customer
Prepared by:
Developer Name
Erick Timreck, Christopher Croft, Samuel Underhill, Ryan Avery
[Group 3]
timrecke@my.easternct.edu
Table of Contents
1
Introduction.................................................................................................... .............
....................... 5
1.1 Purpose of the
System................................................................................. .................................... 5
1.2 Scope of the
System.................................................................................... ....................................
6
1.3 Objective and Success Criteria of the
Project ............................................... .................................. 6
1.4 Definition of Terms and
Acronyms ............................................................... .................................. 6
1.5
References .................................................................................................... ..............
.................... 7
2 System
Context ................................................................................................ .......................
........... 7
2.1 System
Concept.............................................................................................. .........................
........ 8
2.2 Current
System................................................................................................ ........................
........ 9
2.3 System Design (If this is a component or subsystem of a larger
system)....... ........................... ..... 9
3
Requirements ................................................................................................... ..........
....................... 10
3.1 Functional
Requirements ........................................................................ .....................................
.. 10
3.2 Nonfunctional
Requirements ................................................................ .........................................
10
3.3 Functional (Scenario)
Analysis ............................................................. .......................................... 10
3.3.1
Actors............................................................................................... ...........................
................ 11
3.3.2 Use-Case
1 .................................................................................... .............................................
. 11
3.3.3 Use-Case
2 .................................................................................... .............................................
. 11
3.4 Analysis
Model ........................................................................................ ..................................
.... 11
3.4.1 System
Behavior ............................................................................................ .........................
.... 12
3.4.2 Object Structure and
Behavior .................................................................... ............................... 13
3.4.3 Data and Data
Relations ............................................................................................................. 13
3.4.3 Data and Data
Relations ............................................................................................................. 13
APPENDIX A Previous
Versions................................................................ .........................................14
4.1 Project Plan Introduction (Section 1 of the
SPMP)........................................................................ 15
4.1.2 Project Deliverables (1.2 of the
SPMP)....................................................................................... 15
4.1.3 Evolution of the SPMP (1.3 of the
SPMP)................................................................................... 15
4.1.4 Reference Materials (1.4 of the
SPMP)....................................................................................... 15
4.1.5 Donations and Acronyms (1.5 of the
SPMP)............................................................................... 15
4.2 Project Organization (Section 2 of the
SPMP)................................................................................ 16
4.2.1 Process Model (2.1 of the
SPMP)................................................................................................ 17
4.2.2 Organizational Structure (2.2 of the
SPMP)................................................................................ 18
4.2.3 Organizational Boundaries and Interfaces (2.3 of the
SPMP)..................................................... 19
4.2.4 Project Responsibilities (2.4 of the
SPMP)................................................................................... 19
4.3 Management Objectives and Priorities (3.1 of the
SPMP)............................................................. 20
4.3.2 Assumptions, Dependencies, and Constraints (3.2 of the
SPMP)............................................... 20
4.3.3 Risk Management (3.3 of the
SPMP)........................................................................................... 20
4.3.4 Monitoring and Controlling Mechanisms (3.4 of the
SPMP)....................................................... 20
4.3.5 Staffing Plan (3.5 of the
SPMP).................................................................................................... 20
4.4 Technical Process (Section 4 of the
SPMP)..................................................................................... 21
4.4.1 Methods, Tools, and Techniques (4.1 of the
SPMP).................................................................... 21
4.4.2 Software Documentation (4.2 of the
SPMP)................................................................................ 21
4.4.3 Project Support Functions (4.3 of the
SPMP)............................................................................... 21
4.5.1 Work Packages (5.1 of the

SPMP)................................................................................................ 21
4.5.2 Dependencies (5.2 of the
SPMP).................................................................................................. 21
4.5.3 Resource Requirements (5.3 of the
SPMP).................................................................................. 22
4.5.4 Budget and Resource Allocation (5.4 of the
SPMP)..................................................................... 22
4.5.5 Schedule (5.5 of the
SPMP).......................................................................................................... 22
List of Figures & Tables
Figure 1 - System Context
Diagram ................................................................................... 4
Revision History
3/6 ------ Sections 1-2 complete
3/20 ---- Added section 3
4/3 ----- Added section 4 and on
1 INTRODUCTION
The Engineering Design Support System (EDSS) is a web-based tool designed to
support small to medium engineering teams for concept exploration through
prototyping.
This system is designed to boost teamwork and collaboration throughout the
development
process and serves as a medium to share ideas and documents that may change.
EDSS
also serves as a bulletin board to list the latest changes to requirements and the
latest
proposals by team members and leaders. The system is usable from any platform
via the
Internet and allows cross-platform sharing of documents. EDSS is designed to be the
medium through which teamwork and collaboration occurs.
Competition and the constant changes in technology and lifestyles have changed
the face of banking. Nowadays, banks are seeking alternative ways to provide and
differentiate amongst their varied services. Customers, both corporate as well as
retail, are no longer willing to queue in banks, or wait on the phone, for the most
basic of services. They demand and expect to be able to transact their financial
dealings where and when they wish to. With the number of computers increasing
every year, the electronic delivery of banking services is becoming the ideal way for
banks to meet their clients expectations.
Online banking or e-banking can be defined as online systems which allow
customers to plug into a host of banking services from a personal computer by
connecting with the banks computer over the telephone wires. Technology
continues to make online banking easier for the average consumer. Banks are using
a variety of names for online banking services, such as PC banking, home banking,
electronic banking or Internet banking. Regardless of the given name, these
systems certainly offer specific advantages over the traditional banking methods.
E- Banking can be defined as delivery of banks services to a customer at his office
or home using Electronic Technology. The quality, range and price of these
electronic services decide a banks competitive position in the industry.
Technology in banking has been used in four major ways:
To handle a greatly expanded customer base
To reduce substantially the real; cost of handling payments
To liberate the banks from the traditional constraints on time and place
To introduce new products and services.
1.1 Purpose of the System
Competition: Banks feel the need to offer e-banking services today just to keep up
with the competitors and to be able to retain their existing customers. New Markets:
The Internet is not only a low cost approach to determine new distribution channels
but also to establish a presence in new and upcoming markets. Customer Service:
E-banking offers banks an opportunity to improve on their customer service by
collecting and managing information pertaining to their customers and their
individualistic preferences.
For Customers: Anywhere banking- no matter wherever the customer is in the
world, online banking is just a web- site away. Balance enquiry, request for services,
issuing instructions etc. from anywhere in the world are possible. Consumers can
use their computers and a telephone modem to dial in from home or any site where
they have access to a computer. Anytime banking-managing funds in real time and
most importantly, 24 hours a day, 7 days a week.
For Banks: Innovative, secure, addresses competition and presents the bank as
technology driven in the banking sector market. Reduces customer visits to the
branch and thereby human intervention. This impact tells upon establishment costs
of the bank. Inter-branch reconciliation is immediate thereby reducing chances of
fraud and misappropriation. On- line banking an effective medium of promotion of
various schemes of the bank, a marketing tool indeed. E-Banking site can act as a
revenue earner through promotion activity by consumer corporate. Integrated
customer data paves wave for individualized and customized services. E-Banking
provides competitive advantage to the bank. And provides unlimited network to the
bank and is not limited to the number of branches.
For Merchants and Traders: Increase in business because of increased purchasing
power of the credit card holders and ease with which purchasing can be done. Less
need for merchants or traders to provide credit facility to their customers. Making ecommerce a reality and globalizing the trade. Development of global and loyal
clientele base. Assured immediate payment / settlement. Avoid all the cost and risk
problems involved in handling cash.
1.2 Scope of the System
Electronic banking is the wave of the future. It provides enormous benefits to
consumers in terms of the ease and cost of transactions. But it also poses new
challenges for country authorities in regulating and supervising the financial system
and in designing and implementing macroeconomic policy.
Electronic banking has been around for some time in the form of automatic teller
machines and telephone transactions. More recently, it has been transformed by
the Internet, a new delivery channel for banking services that benefits both
customers and banks. Access is fast, convenient, and available around the clock,
whatever the customer's location plus, banks can provide services more efficiently
and at substantially lower costs.
Electronic banking also makes it easier for customers to compare banks' services
and products, can increase competition among banks, and allows banks to
penetrate new markets and thus expand their geographical reach. Some even see
electronic banking as an opportunity for countries with underdeveloped financial
systems to leapfrog developmental stages. Customers in such countries can access
services more easily from banks abroad and through wireless communication
systems, which are developing more rapidly than traditional wired communication
network.
1.3 Objective and Success Criteria of the Project
The problems or disadvantages of E-Banking are Customers may have to face risky
transaction and fraud. Failure of power supply cause to break down of system. There
will also be a loss of heavy income at times of settlement of higher magnitude. Cost
involved in training staff may not be profitable especially in times of attrition. And
lastly the development of an attitude of lethargy. The way to fix all these it to make
the interface for both the customer and the employee user friendly and very easy to
know. But with some problems thats can be fixed there is always advantages to
the system, which are easy opening and closing of accounts. Making the payment of
merchandise transactions through Debit and Credit cards. It gives reliefs customers
from carrying heavy cash. It enables prompt and speedy operation to clients. And
lastly it saves a lot of time to the customer and convenient access for them.
1.4 Definition of Terms and Acronyms
Action Item General assignment of a task to a group, subgroup, or individual
Data Repository Central collection of data
Document Management Versioning control of documents within the system
EDSS Engineering Design Support System
EDSS Administrator Responsible for adding, deleting, and creating Tier 1
projects
and managing Tier 2 users
Markup - Collection of tags that describe the specifications of an electronic
document, as for formatting
Project Administrator Responsible for overseeing entire project on Tier 2; Must
sign off on project for it to be closed
Prototyping - Creation of a model and the simulation of all aspects of a product
Screen Web page/panel
Team Members Active participants on team responsible for Tier 3 projects
Tier 1 EDSS homepage with links to projects
Tier 2 Project homepage
Tier 3 Team homepage within a project (may have additional subtiers)
Viewers Given access to view pages in the EDSS system without modifying them
1.5 References
Amato-McCoy, D. (2005) Creating virtual value, Bank Systems and Technology,
Vol.1,pp 22-27.
Burke, R.R. (2002), Technology and the Customer Interface: What Consumers want
in the
Physical and Virtual Store, Journal of the Academy of Marketing Science,
Vol.30
No.4, pp 411-32.
2 SYSTEM CONTEXT
E-Banking system is a stand-alone system in which the system focuses on the
systems interface to the external world. What this system would do is have an
interface that asks the customer to login to and shows each person accounts and
how much they have in each. It also lets you transfer money to different accounts.
2.1 System Concept
2.2 Current System

N/A
2.3 System Design (If this is a component or subsystem of a larger
system)
3 REQUIREMENTS
3.1 Functional Requirements
1. Customer must have a valid user id and password to login to the system
2. If a wrong password is given three times in succession, that account will be
locked for a set time depending on how many time they kept entering in the
wrong password. When an invalid password is entered a warning is given to
the user that his account is going to be locked.
3. After the valid user logs in he is shown the list of accounts he/she has with
the bank.
4. On selecting the desired account he is taken to a page which shows the
present balance in the particular account number.
5. User can request details of the last n number of transactions he has
performed. A report can also be taken of this.
6. User can make a funds transfer to another account in the same bank. User is
provided with a transaction password which is different from the login
password.
7. User can transfer funds from his account to any other account with this bank.
If the transaction is successful a notification should appear to the customer,
in case it is unsuccessful, a proper message should be given to the customer
as to why it failed.
8. User can request for check book/change if address/stop payment of checks
9. User can view his monthly as well as annual statements. He can take print
out of the same.
3.2 Nonfunctional Requirements
11# Description Range/
1. 1000 Those not registered with the system shall not be able to enter it. Only
users authorized to 1001 enter the system will have the ability to view the
system.
2. 1002 The system shall be designed so it can be easily be modified.
3. 1003 The system shall be simple to configure and use. The system will not
require its users to adhere to specific organizations of information, and will
not be technically difficult to use.
4. 1004 If access to the system is invalid more than three times then the user
will be locked out for security purposes for a set time depending on how
many time the user tried to get access.
3.3 Functional (Scenario) Analysis
1. Customer must have a valid user id and password to login to the systemif
the customer does not a an account with the bank then they cannot log on.
the user that his account is going to be locked. if the user enters the wrong
password three times they will be denied access for 30 minutes, and if the
enter in the worn password for another three times after the 30 minutes they
will be denied access for 1 hour, each time it doubles.
the bank. they will be given their accounts in a list which they can choose
from.
present balance in the particular account number. the user is shown more
about their account that they have chosen
performed. A report can also be taken of this. the user can see and select
any transaction that has happened in the past that regards the account.
password. the user can transfer money for the system without having to go
to the bank to transfer the funds. But you can only make so many transfers
online. And will be given a transaction password to log on with to make sure
the transaction went through.
as to why it failed. the user will get a notification as to when the
transaction has went through or was denied.
the user can order a check book or change their checks. They can also
change their address for the billing statements. And they can cancel their
account if they wish too.
out of the same. the user will be able to view all transactions in all
accounts on one page and will be prompted if they want to print it or not.
3.3.1 Actors
Actor: Account
Purpose: This will store each account in the bank
Relations: each account will be linked with each person who is the owner of the
account
Actor: Person
Purpose: This will kept track of who and how many people have an account with
the bank
Relations: Each person will be given their own account and will only be able to
access that account. Each person can have multiply accounts
3.3.2 Use-Case 1
Use-Case Name: User
Participating Actors: Person, account
Entry Condition: user to person is one to one, user to account is one to many
3.3.3 Use-Case 2
Use-Case Name: Bank
Participating Actors: Person, account
Entry Condition: bank to person is many to many, Bank to account is many to
many
3.4 Analysis Model

What this system does is holds a database of a person and of an account. Where
each person has multiply accounts that they can access over the interface. And will
only let them access the accounts that are matched with their ID. And the inter face
will let them do all different kinds of things with their account form just checking
their balance on their account to transferring money from account to account. Each
database interacts with each other in the each person and have multiply accounts,
but each account must have at least one person.
3.4.1 System Behavior

The system behavior is that it the user log on at their terminal, it bring them
through the internet to the systems control in which it lets them access their
database records that are linked to their account. And form the bank they are able
to access every ones records in the database using the banks admin terminal.
3.4.2 Object Structure and Behavior

Research design for this study is descriptive. This research is undertaken with an
idea to see customer satisfaction regarding e-banking. The main aim of such a
design is to ensure that the required data collected objectively, accurately and
economically.
3.4.3 Data and Data Relations
APPENDIX A Previous Versions

For Customers: Anywhere banking- no matter wherever the customer is in the
world, online banking is just a web- site away. Balance enquiry, request for services,
issuing instructions etc. from anywhere in the world are possible. Consumers can
use their computers and a telephone modem to dial in from home or any site where
they have access to a computer. Anytime banking-managing funds in real time and
most importantly, 24 hours a day, 7 days a week.
For Banks: Innovative, secure, addresses competition and presents the bank as
technology driven in the banking sector market. Reduces customer visits to the
branch and thereby human intervention. This impact tells upon establishment costs
of the bank. Inter-branch reconciliation is immediate thereby reducing chances of
fraud and misappropriation. On- line banking an effective medium of promotion of
various schemes of the bank, a marketing tool indeed. E-Banking site can act as a
revenue earner through promotion activity by consumer corporate. Integrated
customer data paves wave for individualized and customized services. E-Banking
provides competitive advantage to the bank. And provides unlimited network to the
bank and is not limited to the number of branches.
For Merchants and Traders: Increase in business because of increased purchasing
power of the credit card holders and ease with which purchasing can be done. Less
need for merchants or traders to provide credit facility to their customers. Making ecommerce a reality and globalizing the trade. Development of global and loyal
clientele base. Assured immediate payment / settlement. Avoid all the cost and risk
problems involved in handling cash.
1. Customer must have a valid user id and password to login to the system
the user that his account is going to be locked.
the bank.
present balance in the particular account number.
performed. A report can also be taken of this.
password.
as to why it failed.
out of the same.
Project Plan
4.1 Introduction (Section 1 of the SPMP)
4.1.1 Project Overview (1.1 of the SPMP)
This project is an electronic banking system. This will be in the form of an
application that a user could access. The application will need to be developed in
JAVA, with a proper UI and functionality. The requirements of the product can be
located in tin the <requirements document>
4.1.2 Project Deliverables (1.2 of the SPMP)
1. Requirements document 3/13/2013
2. Project Plan, 3/13/2013
3. Design, 4/1/2013
4. Logs and journals, (throughout project)
5. Progress reports, (throughout project)
6. Final documents, 4/24/2013
4.1.3 Evolution of the SPMP (1.3 of the SPMP)
Not applicable yet to this particular project as it is the first of its kind and has yet to
evolve at this time.
4.1.4 Reference Materials (1.4 of the SPMP)
4.1.5 Donations and Acronyms (1.5 of the SPMP)
Action Item General Assignment of a task to a group, subgroup, or individual
Data Repository Central collection of data
Document Management Versioning control of documents within the system
EDSS Engineering Design Support System
EDSS Administrator Responsible for adding, deleting, and creating Tier 1
projects
and managing Tier 2 users
Markup - Collection of tags that describe the specifications of an electronic
document, as for formatting
Project Administrator Responsible for overseeing entire project on Tier 2; Must
sign off on project for it to be closed

Prototyping - Creation of a model and the simulation of all aspects of a product
Screen Web page/panel
Team Members Active participants on team responsible for Tier 3 projects
Tier 1 EDSS homepage with links to projects
Tier 2 Project homepage
Tier 3 Team homepage within a project (may have additional sub tiers)
Viewers Given access to view pages in the EDSS system without modifying them
4.2 Project Organization (Section 2 of the SPMP)
4.2.1 Process Model (2.1 of the SPMP)
4.2.2 Organizational Structure (2.2 of the SPMP)
4.2.3 Organizational Boundaries and Interfaces (2.3 of the SPMP)

The parent organization would be the company that we work for. The customer
organization would be the bank that requires the system. The bank would tell us
what they need and want in the software. They would also have the final say in the
product and all of the functions in it. They would not have much input during the
coding phase but their requirements would dictate it.
4.2.4 Project Responsibilities (2.4 of the SPMP)
4.3 Management Objectives and Priorities (3.1 of the SPMP)

Everyone will be working on everything to keep collaboration high. It will keep
everyone in the loop for the entirety of the project. It will also be easy to see whos
doing how much of what. Reports will be given at the end of all development stages.
Risks would be the constant barrage of snow days. They have already hindered us
at a few key points. Keeping in contact with all group members might be difficult
and should have an eye kept on it because we all have different schedules. So far
we have had difficulty meeting up sue to different schedules. This risk must be dealt
with. This system will be designed from scratch.
4.3.2 Assumptions, Dependencies, and Constraints (3.2 of the SPMP)
During the project we assume the customer has an action to perform. We assume
that they have and account with the bank already if they are trying to withdraw
money or deposit money. Depending on if they have money, how much money they
can withdraw. The customer must put in the proper pin number. The type of
accounts the user has may change what they can and cant do. (For instance
interest on a savings account vs no interest on a checking account.) This will have
constraints to access the system. The customer must have an account to do any
action.
4.3.3 Risk Management (3.3 of the SPMP)
One big risk that weve taken precautions against is the "this person didn't do
enough", weve split it up so everyone has a part in everything. An issue thats
already popped up is the snow issue and school closing down. Weve already missed
a couple of meetings and finding times to make it up is difficult. Some of us dont
come to the school every day and some of us have class when the others dont,
Others have to leave here and immediately go to work. We have to keep in contact
with each other and figure out each others schedules and maybe find a better
meeting time.
4.3.4 Monitoring and Controlling Mechanisms (3.4 of the SPMP)
We will file reports at the end of all phases. There will be constant contact between
the 4 of us over whos doing what and how its getting done. Monitoring will have to
be done through periodic progress checks by the group leader Erick.

4.3.5 Staffing Plan (3.5 of the SPMP)
So far we have everyone doing a bit of everything so most of the categories are
split. We all have some level of programming knowledge that will come in at the
code phase. The only thing that might be trainable is the concept of how a bank
works. There is no time for training and we cant phase out any members. Everyone
is needed at all points of the project. As for skill level that we all need to have, we
must be able to work with object oriented languages at an object level.
4.4 Technical Process (Section 4 of the SPMP)

4.4.1 Methods, Tools, and Techniques (4.1 of the SPMP)
We will be programming our system out in Java. This project will be very customer
driven. There would be lots of meeting between the coders and the customer (in
this case fictitious), to find out the things that they really require.
4.4.2 Software Documentation (4.2 of the SPMP)
This subsection of the SPMP shall contain either directly or by reference, the
documentation plan for the software project. The documentation plan shall specify
the documentation requirements, and the milestones, baselines, reviews, and signoffs for software documentation. The documentation plan may also contain a style
guide, naming conventions and documentation formats. The documentation plan
shall provide a summary of the schedule and resource requirements for the
documentation effort. ANSI/IEEE Std 829-1983 [4] provides a standard for software
test documentation.
4.4.3 Project Support Functions (4.3 of the SPMP)
This subsection of the SPMP shall contain, either directly or by reference, plans for
the supporting functions for the software project. These functions may include, but
are not limited to, configuration management 3; software quality assurance 2 and 5;
and verification and validation 6. Plans for project support functions shall be
developed to a level of detail consistent with the other sections of the SPMP. In
particular, the responsibilities, resource requirements, schedules, and budgets for
each supporting function shall be specified. The nature and type of support
functions required will vary from project to project; however, the absence of a
software quality assurance, configuration management, or verification and
validation plan shall be explicitly justified in project plans that do not include them.
4.5.1 Work Packages (5.1 of the SPMP)
This subsection of the SPMP shall specify the work packages for the activities and
tasks that must be completed in order to satisfy the project agreement. Each work
package shall be uniquely identified; identification may be based on a numbering
scheme and descriptive titles. A diagram depicting the breakdown of activities into
sub activities and tasks (a work breakdown structure) may be used to depict
hierarchical relationships among work packages.
4.5.2 Dependencies (5.2 of the SPMP)
This subsection of the SPMP shall specify the ordering relations among work
packages to account for interdependencies among them and dependencies on
external events. Techniques such as dependency lists, activity networks, and the
critical path method may be used to depict dependencies among work packages.
4.5.3 Resource Requirements (5.3 of the SPMP)

We will require at least 4 computers to create this piece of software. The personnel
will have general knowledge about the topic. We will require a computer lab for
most of the project. There might be some support software to verify and encrypt pin
numbers (fictitious). Overall the project should take about 40 man-hours to
complete, split into even parts that are 10 man-hours for each worker. As for
hardware it wont be too resource drawing so any plain old computer would
probably run it. There would have to be some sort of support software for a
scanning feature for credit cards. (??????)
4.5.4 Budget and Resource Allocation (5.4 of the SPMP)
We will have to evenly distribute our resources throughout the project. We have no
budget since this is just a programming assignment. We also shouldnt have any
expenditure since we are just coding a fake banking system.
4.5.5 Schedule (5.5 of the SPMP)

E Banking System

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

E Banking System

Uploaded by

Copyright:

Available Formats

E-Banking System

Date of Document Generation

4.5.1 Work Packages (5.1 of the

2.1 System Concept

2.2 Current System

3.4 Analysis Model

3.4.1 System Behavior

3.4.2 Object Structure and Behavior

APPENDIX A Previous Versions

sign off on project for it to be closed

4.2 Project Organization (Section 2 of the SPMP)

4.2.1 Process Model (2.1 of the SPMP)

4.2.2 Organizational Structure (2.2 of the SPMP)

4.2.3 Organizational Boundaries and Interfaces (2.3 of the SPMP)

4.3 Management Objectives and Priorities (3.1 of the SPMP)

be done through periodic progress checks by the group leader Erick.

4.4 Technical Process (Section 4 of the SPMP)

4.5.3 Resource Requirements (5.3 of the SPMP)

You might also like