e bankig report
TRANSCRIPT
-
8/3/2019 E Bankig Report
1/76
E BANKING SYSTEM
CONTENTSCONTENTS INTROD
UCTION 1
Purpose
Scope
Technologies to be used
Overview
SYSTEM
ANALYSIS 3
Feasibility Study
Requirement Analysis and Specification
SRS Document
Hardware and Software Requirements
Database Table Design
SELECT
ED SOFTWARE 19
C#.Net 2008
ORACLE 10g
PROJEC
T DESIGN 36
SCREEN
LAYOUT 41
CODING
50
SYSTEM
TESTING 64
1
-
8/3/2019 E Bankig Report
2/76
E BANKING SYSTEM
MAINTE
NANCE 66
FUTURE
SCOPE OF THIS PROJECT 67
CONCL
USION 69
BIBLIO
GRAPHY 70
REFERE
NCES 71
INTRODUCTIONINTRODUCTION
Purpose
The software programs allowed the users personal computer todial up
the bank directly.
It maintains THREE levels of users:-
Administrator Level
Bank Level
User Level
2
-
8/3/2019 E Bankig Report
3/76
E BANKING SYSTEM
The software includes:-
Maintaining Bank details.
Providing all types of service to users.
Scope
It can be used in any Bank for maintaining Bank details and
providing their service to users easily.
Technologies to be used
This project will be a desktop application to be developed in C#.Net (3.5) as
frontend and Oracle as backend.
Database Design (ORACLE)
Form Design (C#.Net)
Coding (C#.Net)
Testing
Overview
Project is related to E-Banking System
The project maintain three levels of users
Administrator Level-Admin
Bank Level-Manager,Staff
User Level-Customer
Main facilities available in this project are:-
Maintaining records of bank employees.
Maintaining users details and creating account details in bank
directly..
Maintaining users .
3
-
8/3/2019 E Bankig Report
4/76
E BANKING SYSTEM
Maintaining backup of data as per user requirements (between
mentioned dates).
Results of tests, prescription, precautions and diet advice will beautomatically updated in the database with single button-click.
User or Administrator can search the corresponding id and other
details.
Overall Description
Goals of proposed system
Planned approach towards working:-The working in the
organization will be well planned and organized. The data will be stored
properly in data stores, which will help in retrieval of information as
well as its storage.
Accuracy:- The level of accuracy in the proposed system will be
higher. All operation would be done correctly and it ensures that
whatever information is coming from the center is accurate.
Reliability:- The reliability of the proposed system will be high due
to the above stated reasons. The reason for the increased reliability of
the system is that now there would be proper storage of information.
No Redundancy :- In the proposed system utmost care would bethat no information is repeated any where, in storage or otherwise. This
would assure economic use of storage space and consistency in the data
stored.
Immediate retrieval of information:-The main objective of
proposed system is to provide for a quick and efficient retrieval of
information . Any type of information would be available whenever the
user requires.
4
-
8/3/2019 E Bankig Report
5/76
E BANKING SYSTEM
Immediate storage of information:- In manual system there
are may problems to store the largest amount of information.
Easy to Operate:- The system should be easy to operate and
should be such that it can be developed within a short period of time and
fit in the limited budget of the user .
5
-
8/3/2019 E Bankig Report
6/76
E BANKING SYSTEM
SYSTEM ANALYSISSYSTEM ANALYSIS
System Analysis is a process by which we attribute process or goals to a human
activity, determine how well those purpose are being achieved and specify the requirements
of the various tools and techniques that are to be used within the system if the system
performances are to be achieved.
FEASIBILITY STUDYFEASIBILITY STUDY
Feasibility is the measure of how beneficial the development of information
system would be to an organization. Feasibility analysis is the process by which feasibility is
measured. The main aim in feasibility study activity is to determine whether it is financially
and technically feasible to develop the product. The feasibility study activity involve the
analysis of the problem and collecting relevant information relating to the product such as
different items which would be required in the processing by the system. The feasibility study
is carried out to find out whether the proposed system can be developed and implemented
without any problems.
The main aim of feasibility study is to determine whether developing the product is
financially and technically feasible.
The feasibility study involves.
An abstract definition of the problem.
Formation of different solution strategies.
Examination of alternative solution strategies and their benefits, indicating
resources required, developed, cost and time respect of each of the alternative
solution. A cost effective analysis is performed to determine which solution is the
best at this stage , it may also determine whether any of this solution is not feasible
due to the high cost , resource constraint or extraordinary technically reason .
The module is totally feasible in all respect i.e. technically it reduces the time
consuming and in economically it reduces the cost. The feasibility aspect of the project was
considered at the time of the negotiation with the officials and while discussing the same with
the team.
6
-
8/3/2019 E Bankig Report
7/76
E BANKING SYSTEM
BehavioralFeasibility:
People inherently resistant to change. In this phase the analyst estimate that how
strong reaction the user staff is likely to have towards the development of purposed system.
Feasibility study is not warranted for a system in which economic justification is
obvious, technical risk is low, few legal problems are expected and no reasonable alternative
exists. Economic justification is generally the bottom-line consideration for most systems
which includes a broad range of concerns that include cost-benefit analysis, long term
corporate income strategies, impact on other profit centers or products, cost of resources
needed for development and potential market growth. Technical justification mainly
associated with the development risk, resources availability, and technology where as legal
justification encompasses a broad range of concerns that include contracts, liability, and
infringements and myriad other traps frequently unknown to technical staff.
TECHNICAL FEASIBILITY:
During this study, it was found that the organization has enough resources to
implement the new system. There already exists a computer system with suitable hardware
and software in the concerned organization.
Technical feasibility includes 2 main aspects:
Hardware feasibility
Software feasibility
Hardware feasibility
To implement this project we need different types of hardware
configuration for server and client.
Software feasibility
7
-
8/3/2019 E Bankig Report
8/76
E BANKING SYSTEM
This system is developed using vb.net. All the resourses used for the
development of the project are available. The system can be expanded as required in future
and modified with the change of acts and rules . Accuracy, reliability ,ease of access and
security of the system is maximum. The tools to be used are highly reliable, updated and
efficient. Thus the proposed system is technically feasible.
ECONOMICAL FEASIBILITY:
Economical feasibility is the most important study that determines
the cost and benefits of the proposed system and compares with the budget. The cost of the
new system does not outweigh the budget. The cost of the project includes the cost of
hardware, software, development and implementation. The cost of the project includes the
cost of hardware, software, development and implementation. The new system also provides
benefits that are expected from the proposed system and compare these with costs expected to
spent on development of the system. Benefits are found to be more than costs, thus it is
decided to develop new system. The new system provides both tangible and intangible
benefits in a formal way . thus the new system is economically feasible.
OPERATIONAL FEASIBILITY:
It was found that the new system is both economically and
technically feasible, the next step is to be determine whether it is operationally feasible or
not. During operational feasibility study, it was found that the system operates in the way that
user wants. There is enough human resourses and there are qualified and experienced
manpower available for the development and implementation of the system. The new system
is acceptable to the people and management.
1 PERT CHART
Pert Chart stands for Program Evaluation Review Technique, it is a scheduling device
that graphically shows which tasks must be completed before others begins which helps the
developers to go with the required pace to meet the customer requirements. This technique is
mainly used with the complex projects. The planning methods that were used by the PERT
chart that are shown in the figure:
The methods are used to:
Indicate the individual activities and the time needed for each activity.
Shows the inter-relationship of activities.
8
-
8/3/2019 E Bankig Report
9/76
E BANKING SYSTEM
Identifying the proper sequence.
Give time estimation.
Isolate areas where potential problems or delays may occur.
Have means of monitoring progress on the project.
detai
9
System analysis
Feasibility Study Data ModelSRS
Interface Design Input DesignDatabase Design
Coding
Testing
Integration Testing System Testing
System Design
-
8/3/2019 E Bankig Report
10/76
E BANKING SYSTEM
(Figure 1: PERT chart of E BANKING System)
REQUIREMENT ANALYSIS & SPECIFICATIONREQUIREMENT ANALYSIS & SPECIFICATION
REQUIREMENT ANALYSIS:
The goal of the requirement gathering activity is to collect all
relevant information from the custmer and give the desired services . An inconsistent
requirement is one where some part of the requirement contradicts with some other part. On
the other hand, an incomplete requirement is one where some parts of the requirement may
have been omitted altogether. In this project we interviewed a no of custmers ,users of
bank,bank administrator, concern manager , staffs, and other technical and nontechnical
persons of different banks. The data collected from such a group usually contain several
contradictions and ambiguities. Therefore, it is necessary to identify all ambiguities and the
contradictions in the requirements and resolve them through further discussion with the
customer. After all ambiguities, inconsistencies and incompleteness has been resolved and all
the requirements properly understood, the requirement specification starts.
REQUIREMENT SPECIFICATION:
The user requirement identified during the requirement
gathering and analysis activity is organized into a SRS document. The important documents
of these documents are the functional requirements, and goals of implementation.
Documenting the functional requirement involves the identification of the function to be
supported by the system. Each function can be characterized by the input data, the processing
required on the input data and the output data to be produced. The non functional requirement
identifies the performance requirements, the required standard to be followed etc.
10
Project
-
8/3/2019 E Bankig Report
11/76
E BANKING SYSTEM
SOFTWARE REQIREMENTSSOFTWARE REQIREMENTS
SPECIFICATION( SRS )SPECIFICATION( SRS )
11
-
8/3/2019 E Bankig Report
12/76
E BANKING SYSTEM
System requirements can be thought of as a foundation for the system to be developed.SRS is
a document comes as an output of Requirement analysis. This document helps the designer to
design the proposed software.
2.5.1 Introduction
12
SLNO REQUIREMENTS ESSENTIAL
OR
DESIRABLE
DESCRIPTION OF
THE
REQUIREMENTS
REMARKS
RS1 The system should have a
login for administrator or
employees
Essential A login box should
appear when login is
invoked
Login details are
assigned by admin or
employees.
RS2 The administrator should
able to see the home page.
Essential A home page should
have details of the entire
management system
Homepage is seen by
user
RS3 The administrator should
able to see all the
department concern to
bank.
Essential The administrator should
able to insert, delete,
display the information
of various departments.
All department
records are updated.
RS4 The administrator should
able to see the manager
details.
Essential The administrator should
able to see manager
details
manager details are
updated.
RS5 The administrator should
able to see the branch
details..
Essential The administrator should
able to update
branch details.
branch details are
displayed.
RS6 The users should able to
see account details.
Essential The administrator should
able to update branch
details and manager
details.
Account details are
displayed.
RS7 The manager should able
to see the user details .
Essential
The manager should able
to update user details.
The user detail
information are
displayed.
-
8/3/2019 E Bankig Report
13/76
E BANKING SYSTEM
This section of the SRS describes the overview of the proposed system and clarifies the
product features and functions and specifies the purpose, scope, and benefit and goals.
2.5.1.1 Purpose
E Banking System is a system to ensure on time delivery of projects to their clients,
each organization needs to manage the whole process of project development, right from the
beginning of the project to their delivery .To fulfill this requirement, they need E Banking
System. The E Banking System gives a systematic approach towards the development of the
project. All the project ls like communication between the administrator, team leaders and
programmers, feedback analysis during the various phases of project development process,
updating project details and personal details and many more can be handled by this E
Banking System
2.5.1.2 Scope
Proposed software description
The proposed system is completely web based. It is an internet based application. The
administrator and user have their own id and password through which they can login in into
the site. From there administrator can update or retrieve or give feedback to any user. Not
only have that, he can send mails to any user those are registered for making transaction with
the bank. The system is user friendly and can be easily handled. Also, it is very easy to
implement any new thing in this system.
2.5.1.3 Definitions, Acronyms, and Abbreviations
This section provides the definitions of all terms, acronyms, and abbreviations
required to properly interpret the SRS. This information may be provided by reference to one
or more appendices in the SRS or by reference to documents.
SRS-Software Requirement Specification.
13
-
8/3/2019 E Bankig Report
14/76
E BANKING SYSTEM
2.5.2 Overall Description
Projects are the hearts of any software company. In todays scenario, not
only project development but the management of those projects is
also necessary. Companies are dealing with hundreds of project at
a time. Not only that, they have to maintain the records of the
future projects also. So E Banking System adds a remarkable value
towards software development.
Function of the project
Every software company works on several projects for different clients, at a time. To ensure
on time delivery of projects to their clients, each organization needs to manage the whole
process of project development, right from the beginning of the project to their delivery. The
E Banking Systems gives a systematic approach towards the easy process of Banks. This
project has 3 modules. The modules are as follows:
(1) Administrative Module This module if for the top label management of the
projects assigned to the company, like Administrator. Administrator can maintain the
details of the project.
Admin Module is used to enquiry about the bank details along with all the employees
information.
Admin can accept or reject the requests from the bankers or account holders.
The requests are in the form of bank registration, customer registration.
Functionalities:
Pending Bankers Requests: Administrator can give access permissions to
bankers who are registered in this portal.
Pending User Requests: Administrator can give access permissions to all users
who are registered in this portal.
Bank Module
Bank Module is devided into two sub modules.One is manager and other is staff
module. Manager is responsible to keep all type information of staffs as well as the
14
-
8/3/2019 E Bankig Report
15/76
E BANKING SYSTEM
customers.The staffs are responsible to do all the transactions what are requested by the users
or the customers.
Functionalities:
List of Customers
List of Accounts
Money Transfer Details
Money Transfer Rejected Details
Details of request for new account
User Module
In this module a User can search account in Bank & he also give request to Bank
admin to do the work like account open or any complains.
Functionalities:
Create New Account
View Account Information
Transfer Amount
Transaction Reports
2.5.3 SPECIFIC REQUIREMENT
This subsection specifies all the requirements of the proposed system like interface
requirements, all requirements of the user, hardware and software requirements and logical
database requirements.
2.5.3.1 INTERFACE REQUIREMENTS
The blueprint for a house in not complete without a representation of doors, windows,
and utility connection for water, electricity, and telephone. The door, windows, and utility
connection for computer software make up the interface design of a system.
15
-
8/3/2019 E Bankig Report
16/76
E BANKING SYSTEM
User interface design creates an effective communication medium between a human and a
computer.Interface requirements of E Banking System are stated below.
Simple Interface:
Interface can be thought of as a middle layer between the user and software , it allows
the user to use the software conditioning the fact that the user might not be a computer expert
rather than a novice in this field. So considering this fact the interface should be simple
enough to be use by E Banking System authorities. The interface shall be supportive enough
to allow the user to use this software conveniently.
Low Graphics:
Normally graphics is used to make the design of the interface attractive. But
unfortunately it makes the Interface complex and takes more memory, which eventually
cause the to work software slow. So the graphics should be kept minimum and it should only
be used if situation arises.
Consistent:
\ The interface should present and acquire information in a consistent fashion. Most ofthe pages of the website shall follows a consistent standard, which gives an familiar view to
the user and he things he is acquainted with the things earlier. Input mechanisms shall
constrain to a limited set that is used consistently throughout the application and the
mechanism of navigation from task to task are consistently defined and implemented.
Error Message:
The user interface shall be designed in such a manner that it shall shows appropriate error
message if the user commits any mistake and shall allows him to correct thereto. Error
Message should provide a hint where the user has committed the mistake for instance if the
user has entered the wrong userId no then the error should be prompted as You have
entered wrong userId no rather than simple an error message.
16
-
8/3/2019 E Bankig Report
17/76
E BANKING SYSTEM
2.5.3.2 PERFORMANCE REQUIREMENTS
This subsection specifies both the static and the dynamic numerical requirements placed
on the software or on human interaction with the software, as a whole these are specified
below.
E Banking System shall support any number of terminals that are accessing the data
from server at a time. Each time a new user comes the server will create a new thread
to give service to the user.
E Banking System shall not allow any deadlock to occur in the mid of the process.
2.5.3.3 USER REQUIREMENTS
E Banking System mainly deals with to user who hava a id in the bank and they can make
transaction directly.
HARDWARE AND SOFTWARE REQIREMENTSHARDWARE AND SOFTWARE REQIREMENTS
HARDWARE REQUIREMENTS:
To develop or implement this project we need different types of
hardware configuration for server and client.
The Client Machines ---
Processor : Intel Pentium IV or more
Ram : 512MB or more
Cache : 512 KB
Hard disk : 80 GB
Speed : 2.2 GHz
Keyboard : Standard
The Server Machines --
Processor : Intel Pentium IV or more
Ram : 512 MB or more
Cache : 512 KB
Hard disk : 80 GB
17
-
8/3/2019 E Bankig Report
18/76
E BANKING SYSTEM
SOFTWARE REQUIREMENTS:
This project was developed by using different types of software which havelisted below:
Operating system : WINDOWS 2000/WINDOWS XP or more
Front end : c# 2008
Back end : Oracle-10g
DATABASE TABLE DESIGNDATABASE TABLE DESIGN
DATA DESIGN:
The data design transforms the information domain model created during
analysis into data structure that will require implementing the software.
Data design is first of the design activities that are conducted during software engineering.
The primary activity during data design is to be select logical representation of data objects
identified during requirement specification phase.
In this phase we are more concerned with database design. This is an activity consisting of
identifying that portion of the enterprise for which the data application is being designed: the
entity sets the integrated collection of data is called a Database.
In database design, information like table name, key fields, table description, and details of
each field in the table is given. Database Systems are designed to manage large bodies of
information.
DBMS is the bridge between Application Program, which determines the need of data and
how they are processed, and the operating system of computer.
18
-
8/3/2019 E Bankig Report
19/76
E BANKING SYSTEM
TABLE DESIGN:
Table1: LOGIN
FIELDNAME DATATYPE SIZE CONSTRAINT DESCRIPTION
USERNAME VARCHAR2 20 NOT NULL USERNAME
PASSWORD VARCHAR2 15 NOT NULL PASSWORD
This table keeps track of all the members identity and their
passwords. The administrative members only can access this table. It contains the data
of Administrator.
Table2: MANAGER
FIELDNAME DATATYPE SIZE CONSTRAINT DESCRIPTION
BRANCH_ID VARCHAR2 20 FOREIGN KEY BRANCH_ID
MDATE VARCHAR2 NOT NULL MANAGER DATE
MANAGER_ID VARCHAR2 20 PRIMARY KEY MANAGER ID
MNAME VARCHAR2 250 NOTNULL MANAGER NAME
MQUAL VERCHAR2 75 NOTNULL MANAGER
QUALIFICATION
JOB_EX VARCHAR2 50 NOT NULL JOB EXPERIENCE
GENDER VARCHAR2 15 NOT NULL GENDER
D:O:B VARCHAR2 25 NOT NULL DATE OF BIRTH
AGE NUMBER 3 NOT NULL MANAGER AGE
PHNO NUMBER 12 NOT NULL MANAGER PHONE
NO
FAXNO NUMBER 12 NOT NULL FAX NO
EMAIL_ID VARCHAR2 120 NOT NULL EMAIL_ID
PRES_ADDRESS VARCHAR2 450 NOT NULL PRESENT ADDRESS
PER_ADDRESS VARCHAR2 450 NOT NULL PERMANENTADDRESS
19
-
8/3/2019 E Bankig Report
20/76
E BANKING SYSTEM
PROOF VARCHAR2 50 NOT NULL IDENTIFICATION
PROOF
PASSWORD VARCHAR2 20 NOT NULL PASSWORD
This table keeps the history of all MANAGER present in our
organization.
Table3: BRANCH
FIELDNAME DATATYPE SIZE CONSTRAINT DESCRIPTION
BRANCH_ID VERCHAR2 25 PRIMARY KEY BRANCH ID
BRANCH_NAME VARCHAR2 150 NOT NULL BRANCH NAME
ADDRESS VARCHAR2 200 NOT NULL BRANCH ADDRESS
PHNO VERCHAR2 15 NOT NULL BRANCH PHONE NO
FAX VARCHAR2 10 NOT NULL BRANCH FAX NO
EMAIL_ID VERCHAR2 75 NOT NULL BRANCH EMAIL ID
This table keeps the history of all branch working under our
organization.
Table4: STAFF
FIELDNAME DATATYPE SIZE CONSTRAINT DESCRIPTION
BRANCH_ID VARCHAR2 20 NOT NULL BRANCH ID
MDATE DATE NOT NULL CURRENT DATE
MANAGER_ID VARCHAR2 20 FOREIGN KEY MANAGER ID
STAFF_NAME VARCHAR2 125 NOT NULL STAFF NAME
SQUAL VERCHAR2 10 NOT NULL STAFF
QUALIFICATION
JOB_EX VERCHAR2 50 NOT NULL STAFF JOB
EXPERIENCE
AGE NUMBER 3 NOT NULL STAFF AGE
GENDER VARCHAR2 15 STAFF GENDER
PRES_ADDRESS VARCHAR2 450 STAFF PRESENT
ADDRESS
20
-
8/3/2019 E Bankig Report
21/76
E BANKING SYSTEM
PER_ADDRESS VARCHAR2 450 STAFF
PERMANENT
ADDRESS
PASSWORD VARCHAR2 20 NOT NULL STAFF
PASSWORD
PHNO NUMBER 12 NOT NULL STAFF PHONE NO
FAXNO NUMBER 12 NOT NULL STAFF FAX NO
DOB VERCHAR2 25 NOT NULL STAFF DATE OF
BIRTH
EMAIL VERCHAR2 120 NOT NULL STAFF EMAIL
This table keeps the entire history of the STAFF who are
joined in to a bank.
Table5:ADMIN
FIELDNAME DATATYPE SIZE CONSTRAINT DESCRIPTION
ADMIN
_EMAILID VARCHAR2 75 PRIMARY
KEY
ADMIN EMAIL ID
ADMIN_NAME VARCHAR2 20 NOT NULL ADMIN NAME
PASSWORD VERCHAR2 20 NOT NULL ADMIN PASSWORD
ADDRESS VARCHAR2 200 NOT NULL ADMIN ADDRESS
PHNO NUMBER 15 NOT NULL ADMIN PHONE NO
DOB VARCHAR2 50 NOT NULL ADMIN DATE OF BIRTH
GENDER VERCHAR2 40 NOT NULL GENDER
DATE_OF_REGD VERCHAR2 15 NOT NULL DATE OF REGISTRATION OF
ADMIN
This table keeps all the informations about the admin of a bank.
21
-
8/3/2019 E Bankig Report
22/76
E BANKING SYSTEM
Table6: WITHDRAWAL
FIELDNAME DATATYPE
SIZ
E
CONSTRAIN
T
DESCRIPTION
AC_NO NUMBER
18 NOT NULL ACCOUNT NO
TYPE_AC VARCHAR2
30 NOT NULL TYPE OF ACCOUNT
C_DATE DATE
15 FOREIGN
KEY
WITHDRAWL DATE
CUST_NO NUMBER
30 NOT NULL CUSTMER NO
WITH_AMT NUMBER
7,2 NOT NULL WITHDRAWL AMOUNT
CHEQUE VARCHAR2
7 NOT NULL CHEQUE
This table keeps all the in formations about which customer withdraw
how much money from the bank.
TABLE 7: DEPOSIT
C_ACCOUNT VARCHAR2 75 Primary
key
C_IDNO NUMBER 12 Not null
C_NAME VARCHAR2 150 Not null
ACC_TYPE VARCHAR2 35 Not null
DDATE DATE Not null
SOR NUMBER 15 Not null
DEPOSIT_BY VARCHAR2 25 Not nullBANK_NAME VARCHAR2 25 Not null
DDNO VARCHAR2 17 Not null
CHQNO VARCHAR2 15 Not null
D_NAME VARCHAR2 80 Not null
SELECTEDSELECTED SOFTWARESOFTWARE
22
-
8/3/2019 E Bankig Report
23/76
E BANKING SYSTEM
The selected software for the project includes frontend as C#.NET andThe selected software for the project includes frontend as C#.NET and
back end as ORACLE 10g both are relevant topic of discussion in this context as knowing theback end as ORACLE 10g both are relevant topic of discussion in this context as knowing the
basics will help in development of project easier and faster.basics will help in development of project easier and faster.
INTRODUCTION TOINTRODUCTION TO MICROSOFT.NETMICROSOFT.NETMicrosoft .NET is a new framework for building applications.This new
framework allows developers to write applications faster and with less codes.
The .NET framework works with a variety of languages namely C#, VB.NET, POWER
BUILDER.NET, and DELPHI.NET etc. The advantage of multiple languages support is that
we dont need to tie ourselves down to a single language. We also dont need to rewrite all of
our existing code to make use of its benefits. We can create all the new code in .NET and
leave the legacy code alone and we can have the legacy code call the new .NET code.
.NET enables modern communications through standard internet protocols such as XML and
SOAP. Through the use of Web Services we open a whole new world of communication. The
end result of .NET is that it makes it far easier for developers to write and maintain programs
that solve complex business problems.
DATA ACCESS
.NET applications can access a variety of data sources such as SQL Server, Oracle Server,
Access, ODBC and OLEDB databases through ADO.NET,ADO.NET accesses data in a
generic fashion. We can switch databases with minimal changes to our source code.It allows
support for disconnected data and XML support.
MICROSOFT.NETMICROSOFT.NET FRAMEWORKFRAMEWORK
Microsoft .NET framework consists of many parts. It no longer makes a
difference as too what language we use for our application. As we can see below, the
Common Language Runtime (CLR) which provides the core .NET functionality is the same
regardless of language. Above the CLR is the .NET framework class library which provides
all the Windows functionality for building an application such as drawing menus, file
handling, networking, and so forth. And above that are the .NET languages. So we can see
that regardless of the languge we have access to same .NET functionality.
The Common Language Runtime(CLR) is responsible for providing a consistent set of
services to .NET applications. The CLR manages memory, handles security, the basics
datatypes, and error handling.
23
-
8/3/2019 E Bankig Report
24/76
E BANKING SYSTEM
COMPONENTS OF .NET
.NET framework has two main components. They are:
1. Common Language Runtime
2. .NET class library
COMMON LANGUAGE RUNTIME
The Common Language Runtime (CLR) is the environment where all
programs in .NET are run. It provides various services, like memory management and thread
management. Programs that run in the CLR need not manage memory, as it is completely
taken care of by the CLR. For example, when a program needs a block of memory, CLR
provides the block and releases the block when program is done with the block.All programstargeted to .NET are converted to MSIL (Microsoft Intermediate Language). MSIL is the
output of language compilers in .NET . MSIL is then converted to native code by JIT (Just-in
Time Compiler) of the CLR and then native code is run by CLR.
As every program is ultimately converted to MSIL in .NET, the choice of language is pure
personal. A program written in VB.NET and a program written in C# are both converted to
MSIL. Then MSIL is converted to native code and run. So, whether you write program in C#
or VB.NET at the end it is MSIL all that you get.
MSIL in .NET is same as Bytecode in concept. CLR is same as JVM (Java virtual
machine)..NET CLASS LIBRARY
.NET comes with thousands of classes to perform all important and not-so-important
operations. Its library is completely object oriented, providing around 5000 classes to
perform just about everything.
24
http://itxt.vibrantmedia.com/al.asp?ipid=111&cc=us&ai=15598777&di=23269&ts=20040122055531&redir=http://www60.overture.com/d/sr/?xargs=02u3hs9yoaj1VuzTCDhBBm30Vvb2vgbAew1wduUvQ5AR4rdn4kMFJ5KBL7qVNq6qtOzNHrN7D%2F8nYr4W%2BMPbtTGa5kmhECyNZasIhJMT1ohEs9azHHvMzNdRZe4If6uxj22%2Fq8usPkvWfx9tCPkUgjk3Z9rPJwjKIHuEgIUgpUCQl62sac3m8Xmhp2TuTd4itIKbQirKCrn9%2BXlNSVWOpr%2BKo%2Buj4wIXOmbIaLZSqCF5hSpgWXy8S4nfyZlhOVy2YFrKcIzAB%2FaRzZUQ%3D%3Dhttp://itxt.vibrantmedia.com/al.asp?ipid=111&cc=us&ai=15598777&di=23269&ts=20040122055531&redir=http://www60.overture.com/d/sr/?xargs=02u3hs9yoaj1VuzTCDhBBm30Vvb2vgbAew1wduUvQ5AR4rdn4kMFJ5KBL7qVNq6qtOzNHrN7D%2F8nYr4W%2BMPbtTGa5kmhECyNZasIhJMT1ohEs9azHHvMzNdRZe4If6uxj22%2Fq8usPkvWfx9tCPkUgjk3Z9rPJwjKIHuEgIUgpUCQl62sac3m8Xmhp2TuTd4itIKbQirKCrn9%2BXlNSVWOpr%2BKo%2Buj4wIXOmbIaLZSqCF5hSpgWXy8S4nfyZlhOVy2YFrKcIzAB%2FaRzZUQ%3D%3D -
8/3/2019 E Bankig Report
25/76
E BANKING SYSTEM
C# .NET (VB.NET) is an object-oriented computer language that can be viewed as an
evolution of Microsoft's C# implemented on the Microsoft .NET framework. The great
majority of C#.NET developers use Visual Studio .NET as their integrated development
environment (IDE).
For example, the .NET Framework collection classes implement a set of interfaces that you
can use to develop your own collection classes. Your collection classes will blend seamlessly
with the classes in the .NET Framework.
As you would expect from an object-oriented class library, the .NET Framework types enable
you to accomplish a range of common programming tasks, including tasks such as string
management, data collection, database connectivity, and file access. In addition to thesecommon tasks, the class library includes types that support a variety of specialized
development scenarios. For example, you can use the .NET Framework to develop the
following types of applications and services:
Console applications.
Scripted or hosted applications.
Windows GUI applications (Windows Forms).
ASP.NET applications.
XML Web services.
Windows services.
For example, the Windows Forms classes are a comprehensive set of reusable types that
vastly simplify Windows GUI development. If you write an ASP.NET Web Form
application, you can use the Web Forms classes.
Client Application Development
Client applications are the closest to a traditional style of application in Windows-based
programming. These are the types of applications that display windows or forms on the
desktop, enabling a user to perform a task. Client applications include applications such as
word processors and spreadsheets, as well as custom business applications such as data-entry
tools, reporting tools, and so on. Client applications usually employ windows, menus,
25
http://en.wikipedia.org/wiki/Object-oriented_programminghttp://en.wikipedia.org/wiki/Computer_languagehttp://en.wikipedia.org/wiki/Microsofthttp://en.wikipedia.org/wiki/.NET_Frameworkhttp://en.wikipedia.org/wiki/Microsoft_Visual_Studiohttp://en.wikipedia.org/wiki/Integrated_development_environmenthttp://en.wikipedia.org/wiki/Integrated_development_environmenthttp://en.wikipedia.org/wiki/Object-oriented_programminghttp://en.wikipedia.org/wiki/Computer_languagehttp://en.wikipedia.org/wiki/Microsofthttp://en.wikipedia.org/wiki/.NET_Frameworkhttp://en.wikipedia.org/wiki/Microsoft_Visual_Studiohttp://en.wikipedia.org/wiki/Integrated_development_environmenthttp://en.wikipedia.org/wiki/Integrated_development_environment -
8/3/2019 E Bankig Report
26/76
E BANKING SYSTEM
buttons, and other GUI elements, and they likely access local resources such as the file
system and peripherals such as printers.
Another kind of client application is the traditional ActiveX control (now replaced by the
managed Windows Forms control) deployed over the Internet as a Web page. This
application is much like other client applications: it is executed natively, has access to local
resources, and includes graphical elements.
In the past, developers created such applications using C/C++ in conjunction with the
Microsoft Foundation Classes (MFC) or with a rapid application development (RAD)
environment such as Microsoft Visual Basic. The .NET Framework incorporates aspects
of these existing products into a single, consistent development environment that drasticallysimplifies the development of client applications.
The Windows Forms classes contained in the .NET Framework are designed to be used for
GUI development. You can easily create command windows, buttons, menus, toolbars, and
other screen elements with the flexibility necessary to accommodate shifting business needs.
For example, the .NET Framework provides simple properties to adjust visual attributes
associated with forms. In some cases the underlying operating system does not support
changing these attributes directly, and in these cases the .NET Framework automatically
recreates the forms. This is one of many ways in which the .NET Framework integrates the
developer interface, making coding simpler and more consistent.
Unlike ActiveX controls, Windows Forms controls have semi-trusted access to a user's
computer. This means that binary or natively executing code can access some of the
resources on the user's system (such as GUI elements and limited file access) without being
able to access or compromise other resources. Because of code access security, many
applications that once needed to be installed on a user's system can now be safely deployed
through the Web. Your applications can implement the features of a local application while
being deployed like a Web page.
Server Application Development
Server-side applications in the managed world are implemented through runtime hosts.
Unmanaged applications host the common language runtime, which allows your custom
26
-
8/3/2019 E Bankig Report
27/76
E BANKING SYSTEM
managed code to control the behavior of the server. This model provides you with all the
features of the common language runtime and class library while gaining the performance
and scalability of the host server.
The following illustration shows a basic network schema with managed code running in
different server environments. Servers such as IIS and SQL Server can perform standard
operations while your application logic executes through the managed code.
Server-side managed code
ASP.NET is the hosting environment that enables developers to use the .NET Framework to
target Web-based applications. However, ASP.NET is more than just a runtime host; it is a
complete architecture for developing Web sites and Internet-distributed objects using
managed code. Both Web Forms and XML Web services use IIS and ASP.NET as the
publishing mechanism for applications, and both have a collection of supporting classes in
the .NET Framework.
XML Web services, an important evolution in Web-based technology, are distributed, server-
side application components similar to common Web sites. However, unlike Web-based
applications, XML Web services components have no UI and are not targeted for browsers
such as Internet Explorer and Netscape Navigator. Instead, XML Web services consist of
reusable software components designed to be consumed by other applications, such as
traditional client applications, Web-based applications, or even other XML Web services. As
a result, XML Web services technology is rapidly moving application development and
deployment into the highly distributed environment of the Internet.
If you have used earlier versions of ASP technology, you will immediately notice the
improvements that ASP.NET and Web Forms offers. For example, you can develop Web
Forms pages in any language that supports the .NET Framework. In addition, your code no
longer needs to share the same file with your HTTP text (although it can continue to do so if
you prefer). Web Forms pages execute in native machine language because, like any other
managed application, they take full advantage of the runtime. In contrast, unmanaged ASP
pages are always scripted and interpreted. ASP.NET pages are faster, more functional, and
easier to develop than unmanaged ASP pages because they interact with the runtime like any
managed application.
27
-
8/3/2019 E Bankig Report
28/76
E BANKING SYSTEM
The .NET Framework also provides a collection of classes and tools to aid in development
and consumption of XML Web services applications. XML Web services are built on
standards such as SOAP (a remote procedure-call protocol), XML (an extensible data
format), and WSDL (the Web Services Description Language). The .NET Framework is built
on these standards to promote interoperability with non-Microsoft solutions.
For example, the Web Services Description Language tool included with the .NET
Framework SDK can query an XML Web service published on the Web, parse its WSDL
description, and produce C# or Visual Basic source code that your application can use to
become a client of the XML Web service. The source code can create classes derived from
classes in the class library that handle all the underlying communication using SOAP and
XML parsing. Although you can use the class library to consume XML Web services
directly, the Web Services Description Language tool and the other tools contained in the
SDK facilitate your development efforts with the .NET Framework.
If you develop and publish your own XML Web service, the .NET Framework provides a set
of classes that conform to all the underlying communication standards, such as SOAP,
WSDL, and XML. Using those classes enables you to focus on the logic of your service,
without concerning yourself with the communications infrastructure required by distributed
software development.
Finally, like Web Forms pages in the managed environment, your XML Web service will run
with the speed of native machine language using
C# .NET provides the easiest, most productive language and tool for rapidly building
Windows and Web applications. C# .NET comes with enhanced visual designers,
increased application performance, and a powerful integrated development
environment (IDE). It also supports creation of applications for wireless, Internet-
enabled hand-held devices. The following are the features of C# .NET with .NET
Framework 1.0 and Visual Basic .NET 2003 with .NET Framework 1.1. SOME
FEATURES OF C#.NET:
Powerful Windows-based Applications
28
-
8/3/2019 E Bankig Report
29/76
E BANKING SYSTEM
C# .NET comes with features such as a powerful new forms designer, an in-place
menu editor, and automatic control anchoring and docking. C# .NET delivers new
productivity features for building more robust applications easily and quickly. With an
improved integrated development environment (IDE) and a significantly reduced
startup time, C# .NET offers fast, automatic formatting of code as you type, improved
IntelliSense, an enhanced object browser and XML designer, and much more.
Building Web-based Applications
With C# .NET we can create Web applications using the shared Web Forms Designer
and the familiar "drag and drop" feature. You can double-click and write code to
respond to events. Visual Basic .NET 2008 comes with an enhanced HTML Editorfor
working with complex Web pages. We can also use IntelliSense technology and tag
completion, or choose the WYSIWYG editor for visual authoring of interactive Web
applications.
Simplified Deployment
With Visual Basic .NET we can build applications more rapidly and deploy and
maintain them with efficiency.
Powerful, Flexible, Simplified Data Access
You can tackle any data access scenario easily with ADO.NET and ADO data access.
The flexibility of ADO.NET enables data binding to any database, as well as classes,
collections, and arrays, and provides true XML representation of data. Seamless
access to ADO enables simple data access for connected data binding scenarios. Using
ADO.NET, Visual Basic .NET can gain high-speed access to MS SQL Server, Oracle,
DB2, Microsoft Access, and more.
29
http://www.startvbdotnet.com/dotnet/vbnet.aspxhttp://www.startvbdotnet.com/dotnet/vbnet.aspxhttp://www.startvbdotnet.com/dotnet/vbnet.aspxhttp://www.startvbdotnet.com/dotnet/vbnet.aspx -
8/3/2019 E Bankig Report
30/76
E BANKING SYSTEM
Improved Coding
You can code faster and more effectively. A multitude of enhancements to the code
editor, including enhanced IntelliSense, smart listing of code for greater readability
and a background compiler for real-time notification of syntax errors transforms into a
rapid application development (RAD) coding machine.
Direct Access to the Platform
C# developers can have full access to the capabilities available in .NET Framework
1.1. Developers can easily program system services including the event log,
performance counters and file system. The new Windows Service project template
enables to build real Microsoft Windows NT Services. Programming against
Windows Services and creating new Windows Services is not available in Visual
Basic .NET Standard, it requires Visual Studio 2003 Professional, or higher.
Full Object-Oriented Constructs
You can create reusable, enterprise-class code using full object-oriented constructs.
Language features include full implementation inheritance, encapsulation, and
polymorphism. Structured exception handling provides a global error handler and
eliminates spaghetti code.
ACTIVEX DATA OBJECTS .NET
ADO .NET OVERVIEW
ADO.NET is an evolution of the ADO data access model that directly
addresses user requirements for developing scalable applications. It was designed
specifically for the web with scalability, statelessness, and XML in mind.
30
http://www.startvbdotnet.com/dotnet/vbnet.aspxhttp://www.startvbdotnet.com/dotnet/vbnet.aspx -
8/3/2019 E Bankig Report
31/76
E BANKING SYSTEM
ADO .NET uses some ADO objects, such as the connection and the command
objects and also introduces new objects. Key new ADO.NET objects include the data
set, datareader and data adaptor.
The important distinction between this evolved stage of ADO.NET and previous
data architecture is that there exists an object the data seti.e. separate and distinct
from any data stores. Because of that the data set functions as a stand-alone entity.
You can think of the data set as an always disconnected record set that knows nothing
about the source or destination of the data it contains. Inside a data set, much like a
database, there are tables, columns, relationships, constraints, views and so forth.
A data adapter is an object that connects to the database to fill the data
set. Then, it connects back to the database to update the data there, based on
operations performed while the data set held the data. In the past, data processing has
been primarily connection based. Now, in an effort multi-tiered app more efficient,
data processing is turning to be a message based approach that resolves around chunks
of information. At the center of this approach is the data adapter , which provides a
bridge to retrieve and save data between a data set and its source data store. It
accomplishes this by means of request to the appropriate SQL commands made
against the data store.
The XML based data set object provides a consistent programming
model that works with all models of data storage: flat, relational, hierarchical. It does
this by having no knowledge of the source of its data, and by representing the data that
it holds as collections and data types. No matter what the source of the data within the
data set is, it is manipulated through the same set of APIs exposed through the data set
and its sub-ordinate objects.
While the data set has no knowledge of the source of its data, the managed provider
has detailed and specific information. The role of the managed provider is to connect,
fill and persist the data set to and from the data source. The OLEDB and SQL
server .NET data providers (System.Data.Oledb and System.Data.Sqlclient) that are
31
-
8/3/2019 E Bankig Report
32/76
E BANKING SYSTEM
the part of the .NET frame provide four basic objects: the command, connection, data
reader, data adapter. In the remaining sections of this document we will walk through
each part of the data set and the oledb/SQL server .NET data providers explaining
what they are, and how to program against them.
The following sections will introduce you to some objects that have evolved, and
some that are new. These objects are:-
Connection- for connection and managing transactions against the database.
Commands-for issuing SQL commands against the data base.
Data readers-for reading a forward-only stream of data records from a SQL
server data source.
Data sets-for storing, remoting and programming against flat data, XML data
and relational data.
Data adapters-for pushing data into a data set, and reconciling data against a
data base
When dealing with connections to a database there are two different options: SQL
server .NET data provider (System.Data.Sqlclient and System.Data.Oledb). In these
samples we will use the SQL server .NET data provider. These are written to talk
directly to Microsoft SQL server. The oledb .NET data provider is used to talk to any
oledb provider as it uses oledb underneath.
CONNECTIONS
Connections are used to talk to databases, and are represented by provider specific
classes such as SQL connection. Commands travel over connections and result sets
are returned in the form of strings which can be read by a data reader object or pushed
into a data set object.
COMMANDS
Commands contain the information that is submitted to the database and are
represented by provider specific classes such as SQL command. A command can be
32
-
8/3/2019 E Bankig Report
33/76
E BANKING SYSTEM
stored procedure call and UPDATE statement or a statement that returns results. You
can also use input and output parameters and return values as a part of your command
syntax. The example below shows how to issue an INSERT statement against the
North Wind database.
DATA READERS
The data reader object is somewhat synonymous with a read-only/forward-only cursor
over data. The data reader API supports flat as well as hierarchical data. A data reader
object is returned after executing a command against a database. The format of the
returned data reader object is different from a record set. For example, you might see
the data reader to show the result of a search list in a web page.
DATA SETS AND DATA ADAPTERS
DATA SETS-The data set object is similar to the ADO record set object, but
more powerful, and with one other important distinction: the data set is always
disconnected. The data set object represents a cache of data, with data base like
structures such as tables, columns, relationships, and constraints. However,
though a data set can and does behave much like a data base, it is important to
remember that data set object do not interact directly with databases, or with
other source data. This allows the developer to work with a programming
model that is always consistent, regardless of where the source data resides.
Data coming from a data base, and XML file, from code, or user input can all
be placed into data set objects. Then, as changes are made to the data set they
can be trapped and verified before updating the source data .The GetChanges
method of the dataset object actually creates a second dataset that contains only
the changes to the data.These data set is only used by a data adapter(or other
objects) to update the original data source.
The dataset has many XML characteristics including the ability to produce and
consume XML data and XML schemas.XML schemas can be used to describe
schemas interchanged via WebServices. In fact, a data set with a schema can
actually be compiled for type safety and statement completion.
33
-
8/3/2019 E Bankig Report
34/76
E BANKING SYSTEM
DATA ADAPTER(OLEDB/SQL)
The data adapter object works as a bridge between the data set and the source data.
Using the provider-specific SQL data adapter (along with its associated SqlComand
and SqlConnection) can increase overall performance when working with a Microsoft
sql server databases. For other OLEDB supported databases, you would use the
OleDBDataAdapter and its associated OleDbCommand and OleDbConnection.
The data adapter objects uses command to update the data source after changes have
been made to the data source. Using the fill method of the data adapter calls the
SELECT command; using the update method calls the INSERT, UPDATE OR
DELETE command for each changed row. You can explicitly set this command in
order to control the statements used at run time to resolve changes, including the use
of stored procedures. For ad-hoc scenarios command build objects can generate these
at runtime to base upon a select statement. However, this run time generation requires
an extra round trip to the server. In order to gather required mete data, so explicitly
providing the INSERT, UPDATE, and DELETE command at design time will result
in better run time performance.
ORACLE 10gORACLE 10g
DATABASE
A database management system, or DBMS, gives the user access to the data and
helps them transform the data into information. Such database management systeminclude dBase, Paradox,
IMS and Oracle. This system allows users to create, update and extract information
from the database.
A database is a structured collection of data.Data refers to the characteristics of
people, things and events. Oracle stores each items in its own fields. In oracle, the
fields relating to a particular person, things or events are bundled together to form a
34
-
8/3/2019 E Bankig Report
35/76
E BANKING SYSTEM
single complete unit of data, called a record.Each record is made upof a number of
fields. No two fields in a record can have the same fields name.
ORACLE TABLES
Oracle stores records relating to each other in a table. Different tables are created for
the various groups of information.Related tables are grouped together to form a
database.
PRIMARY KEY
Every tables in oracle has a fields or a combination of fields that uniquely identifieseach records in the table.The unique identifier is called the Primary Key. The primary
key provides the means to distinguish one record from all other in a table.It allows the
user and the database system to identify, locate and refer to one particular record in
database.
RELATIONAL DATABASE
Oracle makes it very easy to link the data in multiple tables.This what makes oracle a
relational database management system or RDBMS.It stores data in two or more
tables and enables us to define relationships between the tables.
FOREIGN KEY
When a field in one table maches the primary key of another field is refer to as aFOREIGN KEY.A Foreign Key is a field or a group of fields in one table whose
values match those of the Primary Key of another table.
REFERENTIAL INTEGRITY
Oracle allows us to maintain consistency between multiple tables.Ensuring that the
data among related tables is correctly matched is refered to as maintaining Referetial
Integrity.DATA ABSTRACTION
35
-
8/3/2019 E Bankig Report
36/76
E BANKING SYSTEM
A major purpose of a database system is to provide users withan abstract view of the
data. This system hides certain details of how the data is stored and maintained.Data
abstraction is divided into three levels:-
Physical Level :- The lowest level of abstraction at which one describes how
the data are actually stored
Conceptual Level :- The level database abstraction that describes what data are
actually stored and relationship among them.
View Level :- The highest level of abstraction which describes only part of the
database.
ADVANTAGES OF RDBMS
Redundancy can be avoided
Inconsistency can be eliminated
Data can be shared
Standards can be enforced
Security restriction can be applied
Integrity can be maintained
Conflicting requirements can be balanced
Data indepedency can be achived.
DISADVANTAGES OF RDBMS
A Significant disadvantage of the DBMS system is cost. In addition to the cost of
purchasing or developing the software, the hardware has to be upgraded to allow for
the extensive programs and the works space required for their execution and
storage.While centralization reduces duplication, the lack of duplication requires that
the database be adequately backed up so that in case of failure the data can be
recovered.
FEATURES OF ORACLE 10g
The following are some of the important features of Oracle 10g.
36
-
8/3/2019 E Bankig Report
37/76
E BANKING SYSTEM
Large Database Support
Oracle supports largest database, potentially hundreds of pita bytes in size. It also
allows efficient usage of space by providing full control on space management.
Data Concurrence
Oracle supports concurrent access to database by multiple users. It automatically
locks and unlocks rows to maintain integrity of the data.
Industry acceptance standards
Oracle server is 100% compliant with Entry of the ANSI / ISO standards. Oracleadheres to industry standards for data access language, network protocols etc. This
makes Oracle an open system, which protects the investment of customer. It is easy
to port Oracle applicationsThe following are some of the important features of Oracle
10g
Oracle supports largest database, potentially hundreds of pita bytes in size. It also
allows efficient usage of space by providing full control on space management
Oracle supports concurrent access to database by multiple users. It automatically
locks andunlocks rows to maintain integrity of the data.Oracle server is 100%
compliant with Entry of the ANSI / ISO standards. Oracle adheres to industry
standards for data access language, network protocols etc. This makes Oracle anopen system, which protects the investment of customer. It is easy to port Oracle.
Portability
Oracle software can be ported to different operating systems and it is the name on all
systems. Application development in Oracle can be ported to any operating system
with little or no modifications.
Enforced Integrity
Oracle allows users to define business rules and enforce them. These rules need not be
included at the application level.
Data Security
Oracle provides security in different levels system level and object level. It also
makes implementation of security easier through Roles.
37
-
8/3/2019 E Bankig Report
38/76
E BANKING SYSTEM
Support for Client / Server environment
Oracle allows process to be split between client and server. Oracle server does all
database management whereas Client does user interface. Oracle server allows code to
be stored in the database in the form of procedures and functions. This allows
centralization of the code and reduces network traffic.
Enterprise Wide Data Sharing
The unrivaled portability and connectivity of the oracle DBMS enables all the systems
in the organization to be linked into a singular, integrated computing resource.
Sophisticated Concurrency Control
Real World applications demand access to critical data. Oracle employs
full,unrestricted row-level locking and contention free queries minimize and in many
cases entirely eliminates contention wait time.
APPLICATION DEVELOPMENT TOOLS
SQL*PLUS
This is the primary interface to the ORACLE RDBMS. It provides a powerful
environment for querying, defining and controlling data. Based on a full
implementation of ANSI standard SQL,it also provides a rich set extensions in
PL/SQL, another data manipulation language.
PROJECTPROJECT DDESIGNESIGN
38
-
8/3/2019 E Bankig Report
39/76
E BANKING SYSTEM
The traditional tools of data gathering have limitations. An English
narrative description is often vague and difficult for the user to grasp. System
flowcharts focus more on physical than on logical implementation of the candidate
system. Because of these drawbacks, structured tools were introduced for analysis.
Structured analysis is a set of techniques and graphical tools (DFD) that allow the
analyst to develop a new kind of system specifications that are easily understandable
to the user.
DDATAATA FFLOWLOW DDIAGRAMIAGRAM
Data Flow Diagram is a diagrammatic representation of datamovement through a system manual or automated - from inputs to outputs through
processing. The data flow diagrams help in the analysis of the flow of data through a
system and thus help in identifying the system requirements. These are of two types
Logical Data Flow Diagrams and Physical Data Flow Diagrams. The Data Flow
Diagram (DFD) clarifies system requirements and identifies major transformations
that will become programs in system design. It is the starting point of system design
that decomposes the requirements specifications down to the lowest level of detail.
LOGICAL DATA FLOW DIAGRAMS:
The Logical Data Flow Diagrams represent the transformation of the data
from input to output through processing logically and independently of the physical
components that may be associated with the system.
PHYSICAL DATA FLOW DIAGRAM:
The Physical Dataflow Diagrams show the actual implementation and
movement of data between people, departments, and workstations. Each component of
a DFD is labeled with a descriptive name. Process names are further numbered that
will be used for identification purposes. The number assigned to a specific process
does not correspond to the sequence of processes. It is strictly for identification
39
-
8/3/2019 E Bankig Report
40/76
E BANKING SYSTEM
purposes. A data flow diagram allows parallel activities i.e. a number of data-flows
coming out from the source and going into the destination. A DFD concentrates on the
data moving through the system and not on the devices or equipments. A DFD may
consist of a number of levels. The top-level diagram is called the Context Diagram,
which consists of a single process and plays a very important role in studying the
system. It gives the most general and broadest view of the system. Moreover, it gives
the pictorial representation of the scope boundaries of the system under study.
NOTATIONS:
Data-Flows show the movement of data in a specific direction from the source
to the destination. It represents a packet of data.
Processes show the operations performed on the data, which transform it from
input to output.
Sources and Destinations of data are the external sources and destinations of
data, which may be people, programs, organizations or other entities interacting
with the system, but are outside its boundary.
Data Stores are places where data are stored such as files and tables.
DATA FLOW DIAGRAM:
40
-
8/3/2019 E Bankig Report
41/76
E BANKING SYSTEM
The top level of DFD is known as context level. It is the first step in requirement
determination, which aims at learning the general characteristics of the business
process and defines the system that will be studied in the sense that it determines the
boundaries. Anything that is not inside the process identified in the context diagram
will not part of the system.
LEVEL 0:
LEVEL 1:
SUCCESSFUL
LOGIN
LOGIN
INVALID
LOGIN
LEVEL 2:
41
LOGIN
0.1
CHECK
FOR
VALIDAT
E
ADMIN OR
STAFF OR USER
UsernamePassword
ADMIN/STAFF/USER REPORT
E
BANKIN
G
SYSTEM
-
8/3/2019 E Bankig Report
42/76
E BANKING SYSTEM
MANAGER BRANCH
MANAGER
BRANCH
NN
42
MANAGER
SEARCH
BRANCH
SEARCH
MANAGER
ADD
BRAN
CH
ADD
START
ADMIN
0.1.1
MANA
GER0.1.2
ACC
.ISS
UE
STAF
F
SEAR
CH
STAFF
APPOI
NTME
NT
ACCOUNT
SEARCH
CHEC
K
FOR
VALI
D
USE
STAFF
0.1.3
DEPO
SITE/
WITH
DRA
WL
BAL
ANC
E
CHE
CK
ACCOU
NT
SEARC
H
REPORT
USER
0.2.1ACC
REGD.
-
8/3/2019 E Bankig Report
43/76
-
8/3/2019 E Bankig Report
44/76
E BANKING SYSTEM
SCREEN LAYOUTSCREEN LAYOUT
LOGIN PAGELOGIN PAGE
44
-
8/3/2019 E Bankig Report
45/76
E BANKING SYSTEM
45
-
8/3/2019 E Bankig Report
46/76
E BANKING SYSTEM
46
-
8/3/2019 E Bankig Report
47/76
E BANKING SYSTEM
47
-
8/3/2019 E Bankig Report
48/76
E BANKING SYSTEM
48
-
8/3/2019 E Bankig Report
49/76
E BANKING SYSTEM
49
-
8/3/2019 E Bankig Report
50/76
E BANKING SYSTEM
50
-
8/3/2019 E Bankig Report
51/76
E BANKING SYSTEM
51
-
8/3/2019 E Bankig Report
52/76
E BANKING SYSTEM
. PROJECT LIFE CYCLE
52
-
8/3/2019 E Bankig Report
53/76
E BANKING SYSTEM
The E-BANKING SYSTEM applied the Iterative waterfall Life Cycle Model
The life cycle paradigm encompasses the following activities.
1. Feasibility Study
2. Software Requirement Analysis & Specification
3. Design
4. Coding
5. Testing
6. Maintenance
Figure 1: Iterative Waterfall Model of Software Life Cycle
53
Feasibility Study
Requirement analysis
& Specification
Coding & Unit
Testing
System Design
Integration & System
Testing
Maintenance
-
8/3/2019 E Bankig Report
54/76
E BANKING SYSTEM
SYSTEM TESTINGSYSTEM TESTINGSystem testing is the process in which the system undergoes experimental testing so as
to check that the system does not fail i.e. to check whether the required system is running
according to specification and user expectation. System testing also tests to find discrepancies
between the system and its original objective, current specification and systems
documentation. Hence most useful and practical approach is with the understanding that
testing is the process of executing a program with the explicit intention of finding errors that
is making the program fail.
Testing performs a very critical role for quality assurance and
ensuring the reliability of the software. During testing, the program to be tested is executed
with a set of test cases and output of the program for the test cases and output of the program
for the test case is evaluated to determine if the program is performing as it is expected to.
Hence
Testing is the process of executing a program with the intention of finding errors.
A good test case is the one that has a high probability of finding as yet
undiscovered error.
A successful test is one yet uncovers as yet undiscovered errors.
Testing is performed according to two different strategies:
1. Code testing
2. Specification testing
CODE TESTINGCODE TESTING
The code testing strategy examines the logic of program i.e. the
analyst develops test cases that results in executing every instruction in the program.
Basically during code testing every path through the program is tested.
SPECIFICATION TESTINGSPECIFICATION TESTINGTo perform specification testing, analyst examines the specification
stating what the program should do and how it should perform under various conditions.
Then test cases are developed for each. In order to find which strategies to follow, levels of
testing should be followed.
LEVELS OF TESTING
54
-
8/3/2019 E Bankig Report
55/76
E BANKING SYSTEM
The basic levels are unit testing, integration testing, system testing and
acceptance testing. These different levels of testing attempt to detect different types of faults.
The different levels of testing are as follows:
Unit testing:
In this testing different modules are tested against specification
produced during design of the modules. Unit testing is essential for verification of code
produced during the coding phase and hence its main goal is to test internal logic modules.
Integration testing:
In this testing tested modules are combined into subsystems which are
then tested. The goal here is to see if the modules can be indicated properly and emphasis is
being on testing interfaces between modules.
System testing:
In this testing the entire software system is tested. The reference
document for this process is the requirements document and the goal is to see if the system
meets its requirements.
This is normally performing on realistic data of the client to demonstrate for the software is
working satisfactorily. Testing here focus on external behavior of the system.
Black box testing:
In Black box testing, test cases are designed from an examination of
the I/O values only and no knowledge of design or code is required. In this strategy some test
cases are generated as input conditions that fully execute all functional requirements for the
program. This testing has been used to find errors in the following categories:
Incorrect or missing functions
55
-
8/3/2019 E Bankig Report
56/76
E BANKING SYSTEM
Interface errors
Errors in data structure or external database access
Performance errors
Initialization and termination errors
White box testing:
One white box testing is said to be stronger than another strategy, if
all types of errors detected by the first strategy are also detected by the second testing and the
second strategy additionally detects some more types of errors. When two testing strategies
detect errors that are different at atleast with respect to some types of errors, they are called
complementary.
56
-
8/3/2019 E Bankig Report
57/76
E BANKING SYSTEM
MAINTENANCEMAINTENANCE
Maintenance is necessary to eliminate errors in the working system during
its working life and to tune the system to many variations in its working environment. Often
small system deficiencies are found as a system is brought into operation and changes are
made to remove them. System planners must always plan for resource availability to carry
out these maintenance functions. The importance of maintenance is to continue to bring the
new system to standards.
The maintenance can be classified into three types such as:
Maintenance to repair software faults; coding errors are usually relatively
cheaper to correct, design errors are more expensive as they may involve the rewriting of
several components. Requirement errors are the most expensive to repair because of the
extensive system design which may be necessary.
Maintenance to adopt the software to different operating environment; this
type of maintenance is required when some aspects of system environments such as
hardware, the platform operating system or the other support software changes. The
application system must be modified to adopt it to cooperate with these environmental
changes.
Maintenance to add or modify the system functionality; this type
maintenance is necessary when the system requirements change in response to organizational
change or business change. The scale of changes required to software is often much greater
than that for the other type of maintenance.
57
-
8/3/2019 E Bankig Report
58/76
E BANKING SYSTEM
FUTURE SCOPE OF THIS PROJECT
The project has made the standards required to work on WEB based E BANKING
SYSTEM. If the business policies remain same the project can be portrayed to many
BANKS with minor changes in the working procedure of the project. The project can be
used as an availability to develop the project for a different banks with different businesslogics, where in the commonalities in certain areas remain very same at any business level.
By using the common features in the future developments, the development time as well as
the cost of development can be desiredeconsiderable
58
-
8/3/2019 E Bankig Report
59/76
E BANKING SYSTEM
Code:Code:using System;using System.Web;using System.Web.Security;using System.Web.UI;
using System.Web.UI.HtmlControls;using System.Web.UI.WebControls;using System.Web.UI.WebControls.WebParts;using System.Xml.Linq;using System.Data;using System.Data.OleDb;
////// Summary description for Mybank///publicclassMybank{ publicOleDbConnection cc = newOleDbConnection("provider=msdaora;datasource=orcl;user id=ebank;password=jitu;unicode=true"); publicOleDbCommand cmd; publicOleDbDataAdapter adp;
public Mybank(){}
publicvoid textclear(TextBox[] txt){
for (int i = 0; i < txt.Length; i++){
txt[i].Text = "";}
} publicstring LoginCheck(string emailid, string paswword)
{ string sql = "select * from admin_login where admin_emailid='" +emailid + "' and password='" + paswword + "'";
adp = newOleDbDataAdapter(sql, cc); DataTable dt = newDataTable();
adp.Fill(dt); if (dt.Rows.Count != 0)
{ return"admin";
} else
{ string sql1 = "select * from bank_login whereBANK_USER_EMAILID='" + emailid + "' and BANK_USER_PASSWORD='" + paswword +"'";
adp = newOleDbDataAdapter(sql1, cc); DataTable dtt = newDataTable();
adp.Fill(dtt); if (dtt.Rows.Count != 0)
{ return dtt.Rows[0][2].ToString();
} else
{ string sql2 = "select * from cust_login where
CUST_EMAILID='" + emailid + "' and password='" + paswword + "'";adp = newOleDbDataAdapter(sql2, cc);
59
-
8/3/2019 E Bankig Report
60/76
E BANKING SYSTEM
DataTable dttt = newDataTable();adp.Fill(dttt);
if (dttt.Rows.Count != 0){
return"customer";}
else{ return"**";
}}
}
} publicvoid date_load(DropDownList ddl)
{ddl.Items.Add("DD");
for (int i = 1; i
-
8/3/2019 E Bankig Report
61/76
E BANKING SYSTEM
{ string sql = "insert into admin_login values('" + emailid + "','" +password + "')";
cmd = newOleDbCommand(sql, cc);cc.Open();cmd.ExecuteNonQuery();
cc.Close();} publicbool New_branch(string branch_id, string branch_name, stringaddress, int phno, int fax, string emailid)
{ string ss = "select * from branch where branch_id='" + branch_id +"'";
adp = newOleDbDataAdapter(ss, cc); DataTable dt = newDataTable();
adp.Fill(dt); if (dt.Rows.Count == 0)
{ string sql = "insert into branch values('" + branch_id + "','"
+ branch_name + "','" + address + "'," + phno + "," + fax + ",'" + emailid+ "')";cmd = newOleDbCommand(sql, cc);cc.Open();cmd.ExecuteNonQuery();cc.Close();
returntrue;}
else{
returnfalse;}
}
publicvoid Branchid_load(DropDownList ddl){ string sql = "select BRANCH_ID from branch";
adp = newOleDbDataAdapter(sql, cc); DataTable dt = newDataTable();
adp.Fill(dt);ddl.Items.Add("");
for (int i = 0; i < dt.Rows.Count; i++){
ddl.Items.Add(dt.Rows[i][0].ToString());}
} publicvoid Branch_info_load(string branchid, TextBox branchname,TextBox address, TextBox phno, TextBox fax, TextBox email)
{ string sql = "select * from branch where branch_id='" + branchid +"'";
adp = newOleDbDataAdapter(sql, cc); DataTable dt = newDataTable();
adp.Fill(dt);branchname.Text = dt.Rows[0][1].ToString();address.Text = dt.Rows[0][2].ToString();phno.Text = dt.Rows[0][3].ToString();fax.Text = dt.Rows[0][4].ToString();email.Text = dt.Rows[0][5].ToString();
} publicvoid branch_update(string branchid, string branch_name, stringaddress1, int phno1, int fax1, string emailid)
61
-
8/3/2019 E Bankig Report
62/76
E BANKING SYSTEM
{ string sql = "update branch set branch_name='" + branch_name +"',address='" + address1 + "',phno=" + phno1 + ",fax=" + fax1 +",email_id='" + emailid + "' where branch_id='" + branchid + "'";
adp = newOleDbDataAdapter(sql, cc); DataTable dt = newDataTable();
adp.Fill(dt);} publicvoid branch_delete(string branch_id)
{ string sql = "delete from branch where branch_id='" + branch_id +"'";
cmd = newOleDbCommand(sql, cc);cc.Open();cmd.ExecuteNonQuery();cc.Close();
} publicvoid new_account_request(int slno, string NAME, stringFATHER_NAME, string PRESENT_ADDRESS, string PERMANENT_ADDRESS, string
GENDER, string DOB, string QUALIFICATION, string EMAILID, long PHNO, doubleBASIC_DEPOSITE, long FROM_ACCOUNT, string DATE_OF_REGD,string account_type){
string sql1 = "insert into account_request values(" + slno + ",'" +NAME + "','" + FATHER_NAME + "','" + PRESENT_ADDRESS + "','" +PERMANENT_ADDRESS + "','" + GENDER + "','" + DOB + "','" + QUALIFICATION +"','" + EMAILID + "'," + PHNO + "," + BASIC_DEPOSITE + "," + FROM_ACCOUNT +",'" + DATE_OF_REGD + "','" + account_type + "')";
cmd = newOleDbCommand(sql1, cc);cc.Open();cmd.ExecuteNonQuery();cc.Close();
} publicvoid branchload(DropDownList dl){
string sql = "select branch_id from branch"; DataTable dt = newDataTable(); OleDbDataAdapter adp = newOleDbDataAdapter(sql, cc);
adp.Fill(dt);dl.Items.Add("---select---");
for (int x = 0; x < dt.Rows.Count; x++){
dl.Items.Add(dt.Rows[x][0].ToString());}
} publicvoid branchshow(string bnid, TextBox txt)
{ string sql = "select branch_id, BRANCH_NAME from branch wherebranch_id='" + bnid + "'"; DataTable dt = newDataTable(); OleDbDataAdapter adp = newOleDbDataAdapter(sql, cc);
adp.Fill(dt);txt.Text = dt.Rows[0][1].ToString();
} publicvoid InsertManager(string BRANCH_ID, string MDATE, stringMANAGER_ID, string MNAME, string MQUAL, string JOB_EX, int AGE, stringGENDER, string DOB, string PER_ADDRESS, string PRES_ADDRESS, string PROOF,string PASSWORD, int PHNO, int FAXNO, string EMAIL)
62
-
8/3/2019 E Bankig Report
63/76
E BANKING SYSTEM
{ string sql = "insert into manager(BRANCH_ID, MDATE, MANAGER_ID,MNAME, MQUAL, JOB_EX, AGE, GENDER, DOB, PER_ADDRESS, PRES_ADDRESS, PROOF,PASSWORD, PHNO, FAXNO, EMAIL) values('" + BRANCH_ID + "','" + MDATE + "','"+ MANAGER_ID + "','" + MNAME + "','" + MQUAL + "','" + JOB_EX + "'," + AGE+ ",'" + GENDER + "','" + DOB + "','" + PER_ADDRESS + "','" + PRES_ADDRESS
+ "','" + PROOF + "','" + PASSWORD + "'," + PHNO + "," + FAXNO + ",'" +EMAIL + "')";cmd = newOleDbCommand(sql, cc);cc.Open();cmd.ExecuteNonQuery();cc.Close();
} publicvoid Managercmdload(DropDownList dl)
{ string sql = "select manager_id from manager"; OleDbDataAdapter adp = newOleDbDataAdapter(sql, cc); DataTable dt = newDataTable();
adp.Fill(dt);
dl.Items.Add("---select---"); for (int x = 0; x < dt.Rows.Count; x++){
dl.Items.Add(dt.Rows[x][0].ToString());}
} publicvoid ManagerSelect(string search, DropDownList BRANCH_ID,TextBox MDATE, TextBox MANAGER_ID, TextBox MNAME, DropDownList MQUAL,TextBox JOB_EX, TextBox AGE, RadioButtonList rd, DropDownList dd,DropDownList mm, DropDownList yy, TextBox PER_ADDRESS, TextBoxPRES_ADDRESS, CheckBoxList chk, TextBox PASSWORD, TextBox PHNO, TextBoxFAXNO, TextBox EMAIL)
{
string sql = "select * from manager where MANAGER_ID='" + search +"'"; OleDbDataAdapter adp = newOleDbDataAdapter(sql,cc); DataTable dt = newDataTable();
adp.Fill(dt);BRANCH_ID.Text =dt.Rows[0][0].ToString();
DateTime ssp = Convert.ToDateTime(dt.Rows[0][1].ToString()); string ss1 = ssp.ToString("dd-MMM-yy");
MDATE.Text = ss1.ToString();MANAGER_ID.Text = dt.Rows[0][2].ToString();MNAME.Text = dt.Rows[0][3].ToString();MQUAL.Text = dt.Rows[0][4].ToString();JOB_EX.Text = dt.Rows[0][5].ToString();AGE.Text = dt.Rows[0][6].ToString();rd.Text = dt.Rows[0][7].ToString();
DateTime dd1 = Convert.ToDateTime(dt.Rows[0][8].ToString()); string ddd1 = dd1.ToString("dd-MMM-yyyy"); string[] ddd = ddd1.Split('-');
dd.Text = ddd[0].ToString();mm.Text = ddd[1].ToString();yy.Text = ddd[2].ToString();PER_ADDRESS.Text = dt.Rows[0][9].ToString();PRES_ADDRESS.Text = dt.Rows[0][10].ToString();chk.Text = dt.Rows[0][11].ToString();PASSWORD.Text =dt.Rows[0][12].ToString();PHNO.Text = dt.Rows[0][13].ToString();FAXNO.Text = dt.Rows[0][14].ToString();EMAIL.Text = dt.Rows[0][15].ToString();
}
63
-
8/3/2019 E Bankig Report
64/76
E BANKING SYSTEM
publicvoid clear1(TextBox[] txt1){
for (int x = 0; x < txt1.Length; x++){
txt1[x].Text = "";}
} publicvoid ManagerUpdate(string search, string BRANCH_ID, stringMDATE, string MANAGER_ID, string MNAME, string MQUAL, string JOB_EX, doubleAGE, string GENDER, string DOB, string PER_ADDRESS, string PRES_ADDRESS,string PROOF, string PASSWORD, double PHNO, double FAXNO, string EMAIL)
{ string sql = "update manager set BRANCH_ID='" + BRANCH_ID +"',MDATE='" + MDATE + "',MANAGER_ID='" + MANAGER_ID + "',MNAME='" + MNAME +"',MQUAL='" + MQUAL + "',JOB_EX='" + JOB_EX + "',AGE=" + AGE + ",GENDER='"+ GENDER + "',DOB='" + DOB + "',PER_ADDRESS='" + PER_ADDRESS +"',PRES_ADDRESS='" + PRES_ADDRESS + "',PROOF='" + PROOF + "',PASSWORD='" +PASSWORD + "',PHNO=" + PHNO + ",FAXNO=" + FAXNO + ",EMAIL='" + EMAIL + "'where MANAGER_ID='" + search + "'";
OleDbCommand cmd = newOleDbCommand(sql, cc);cc.Open();cmd.ExecuteNonQuery();cc.Close();
} publicvoid managernameex(string magerid, TextBox txt)
{ string sql = "select MNAME from manager where manager_id='" +magerid + "'"; OleDbDataAdapter adp = newOleDbDataAdapter(sql, cc); DataTable dt = newDataTable();
adp.Fill(dt);txt.Text = dt.Rows[0][0].ToString();
} publicvoid staffInsert(string BRANCH_ID, string MDATE, stringMANAGER_ID, string STAFF_ID, string STAFF_NAME, string MQUAL, stringJOB_EX, int AGE, string GENDER, string DOB, string PER_ADDRESS, stringPRES_ADDRESS, string PROOF, string PASSWORD, int PHNO, int FAXNO, stringEMAIL)
{ OleDbCommand cmd = newOleDbCommand("Estaff", cc);
cmd.Parameters.AddWithValue("BRANCH_ID", BRANCH_ID );cmd.Parameters.AddWithValue("MDATE",MDATE);cmd.Parameters.AddWithValue("MANAGER_ID",MANAGER_ID);cmd.Parameters.AddWithValue("STAFF_ID",STAFF_ID);cmd.Parameters.AddWithValue("STAFF_NAME",STAFF_NAME);cmd.Parameters.AddWithValue("MQUAL",MQUAL);
cmd.Parameters.AddWithValue("JOB_EX",JOB_EX);cmd.Parameters.AddWithValue("AGE",AGE);cmd.Parameters.AddWithValue("GENDER",GENDER);cmd.Parameters.AddWithValue("DOB",DOB);cmd.Parameters.AddWithValue("PER_ADDRESS",PER_ADDRESS);cmd.Parameters.AddWithValue("PRES_ADDRESS",PRES_ADDRESS);cmd.Parameters.AddWithValue("PROOF",PROOF);cmd.Parameters.AddWithValue("PASSWORD",PASSWORD);cmd.Parameters.AddWithValue("PHNO",PHNO);cmd.Parameters.AddWithValue("FAXNO",FAXNO);cmd.Parameters.AddWithValue("EMAIL", EMAIL);cmd.CommandType = CommandType.StoredProcedure;cc.Open();cmd.ExecuteNonQuery();cc.Close();
64
-
8/3/2019 E Bankig Report
65/76
E BANKING SYSTEM
} publicvoid Autogen(TextBox txt)
{ string sql = "select estaff1.nextval from dual"; string sl = "S00";
adp = newOleDbDataAdapter(sql, cc);
DataTable dt = newDataTable();adp.Fill(dt);txt.Text = sl+dt.Rows[0][0].ToString();
}
publicvoid staffload(DropDownList dl1){
string sql = "select STAFF_ID from staff"; OleDbDataAdapter adp = newOleDbDataAdapter(sql, cc); DataTable dt = newDataTable();
adp.Fill(dt);dl1.Items.Add("---select---");
for (int x = 0; x < dt.Rows.Count; x++)
{ dl1.Items.Add(dt.Rows[x][0].ToString());}
} publicvoid AC_ISSUE(TextBox txt)
{ string sql = "select estaff1.nextval from dual"; string sl = "301010";
adp = newOleDbDataAdapter(sql, cc); DataTable dt = newDataTable();
adp.Fill(dt);txt.Text = sl + dt.Rows[0][0].ToString();
}
publicvoid ACcmdload(DropDownList dl){ string sql="select slno from issue_ac";
dl.Items.Add("---select---");adp=newOleDbDataAdapter(sql,cc);
DataTable dt=newDataTable();adp.Fill(dt);
for (int x = 0; x < dt.Rows.Count; x++){
dl.Items.Add(dt.Rows[x][0].ToString());}
}
publicvoid CustomerSelect(string SLNO, TextBox NAME1, TextBox name2,TextBox FATHER_NAME, TextBox PRESENT_ADDRESS, TextBox PERMANENT_ADDRESS,RadioButtonList GENDER, DropDownList DOB1, DropDownList dob2,DropDownList dob3, DropDownList QUALIFICATION, TextBox EMAILID, TextBoxPHNO, TextBox BASIC_DEPOSITE, TextBox FROM_ACCOUNT, TextBox D