BANK GLOBAL ACCESS SYSTEM
ABSTRACT:
The main objective of this system is to let any
customer to set the GAID (Global Access ID) through web or telephone and
provides all other banking services also. This system let the global banks to
set their GPSI (Global Party System Index) and also provides the flexibility
to access the Global customers transactional details using PI (Party
Identifier).The customer can do all the necessary banking operations also
like bill payments, money transfer, deposit of money through out the globe.
• This provides a mechanism for customized customer access to electronic
services through multiple portals.
• The Global Access ID helps a customer to access his/her account
throughout the globe with irrespective to the location.
• The PI is a unique number, which acts as the “key” for component access.
INTRODUCTION:
The modules in this project are
Modules:
1. Transactions.
2. Credit Card Information.
3. Balance Enquiry.
4. Maintaining Customer Details.
5. Check Book Status.
1.Transactions:
We can not only transfer the money from one Account to other
Account but we can also transfer the money from one bank Account
number to another bank Account number using GAID(Global Access
ID)through online.
2.Credit Card Information:
We can view the details of our credit card by providing card
number through online.
3.Balance Enquiry:
We can check our balance amount in our account ,we can see all the
details of our account transactions.
4.Maintaining Customer Details:
Bank can maintain customer details and also providing transactions
information in the form of webpages.
5.Check Book Status:
We can view the check book status i,e the bank will provide a check
book when we open our account, if that book is completed we can apply
for new check book, so we can view the status of the check book
whether they issued it or it is under processing.
Existing System:
In Banks every activity is handled manually such as reports
generation etc.Here
we can transfer the money through online only with in the same bank,
We cannot
transfer the money from one account in one bank to another account in
another
account.If we want to do this the person has to go to the bank and do all
these
things.It is a manual process which is time consuming.Here the client is
focused
with a problem.
Proposed System:
In Proposed System we are concentrating on the problems which the
customer
faced with the existing system.By introducing the Bank Global Access
System
thecustomer can have a quick response for the services like transaction
service,report generation etc.Here we can transfer the money from one
bank to
another bank.To access your account through this system we need a
unique number
which provides security.
ROLES & RESPONSIBILITIES
1) Customer
Role: Account Holder
Responsibilities:
Registration
Login
Transactions
Card Information
Account Details
Check Book Status
Mailing System
Change Password
Logout
2) Official
Role: The person who maintains the accounts
Responsibilities:
Registration
Login
Add Customer
View Customer Details
View Account Details
Update Account Details
Update Check Book Status
Mailing System
Change Password
Logout
3) System Manager
Role: He maintains the database and provides userid and password.
Responsibilities:
Login
Provide Details of GAID
Delete GAID
Add and Delete Employees
Proivide User and pwd
Mailing System
Change Password
Logout
Hierarchical Requirement of Data.
Customer:
REQUIREMENT ELOBORATION FURTHER
ELOBORATION
Registration Details ------
Login User id,pwd ------
Transactions Account No,A/c holder Amount to be
name,bank name etc transferd
Credit card details Card number,type etc Amount to be
drawn
Card Information Card name,Card ------
Type,Bank Name etc
Account Details Account No,Customer ------
Name
Check Book Status Check Book ---------
Name,Custmer Name
Mailing System Sender Id,Recevier ------
Id,Subject
Change password Old pwd,new pwd ------
Official:
REQUIREMENT ELOBORATION FURTHER
ELOBORATION
Registration Details -----
Login User id,Pwd -----
Add Customer Customer Details -----
Customer Name,acct -----
View Customer Details no etc
View Account Details Acct no,balnance etc -----
Update Account Details Accoutn No,Customer ------
Name
Update Check Book Check Book No. -------
Status
Mailing System Sender Id,receiver ------
Id,Subject
Change Password Old pwd,new pwd
System Manager:
REQUIREMENT ELOBORATION FURTHER
ELOBORATION
Login Userid,pwd ------
Provide Details of GAID GAID Details ------
Delete GAID GAID Number ------
Add and Delete Employee -------
Employees Name,Employee Id
Mailing System Sender Id,Receiver ------
Id,Subject
Change password Old Pwd,new Pwd ------
5W, 1H
Customer
Who: The person who has an account
What: Account Holder
Where:Through Internet
When:When he wants to any transactions
Why: To Deposit or Withdraw
How: Through our application
Official:
Who:The person who maintains the accounts
What:Cashier
Where: Through Internet
When: When he wants to do any modifications
Why:.To maintain accounts
How: Through our Application
System Manager:
Who: The person who maintains the database and customer and bank details
What: Maintaing the database
Where: Through Internet
When: If he wants any changes in the database
Why: To maintain the system
How: Through our application.
Context Diagram:
The context diagram is a data flow diagram showing data flows between a
generalized application within the domain and the other entities & abstractions with
which it communicates. One thing that differentiates the use of data flow diagrams
in domain analysis from other typical users is that the variability of the data flows
across the domain boundary must be accounted for with either a set of diagrams or
text describing the differences.
Customer Official
GBAS
System Manager
Customer:
1.Registering And Login using userid,pwd
2.View Card Information
3.View Account Details
4.View Check Book Status
4.Change his password
Official:
1.Registering And Login using userid,pwd
2.Add Customers And View
3.View Account Details and Update
4.Update Check Book Status
5.Change his password
System Manager:
1.Login using userid and pwd
2.Provide Details of GAID and delete
3.Add and delete employees
4.Provide Userid and Password
5.Change password and logout
DATA FLOW DIAGRAMS:
Data flow diagrams (DFDs) were introduced and popularized for structured
analysis and design. DFDs show the flow of data from external entities into the
system, following figures shows how the data moved from one process to another, as
well as its logical storage.
The symbols are:
Squares representing external entities, which are sources or
destinations of data.
Process
Arrows representing the data flows, which can either be
electronic data or physical items
Open-ended rectangles representing data stores,
such as databases It is the permanent database.
Temporary database.
Weak entity
Customer: D1 login D2
Reg
P2
Customer
Custmr Reg login
P3
Home Cstmr
page
card D3
P4
card Customer
dtls
Acct D4
P5
Custmr
custmr
Cstmrn D
System Manager o dtl recve
5
sent D5
P6 P7
Sent Recmai Custmr
mmail l
subjct subjct
logou
t D6
P8
custmr
detals
D1 login D2
Reg
P2
Official:
Official
Offcial Reg login
P3
Home Offcial
page
cstmr D3
P4
View Official
dtls
Acct D4
P5
VewAcc Official
tt
dtls D
chk
5
chk D5
P6 P7
Official
Updt ch Viw ch
Chk
Chk no no
logou
D6
t
P8
custmr
detals
Sys mngr
:
System Manager:
login D1
P2
login
P3
Sys
Home mngr
page
Sys mngr
Sys mngr
GAID D2
P4
dtls Sys mngr
dtls
GAID D4
P5
Sys mngr
delet
Gaid D
no emp
emp 5
D5
ly
P6 P7
Addemp deltemp
detls detls
logou
t D6
P8
detals
r
Entity Diagram:
An entity relationship model(ER-Model) is a detailed
logical representation of data for an organization or for a business area the
ER-Model expresses in terms of entitles and attributes of both the entities
and their relationships.
An ER-Model is normally expresses as an entity-relationship
diagram which a graphical representation of an ER-Model.
The basis constructs of entity relationship and attributes.
There are different symbols in ER-diagram.
ENTITY:
An entity is a person, place, object event or concept in the user environment
about which the organization which to maintain data.
RELATIONSHIP:
A relationship is an association among the instance of one or more
entity types.
ATTRIBUTE:
Each entity type has a set of attributes associated with it. An attribute is
a property or charactertic of an entity.
COMPOSITE ATTRIBUTE
DATAFLOW:
MANY TO ONE:
ONE TO MANY:
MANY TO MANY:
MANDETARY:
OPTIONAL:
DUPLICATE ENTITY:
--
empn
ame
PID Name
Empi desgnt
d n
Uid Gaid
Acctno
Pwd
A
cc
CUSTOMER ou OFFICIAL
T
nt
Doorno
Pwd
Uid
Address man
agm
nt
Stertnam
Stret name
City
SYSTEM
MANAGER
Uid Address
Pwd
City Doorno Stretnam
DATA DICTIONARY:
A data dictionary is a collection of descriptions of the data objects or items in a data
model for the benefit of the programmer and others who need to refer to them. A first
step in analyzing a system of objects with which users interact is to identify each object
and its relationship to other objects.
This process is called data modeling results in a picture of object relationships. After each
data object or item in is given a descriptive name, its relationship is described the type of
data is described, possible predefined values are listed and a brief textual description is
provided. This collection can be organized for reference in to a book called data
dictionary.
When developing programs that use the data model, a data dictionary can be consulted to
understand where a data item fits in the structure, what values it may contain and
basically what the data item means in real world terms.
A data dictionary is a set of Meta data that contain definitions and representations of data
elements with in the context of a DBMS a data dictionary is a database in its own
dictionary.
Attribute Alias Name Data Type Size Repeatable
Name Or Not
PI No Party Identifier Varchar2 20 No
Acct No Account Varchar2 20 No
Number
Custmr Name Coustmer Varchar2 20 Yes
Old Cheq Book Old Cheque Varchar2 20 No
No. Book Number
New Chq Book New Cheque Varchar2 20 No
No. Book Number
Status Status Varchar2 15 Yes
Uid User Id Varchar2 20 No
Pwd Password Varchar2 15 No
Bank Name Bank Name Varchar2 20 Yes
Opn Balnce Open Balance Number 15 Yes
Cname Customer Varchar2 15 Yes
Name
Crd Type Card Type Varchar2 10 Yes
Crd No Card Number Varchar2 15 No
Doi Date Of Issue Date Yes
Doe Date Of Expiry Date Yes
Crd Amount Card Amount Number 10 Yes
Bname Bank Name Varchar2 10 Yes
Addr Address Varchar2 20 No
Gaid Global Access Varchar2 10 Yes
Id
Type Of User Type Of User Varchar2 15 Yes
Fname First Name Varchar2 20 No
Lname Last Name Varchar2 20 No
Gender Gender Varchar2 10 Yes
Dob Dtae Of Birth Date Yes
Ph No. Phone Number Number 15 No
Mob No. Mobile Number Number 15 No
Desg Designation Varchar2 15 Yes
Emplyid Employee Id Varchar2 10 No
To Id To Whom We Varchar2 25 No
Send
Sub Subject Varchar2 20 Yes
Mess Message Varchar2 50 Yes
Doj Date Of Joining Date Yes
SCREEN DESIGNING
HOME PAGE
LOGIN PAGE
CUSTOMER HOME PAGE
CARD DETAILS
ACCOUNT DETAILS
CHEECK BOOK STATUS
COMPOSE
SEND ITEAMS
CHANG PASSWORD
LOGOUT
OFFICIAL HOME
CUSTOMER INFORMATION
ACCOUNT HOLDER DETAILS
ISSUE OF CARD
UPDATE ACCOUNT
UPDATE ACCOUNT
UPDATING STATUS:
AFTER UPDATING ACCOUNT STATUS
UPDATING CHEECK BOOK STATUS
STATUS OF CHEECK BOOK
ALL USERS CHECK BOOK STATUS
SYSTEM ADMINISTRATOR HOME PAGE
ADDING EMPLOYEES
