Vous êtes sur la page 1sur 40

E-Banking

CONTENTS
1. ABSTRACT 2. INTRODUCTION 3. DESIGN PRINCIPLES & EXPLANATION 3.1. MODULES 3.2. MODULE DESCRIPTIOIN 4. PROJECT DICTIONARY 4.1. DATAFLOW DIAGRAMS 4.2. E-R DIAGRAMS 4.3. DATA DICTIONARY 5. FORMS & REPORTS 5.1. I/O SAMPLES 6. BIBILIOGRAPHY

ABSTRACT In the bank all the activities are being done manually .As the bank widens its services & it finds difficult to manage its operations manually and hence this leads to the automation of some of its operations. Banking Information system is a windows based applications. This project mainly deals with managing there types of account such as Saving Account, Current Account and Recurring Deposits . In this project bank is seeking to manage these account through computer based system. Tasks involved in this project are opening the user accounts , recording the account holders transactions , modify, the user records and generating the reports .

2. INTRODUCTION APCOB, which was started as a co-opreative bank with just two branches has grown into a large organization with 25 branches in short span. The rapid growth of the bank has strained the manual accounting processes making it difficult to manage and transfer data. The management has decided to automate the banking activity in a phased manner . One part is to automate the activity with respect to savings account and Current account. The specifications are as follows: FOR ADDITION Account type MUST be accepted from the user . Validation: it should be either SAVING OR CURRENT. Account No. should be generated automatically or given by the ADMIN. Validation: No two accounts should have the same account no. Account holders name must be accepted . Validation: It should neither be special characters nor digits. 4.account holders address should be accepted (no validation). 5.Mobile number should be accepted . Validation: It must be of 10-Digits. 6.occupation should be accepted. Validation: it should be either BUSINESS OR SERVICE. 7.opening date should not be accepted. Validation: should not sysdate. 8. current balance should be accepted. Validation: it should be accepted provided the account type is s,c. 9. Account number, number of months rate of interest, amount of deposited. Maturity date and maturity amount should be entered only if the account want to edit it. Incase of Recurring: Account number should be displayed from the previous block. Number of months should be accepted. Validation: should be only 12, 24 or 36. Rate of interest should be accepted. (No validation). Amount of deposited should be accepted (no validation). Maturity date should be displayed only. Validation: should be calculated as (Sysdate + no .of months). Maturity amount should be displayed only. Validation: should be calculated using the formula Maturity Amount = (P + PNR/100) Where, P- Principal amount or amount deposited N- no. of years and R- rate of interest. FOR MODIFICATION.

account number &account type should be entered/ validation: the account no. should be present in the database. 2.fields account number, account type. Opening date and current balance are only displayed 3.modification of rate of interest, no. of months , maturity date, maturity amount , maturity deposit are not allowed. C: FOR DELETION 1.Accout number should be entered validation :the account number should be present in the data base . before actually closing the account his /her dues have to be settled. if the reccurring deposit account is closed before the maturity date then the interest is calculated till that date . before deleting the account display the matured amount first and ask for confirmation to delete. D.FOR TRANSACTION Transaction date should be system date and it should only be displayed. Transaction type should be entered. Validation: It should be D / W / I. (D-deposit , W-withdrawal, I-interest) Depending on the Trans type the trans remark is displayed. Trans type Trans remark D By deposit W By withdrawal I By interest Transaction type D/W is allowed only for Account type Savings or Current. Transaction type I is allowed only for Account type Savings. Interest will be eredited only in June and December for Saving account. The interest rate is 5.5 % p.a. for the account type Reccurring deposit , the penal interest is calculated. The Reccurring Deposit holder can pay the amount without interest. If he pays before 10th of every calendar month. Failing to pay before 10th he will be charged a penal Interest of 10% of his initial deposit calculated as per day. For persons who have cheque (Y), a minimum amount of Rs. 1000/- should be maintained in his/her account for current account and Rs. 500/- for savings account. at any point of time his/her balance amount should be a minimum of Rs.250/- for savings account and the minimum of Rs.500/- for current. Existed System: In the Bank every Activity is handled manually, such as Opening Account , storing Account holder Details , Transaction Details, Reports Generation. The manual system is taken more time and the services to the Customer are slow and not accurate . The client is focus problem with the existing system with respective two values , such as time value and cost value.

Proposed System In proposed system we are concentrating the problems what ever a client faced with existing manual system. By introducing Automation system for Banking Information system. The client is provides fast services to the customer. The transaction service, report generation service and every service is available at no delay.

3. DESIGN PRINCIPLES & EXPLANATION 3.1. MODULES This project is having three module: Bank Master Module Transaction Module Reports module 3.2. MODULE DESCRIPTION Bank Master Module: This module mainly deals with creation of new Account i.e. Adding new Account Holders. Other activities such as viewing, Modifying , Deleting Account holder Details. Transaction Module: This module deals with different types of transactions such as Deposit, Withdraw and Interest calculation related to customer as well as Bank. Reports Module: This module deals with generation of reports for customer and Bank such as Daily reports, Weakly reports and report for a particular period of time.

4. PROJECT DICTIONARY 4.1. DATAFLOW DIAGRAMS

ADMINISTATOR

MANAGEMENT

eBANKING

BANK OFFICIAL

CUSTOMER

ADMINISTRATOR

LOGIN

USERTABLE

EMPLOYEEMANAGEMENT

CUSTOMERMANAGEMENT

CUSTOMERD USER

LOGOUT

MANAGEMENT

LOGIN

USER-TABLE

DESIGNINGSCHEMES

ACCOUNT-TYPE

LOGOUT

CUSTOMER

LOGIN

CUSTOMER-USER

STOPD CHEQUE

STOPCHEQU E

FUNDTRANSF ER

BILLPAYME NT

CLEARI NGCREDIT

FACILITIES E-DETAILS

TRANSACTION

LOGOUT

BANK OFFICIAL

LOGIN

USER-TABLE

COUNTER

BILL PAYMENT

STOP CHEQUE

CLEARING CREDIT B

OPENING ACCOUNT

BILLPAY MENT

D PAYING BILLS STOP D

STOPCHEQUE

TRANSAC D TION D LOGOUT

REGISTARIN G ACCOUNT

CUSTOMARMASTER

COUNTER

WITHDRAWL

DEPOSIT

TRANSACTION WITHDRAWL-FORM WITHDRAWLCHEQUE

D LOGOUT

TRANSACTION DEPOSIT-CASH DEPOSIT-CHEQUE DEPOSIT-DD

CLEARING CREDIT

CREDIT CLEARING

CREDIT-CARD-MASTER CREDIT-CLEARING

LOGOUT

4.2. E-R DIAGRAMS CUSTOMER

User

Pass wor d

Cust_i d

A/c type

min_bal

max_ba l

Customer

1:n has
m Has

Account

1:nPerfo rms

1:nThroug h

Transaction

a/c no Amount Tr_id Tr_type

MANAGEMENT

User_id

Password

Management
User_i d Usernam e

Password A/c no

1:nDesi gn

Customer

ADMINISTRATOR

User_id

Usernam e Password

Administrator
User_i d

Passwor d

1:n Provides User_id


To

Management

Bank official

User_i d

Password

BANK OFFICIAL

User_i d

Password

Bank Official
Tr_id Tr_type A/c no Amount

m:n Regulate s

Counter transactions

Uname

pwd

Custid
1:n Design Scheme

Uname

pwd 1:1 Register max bal

Management

Customer
min bal

1:1Cre ates uid,pw d

bal Uname pwd a/c id a/c type 1:nPerfo rms

Account

Administration Throug h

1:nCreate s uid,pwd

Bank official

1:n Records

Transaction

Uname

pwd

T-id

a/c no

T-type

4.3. DATA DICTIONARY The logical characteristics of current systems data stores, including name, description, aliases, contents, and organization, identifies processes where the data are used and where immediate access to information required, Serves as the basis for identifying database requirements during system design. Uses of Data Dictionary: To manage the details in large systems. To communicate a common meaning for all system elements. To Document the features of the system. To facilitate analysis of the details in order to evaluate characteristics and determine where system changes should be made. To locate errors and omissions in the system. E-care consists of various tables like super login, eloign, registration, hdlevels, categories, modules, supportteam, hdemp, schedules, hdproblemrequest, superuserprofile, forward, problemhistory, messages etc. 1)Login-Table: FieldName userid Password Description Datatype Varchar2(20) Primary Key Varchar2(20) Varchar2(20)

2)Savings-table: FieldName Accno Acctype Opendate Balance Name Address Phone Occupation Nation Income cheque status dob Datatype Varchar2(20) Primary key Varchar2(20) date number(20) Varchar2(20) Varchar2(20) Varchar2(20) Varchar2(20) Varchar2(20) number(20) Varchar2(20) varchar2(20) Varchar2(20)

gender 3)Current-table: FieldName Accno Acctype Opendate Balance Name Address Phone Occupation Nation Income cheque status dob gender

varchar2(20)

Datatype Varchar2(20) Varchar2(20) date number(20) Varchar2(20) Varchar2(20) Varchar2(20) Varchar2(20) Varchar2(20) number(20) Varchar2(20) varchar2(20) Varchar2(20) varchar2(20)

4)Recurring-table: Fieldname Accno Acctype Opendate Balance Period Mamount Interest Name Adddress Phone Occupation Nation Income Dob Gender Datatype Varchar2(20) Varchar2(20) date number(20) number(20) number(20) number(20) Varchar2(20) Varchar2(20) Varchar2(20) Varchar2(20) Varchar2(20) number(20) Varchar2(20) Varchar2(20)

Mdate Status 5)Reports: Fieldname Trano Accno Name Acctype Tdate Tratype Traamt

date Varchar2(20)

Datatype Varchar2(20) Primary key Varchar2(20) Varchar2(20) Varchar2(20) date Varchar2(20) number(20)

5. FORMS & REPORTS 5.1. I/O SAMPLES

Top of Form

BIBILIOGRAPHY

Charles Petzold, 2002 Programming Windows WP Publishers and Distributors Ltd, Bangalore. . Date. C. J., 1994 An Introduction to Database Systems Addison-Wesley Publishing Company. Herbert Schildt, , 2000 MFC Programming from the Ground Up Tata McGraw-Hill Book & Co., New Delhi. Raghu Ramakrishnan, Johannes Gehrke, , 2000 Database Management Systems, (Second Edition) Mc Graw-Hill International Edition Roger S. Pressman, 1997 Software Engineering, (Fourth Edition) McGraw-Hill International Edition. 6. Silberschatz, Korth, Sudarshan, , 2002. Database Systems Concepts, 4th Edition Mc Graw-Hill International Edition. WEB SITES 7. codeguru.com 8. codeproject.com