8/8/2019 Banking 87

1/17

ONLINE BANKING SYSTEM

OBJECTIVE:

To use the case tools for analyzing the requirements and to design a project model for Online Banking

System which is used to maintain customer details and deal with the transactions. These requirements are

provided by the customer and are validated by project members.The documentation will provide a basis for the

system design.

PROBLEM STATEMENT:

The objective of this project is to provide an efficient system for withdraw of money. The system is host

centered program supporting two types of users, bank customers and administrators. The system not only

provides the end user with a user-friendly interface but it also provides the system administrator easy access to

perform system administration functions.

A customer will login to the system by providing the user name and password.The customer enters his

personal details and he is provided with a username and password. The Administrator will have the control over

the validation and all the transactions done by a customer. The administrator will maintain the account details of

all the customers.The system allows the customer to withdraw and deposit the amount from his account.The

system allows withdrawal of amount only when the customer has a sufficient balance.

FUNCTIONAL REQUIREMENTS:

Login:

y Username should accept only characters, if any special characters or number is provided, login window

should remain.

y Password should contain a minimum of 8 characters, first character should be an alphabet.

Customer Details:

y Customer Details should have the fields name, age, gender, address, state, pincode, phone number.

y Age, pincode, phone number fields should have only numbers and no alphabets or special charectors.

User account management:

y Customer accounts can be managed by the system administrator.

y For creating a new user account the screen will display a form with all appropriate attributes likeuserID,name,address,phone.e-mail and account status.

y A unique ccount will be generated whenever the administrator fills in the information and submits it tocreate a new account.

y The account is created when the required information is entered and submitted.

8/8/2019 Banking 87

2/17

Update account:

y For updating an account we will get a different form depending on which field we want to update.

y The account is updated based on the user requirements.

y When the user requests for the account to be updated, the account is updated.

Delete account:

y For deleting an account we will get a different form with the user account number, name, address, SSNinformation and will be asked to double check before the account is permanently removed from the

system.

y The account is deleted after getting confirmation from the user.

Enable/Disable account:

y In addition we can also disable or enable an account temporarily.

y Based on the request from the user, the administrator the account is enabled or disabled.

y The account is enabled or disabled if the user is requesting so.

UML MODELING:

DESCRIPTION FOR USECASE DIAGRAM:

The Use-Case Diagram illustrates the functionality of online banking System. It has two actors.

The first one is the customer he can access the functionalities for providing details, withdrawing and depositing amount.

The second actor is the administrator he can access the use-cases like checking balance, maintaining account detail and

Allowing withdrawal and depositing money.

DESCRIPTION FOR ACTIVITY DIAGRAM:

The activity diagram describes the system by step by step activity. The customer will login to the system by providing his

user name and password, if login details are correct then it is validated by the administrator, then the customer is allowed

for further proceedings like whether he can withdraw amount or deposit amount. Once after withdrawing or depositing he

may allowed to view current balance. If the current balance is below minimum balance, then the administrator can

produce fine amount for maintaining low balance.

DESCRIPTION FOR SEQUENCE DIAGRAM:

Sequence Diagram will describe about the sequence of method calls between the objects. It has five objectsy Customer

y Balance

y Administrator

y Deposit

y Withdraw

First the customer will login to the system then he can withdraw or deposit or he can view current balance for that the

Respective methods will be called, and then the administrator object can view and then validate the customers account.

8/8/2019 Banking 87

3/17

DESCRIPTION FOR COLLABORATION DIAGRAM:

Collaboration diagram is used to depict the flow of events in the system over a timeline.

First the customer will login to the system then he can withdraw or deposit or he can view current balance for that the

Respective methods will be called, and then the administrator object can view and then validate the customers account.

DESCRIPTION FOR CLASS DIAGRAM:

y The System contains five classes: Account History, Account History Context, Account, TransactionList, and Transaction.

y Account class contains the attributes Holder, Number and Type and it has methods for maintaining theseattributes.

y Transaction List class contains the information about the previous transactions.

y Transaction class contains all the details about the current transaction.

y Account History class has access to both AccountHistoryContext and TransactionList class.

8/8/2019 Banking 87

4/17

GENERATED CODE:

//Source file: Z:/SE/Transaction.java

public class Transaction extends TransactionList

{

private string date;

private string description;

private string deposit;

private string withdraw;

private string balance;

public Transaction()

{}

/**

@roseuid 4CA9A85401F5

*/

public void transaction()

{

}

/**

@roseuid 4CA9A92C0129

*/

public void getdate()

{

}

/**

@roseuid 4CA9A93100CC

*/

public void getdescription()

{

8/8/2019 Banking 87

5/17

}

/**

@roseuid 4CA9A93B00FB

*/

public void getdeposit()

{

}

/**

@roseuid 4CA9A942005F

*/

public void opname2(){

}

/**

@roseuid 4CA9A94602A2

*/

public void getwithdraw()

{

}

/**

@roseuid 4CA9A950016A

*/

public void getbalance()

{

}

}

8/8/2019 Banking 87

6/17

//Source file: Z:/SE/AccountHistoryContext.java

public class AccountHistoryContext

{

private String dateFrom;

private String DateTo;

private int account;

public Account theAccount;

/**

@roseuid 4CA9A3A001C7

*/

public AccountHistoryContext()

{

}

/**

@roseuid 4CA9A3AA012C

*/

public date getDateFrom()

{

}

/**

@roseuid 4CA9A3B203AD

*/

public void setDateFrom()

{

}

/**

@roseuid 4CA9A3BE01E9

*/

public date getDateTo()

{

}

/**

8/8/2019 Banking 87

7/17

@roseuid 4CA9A3C4019B

*/

public void setDateTo()

{

}

/**

@roseuid 4CA9A3C903BE

*/

public Account getAccount()

{

}

/**

@roseuid 4CA9A3CE00A1

*/public void setAccount()

{

}

/**

@roseuid 4CA9A3D30063

*/

public void toXML()

{

}

/**

@roseuid 4CA9A3E70007

*/

public void fromXML()

{

}

}

8/8/2019 Banking 87

8/17

//Source file: Z:/SE/AccountHistory.java

public class AccountHistory

{

private object transactionList;

private String context;

public AccountHistoryC

ontext theAccountHistoryC

ontext;public TransactionList theTransactionList;

/**

@roseuid 4CA9A2590208

*/

public AccountHistory()

{

}

/**

@roseuid 4CA9A2640331

*/

public void getTransactionList()

{

}

/**

@roseuid 4CA9A272010E

*/

public void getAccountHistoryContext()

{

}

/**

@roseuid 4CA9A27C0015

*/

public void toXML()

{

}

}

8/8/2019 Banking 87

9/17

//Source file: Z:/SE/Account.java

public class Account

{

private string holder;

private int number;

private string type;

public Account()

{

}

/**

@roseuid 4C

A9A7C

20218*/

public void account()

{

}

/**

@roseuid 4CA9A7C9018C

*/

public void getholder()

{

}

/**

@roseuid 4CA9A7D701AC

*/

public void setholder()

{

}

/**

@roseuid 4CA9A7E00016

*/

8/8/2019 Banking 87

10/17

public void getnumber()

{

}

/**

@roseuid 4CA9A7EA0036

*/

public void setnumber()

{

}

/**

@roseuid 4CA9A7EF022B

*/public void gettype()

{

}

/**

@roseuid 4CA9A7F503E1

*/

public void settype()

{

}

}

8/8/2019 Banking 87

11/17

//Source file: Z:/SE/TransactionList.java

public class TransactionList

{

private ArrayList transactions;

public TransactionList()

{

}

/**

@roseuid 4CA9A9F20220

*/

public void TranasactionList(){

}

/**

@roseuid 4CA9A9FE027E

*/

public void getTransaction()

{

}

/**

@roseuid 4CA9AA090127

*/

public void addTransaction()

{

}

}

8/8/2019 Banking 87

12/17

USE CASE DIAGRAM

enter account number

enter password

deposit or withdraw

amount to be deposited or

with drawn

customer

Maintains account details

check balance and allow withdrawal

c red it or deb it the amount f rom the

account

check balance

bank administrator

8/8/2019 Banking 87

13/17

ACTIVITY DIAGRAM

initial state

Get all customer

details

Get the login

details

allow access toaccount

check login d etail s

are correct

yes

Number of trial s

exceed permitted no.

no

Declare asunauthorised user

if withdrawal

get amount to

be withdrawn

action

cancelled

if amou nt less

than balanceyes

pay the amount and

debit from account

get deposit amount

and credit in account

Display the

current balance

final state

no

yes

8/8/2019 Banking 87

14/17

CLASS DIAGRAM

8/8/2019 Banking 87

15/17

SEQUENCE DIAGRAM

customer administrator withdrawal deposit balance

log in withdraw

deposit

credit the account

debit the account

view balance of a customer

view balance

8/8/2019 Banking 87

16/17

COLLOBORATION DIAGRAM

cust

m

r

it r

l

sit

l ce

admi

istr

at

r

2: l i

7: view

a lance

3: wit

draw

4: deposit

6: view

a lanceofacustomer

5: deb it t

eaccoun t

1: cred it t

eaccount

8/8/2019 Banking 87

17/17

RESULT:

Thus the UML diagrams for banking system are drawn and the skeleton JAVA code has beengenerated.