I am sending ER diagrams, I don’t know weather they are correct or not..Check and tell me.

I need DFD(Data flow diagram),CFD(context flow diagram) diagrams I don’t know how to draw ..I tried
 Reg_dat
Balanc e
Account e Date_of_birth
_number

Login_name Gender

Password Education
Customer

Name email

Addres Name
s
Emp
City Zip_ code
code
State
Company

occupatio
appl Annual n
y income
Company
perf
name
orm
s
loan

Loan
request id
Amount
Loan required
purpos
e

Transaction
Transactio
n id
Funds
Transfer
Amoun
t
Currency
Transfer
Deposit Withdraw
 Reg_dat
Balanc e
Account e Date_of_birth
_number

Login_name Gender

Password Education
Customer

Name email

Addres Name
s
Company

Annual
income

appl
y

perf
orm
s
loan

Loan
request id
Amount
Loan required
purpos
e

Transaction
Transactio
n id
Funds
Transfer
Amoun
t
Currency
Transfer
Deposit Withdraw
 DATA FLOW DIAGRAM

Unregistered view Unregistered

Customer 1 Provide info. Customer

Registered Login Registered

Customer Customer
Banking Activity
 registration 1 Customer
Unregistered Customer Details
Customer Registration D1 Login Details

Registered
Valid Customer
Customer

3 Customer D2 Account Details

2 Customer Deposit Amount

Login
4 Customer D2 Account Details

Withdraw Amount

5 Customer D3 Account Details

Display Balance

6 Customer
D2 Account Details
Display
Transaction Details

7 Customer
D2 Request Details
Funds Transfer

8 Customer D2 Account Details

Currency Trasfer

9 Customer

Apply loan D3 request Details

Functional Requirements
This section provides a high level overview of the online bank customer.

Application Overview

• Open an account
• Deposit Amount
• Withdraw Amount
• Display Balance Amount
• Display transaction details
• Transfer funds
• Currency Transfer
• Apply for a loan

Application scope/High level requirements

The online bank customer has the following functions.

Deliverables

• HTML/JSP screens with validations.

• Design Document.

• Test plan and Test Results.

• Full Functional Applications.

SYSTEM REQUIREMENTS

System Interface

The software is to be developed in J2EE environment, which has in-built cross platform capabilities.

User interface

The user interacts with the system through HTML/JSP pages.

Communication Interface

The communication between front end and the back end of the application is provided by JDBC.

Availability

Since this is a prototype development, there are no strict requirements on availability.

Usability

The online bank customer must be easy-to-use. Development team designed the application in compliance
with Wipro design standards.

Maintainability

The online bank customer is designed for ease of maintenance.

TABLE DESIGN

Register information

S.No Field Name Data Type Length Domain Constraints Description

Register ID of the
Account_
1. Number 10 0-9 Primary Key user(internally
number
generated)
Login Name of the
2. Login_name Text 20 a-z,A-Z,_ Not null
requested person
Password of the
3. Password Text 20 a-z, A-Z Not null
requested person
Full Name of the
4. Name Text 20 a-z, A-z Not Null
requested person
5. Address Text 100 a-z, A-z,0- Not Null Address of the
 9 requested person
City where the
0-9, a-z,
6. City Text 20 Not Null requested person is
A-Z
staying
State where the
0-9, a-z,
7. State/Province Text 20 Not Null requested person is
A-Z
staying
Zip code of the place
0-9, a-z,
8 Zip/Postal code Number 10 Not Null where the requested
A-Z
person is staying
Office Phone Phone number of the
9. Text 12 0-9 Not Null
Number requested person
Phone number of the
10. Work Phone Number 12 0-9 Not Null
requested person
Email id of the
11. Email id Text 40 a-z, A-z Not Null
requested person
Person account
Surety account number who
12. Number 20 0-9 Not null
number introduces him to
bank
Company of the
a-z,A-Z,0-
13 Company name Text 40 Not Null requested person
9
where he is working
Employee code of the
14. Emp code Number 12 0-9 Not Null
requested person
0-9, a-z, Occupation of the
15. Occupation Text 20 Not Null
A-Z requested person
Annual income of the
16. Annual income Number 20 0-9 Not Null
requested person
Gender of the
17. Gender Text 10 a-z, A-z Not Null
requested person
dd- Date of birth of
18. Date-of-Birth Date Not null
mon_yyy requested person
Marital status of the
19. Marital Status Text 20 a-z,A-Z Not Null
requested person
Country where the
20. Nationality Text 20 a-z, A-Z Not Null requested person
leaves
Education
21. Education Text 20 a-z,A-z Not null qualification of the
requested person
 Current date when the
user account is
22. Current Date Date Sysdate Not null
requested (internally
generated)

Transaction Information

S.No Field Name Data Type Length Domain Constraints Description

Transaction id of the
1. Transaction Id Number 10 0-9 Primary Key
account holder
Account Number of
Account 0-9,a-z,A-
2. Text 10 Primary Key the user having an
Number Z
account already
Transaction 0-9,-,A- Date on which
3. Date 12 Not null
Date z,a-z transaction is done
4. Debit Amount Number 5 0-9 Amount Debited
5. Credit Amount Number 5 0-9 Amount Credited

Loan Request Information

S.No Field Name Data Type Length Domain Constraints Description

Request ID for the
1. Request Id Number 10 0-9 Primary Key
request
References
Account Number of
Account Account holder
2. Text 10 0-9,a-z,A-Z the user requested for
Number information(ac
loan
count number)
Purpose for taking the
3. Purpose Text 20 a-z, A-Z Not Null
loan
Status of the
4. Status Number 2 0-1 Not Null
requested

Here also I need name,occupation,Annual income,address …It’s redundancy