OOP based project

[Farrukh Nadeem]

I am learning java and think myself as having knowledge more than basics but below intermediate level. I want to write an application where I could implement my understanding of OOP. Could you people advise me what to write considering that it should be revised/extended later at advance level?

[Campbell Ritchie]

What else are you interested in? If you are interested in music, something musical. If sports, something sporty.

[Farrukh Nadeem]

Interested?.............Nothing. I spend my spare time in front of laptop practicing Java. I work in a bank, therefore, I could only think of something related to my workplace. If you think it is good to write it in OOP. Then here it is my understanding with basic banking.

Project in simple words.
A lot of people have various accounts in a bank i.e. current, saving & loan account, some have multiples. When program starts there is prompt for PIN for authentication. If successful, prompts selection 1-deposit, 2-withdrawal etc. else retries or quit. People make different transactions like paying to other people and even to bank itself (markup). The bank maintains balances of its customers and of itself where it stores aggregate of all deposits (liabilities), loans disbursed (assets), and also its income account (markup).

If you think it is too basic then please add something to start with.

[Campbell Ritchie]

Yes, create an OO banking app.
No, that specification is good for a start; you can enhance it later.
Have you managed to implement the printing of notes through the CD drive?

[Farrukh Nadeem]

 

Campbell Ritchie wrote:
Have you managed to implement the printing of notes through the CD drive?

Sorry, failed to understand..

[Campbell Ritchie]

The wife said that joke would not work.

[Farrukh Nadeem]

Now got it... I wish there would be a program to configure computer to do this. But in this way every programmer would be billionare

[Campbell Ritchie]

 

Farrukh Nadeem wrote: . . . every programmer would be billionare

No, prices would rise into the billions because there is so much money available

[Farrukh Nadeem]

Have been busy on some assignments, could not start the project. Now, struck on this.
Account class created

public class Account {
private String name;
private String city;
private int accNum;
private double balance;
private int pin;
public Account(String name, String city, int accNum, double bal, int pin) {
this.name = name;
this.city = city;
this.accNum = accNum;
this.balance = bal;
this.pin = pin;
}
public String getName() { return name; }
public void setName(String name) { this.name = name; }
public String getCity() { return city; }
public void setCity(String city) { this.city = city; }
public int getAccNum() { return accNum; }
public void setAccNum(int accNum) { this.accNum = accNum; }
public double getBalance() { return balance; }
public void setBalance(double balance) { this.balance = balance; }
public int getPin() { return pin; }
public void setPin(int pin) { this.pin = pin; }
public boolean validPin (int userPin){
if (userPin == pin)
return true;
else
return false;
}
public void credit (double amount) { balance += amount; }
public void debit (double amount) { balance -= amount; }
public String toString (){
return String.format
("Name:\t\t%s\nAddress:\t%s\nAccount No.:\t%d\nPin:\t\t%d\nBalance:\t%.2f",
getName(), getCity(), getAccNum(), getPin(),getBalance());
}
}

Account class extended.

public class CurrentAccount extends Account {
private double charges;
public CurrentAccount(String name, String city, int accNum, double balance, int pin, double charges) {
super(name, city, accNum, balance, pin);
this.charges = charges;
}
}

Database class to hold array of accounts

public class DataBase {
private CurrentAccount [] cAccount;
public DataBase(CurrentAccount[] currentAccounts) {
cAccount = new CurrentAccount [10];
}
}

Now, trying to create account in main method, but dont get a way to this.

public class testing {
public static void main(String[] args) {
DataBase dBase = new DataBase (CurrentAccount[], cAccount);
cAccount[0] = new CurrentAccount ("farrukh","sialkot", 1, 100, 1234, 0.05);
cAccount[1] = new CurrentAccount ("nadeem", "lahore", 2, 250, 4321, 0.05);
}
}

Failed to create array of accounts. Will appreciate if mistakes are pointed out. Thanks in advance

[N Sam]

Your DataBase constructor is called in main as no-argument constructor. But you have only defined a DataBase constructor with 1 argument; so the compiler will supply a default for you.
BTW, where is Account class ? you forgot to add it to the code shown above. There maybe other mistakes, but i didn't look closely.

[Farrukh Nadeem]

Edited in the original code.

[Campbell Ritchie]

 

Farrukh Nadeem wrote:Edited in the original code.

No, don't do that. It makes subsequent replies look like rubbish.

I do not like the design. You have too many fields in the account class, and they can all be changed by set methods.

Never use \n unless you have been told LF is required, least of all in String#format. Use %n there.
Never use if (...) return true; else return false; Look here for the right format.

[Farrukh Nadeem]

My bad
I think I wont be able to write good code in the way I am learning. Have to shift away from this book (dietel's) and look somewhere else.
I shall appreciate your suggestion?

[Farrukh Nadeem]

Changed and little bit simplified
Account Class

package HBL;
public class Account {
private int id;
private int accNum;
private double balance;
private int pin;
public Account(int id, int accNum, double bal, int pin) {
this.id = id;
this.accNum = accNum;
this.balance = bal;
this.pin = pin;
}
public int getId() { return id; }
public int getAccNum() { return accNum; }
public double getBalance() { return balance; }
public int getPin() { return pin; }
public boolean validPin (int userPin) { return (userPin == pin ? true : false); }
public void credit (double amount) { balance += amount; }
public void debit (double amount) { balance -= amount; }
public String toString (){
return String.format
("ID:\t\t%d%nAccount No.:\t%d%nPin:\t\t%d%nBalance:\t%.2f",
getId(), getAccNum(), getPin(), getBalance());
}
}

CurrentAccount class

package HBL;
public class CurrentAccount extends Account {
private double charges;
public CurrentAccount(int id, int accNum, double balance, int pin, double charges) {
super(id, accNum, balance, pin);
this.charges = charges;
}
public double getCharges() { return charges; }
public void setCharges(double charges) {
if (charges > 0.0 && charges < 0.7)
this.charges = charges;
throw new IllegalArgumentException ("charges are out of range");
}
public String toString (){
return String.format ("%s%nAnnual Charges:\t%.2f%n",
super.toString(), getCharges());
}
}

Customer class

package HBL;
public class Customer {
private int id;
private String name;
private String city;
public Customer(int id, String name, String city) {
this.id = id;
this.name = name;
this.city = city;
this.id = id;
}
public int getId () { return id; }
public String getName() { return name; }
public String getCity() { return city; }
public String toString (){
return String.format
("ID:\t\t%d%nName:\t\t%s%nAddress:\t%s%n", getId(), getName(), getCity());
}
}

Database class

package HBL;
public class DataBase {
private CurrentAccount [] cAccount;
private Customer [] customer;
public DataBase (CurrentAccount[] cAccount, Customer[] customer) {
this.cAccount = cAccount;
this.customer = customer;
}
private Customer getId (int id){
for (Customer cus : customer){
if(cus.getId() == id)
return cus;
}
return null;
}
}

Main method

package HBL;
public class testing {
public static void main(String[] args) {
CurrentAccount[] account = new CurrentAccount [4];
Customer [] customer = new Customer [2];
account [0] = new CurrentAccount (1, 123, 3000.0, 7711, 0.5);
account [1] = new CurrentAccount (1, 123, 4000.0, 7711, 0.5);
account [2] = new CurrentAccount (2, 321, 3000.0, 1177, 0.6);
account [3] = new CurrentAccount (2, 321, 4000.0, 1177, 0.6);
customer[0] = new Customer (1, "farrukh", "sialkot");
customer[1] = new Customer (2, "nadeem", "lahore");
DataBase db = new DataBase (account, customer);
db.accountPrint();
}
}

Any suggestion now ??

[Winston Gutkowski]

 

Farrukh Nadeem wrote:Any suggestion now ??

Yes.

1. A 'pin' belongs to a Customer, not an Account.
2. You are really hamstringing yourself by relying on arrays for your "database". Java has a bunch of collections that I think you'll find much more useful.
3. StopCoding (←click). I think you need to step back and understand what you want this "bank" of yours to do before you write one more line of Java code. Right now you're obsessed with nuts and bolts, and you need to see the bigger picture. You might also find the WhatNotHow page worth reading.

HIH

Winston

[Campbell Ritchie]

Also the style could do with improvements. There are several conventions about braces (ond suggestion here), but I know of none which would have a whole method as one line.
Also look at this style guide, where you will find a better way to write the method about PINs.

[Farrukh Nadeem]

 

Also the style could do with improvements. There are several conventions about braces (ond suggestion here), but I know of none which would have a whole method as one line.
Also look at this style guide, where you will find a better way to write the method about PINs.

Did on purpose to feel the code shorter for you, although I follow general practice. I like the reference page, will follow it.

StopCoding.... I think you need to step back and understand what you want this "bank" of yours to do before you write one more line of Java code

Stopped.. My Bigger Picture is to write full fledged working Banking Application. Although it may take years.
Thats why I started it at a very basic level. If you still thinks I am overdoing this. then do tell me. What I understood from WhatNotHow is that I should write down each and every scenario in which my stripped down classes could work along with corner cases in pseudo code or plain English.

Please let me know if I am still going astray.
Thanks for the guidance.

[Campbell Ritchie]

 

Farrukh Nadeem wrote: . . . Did on purpose to feel the code shorter for you, . . .

Don't. You are not printing millions of lines on paper, but showing dozens of lines on screen. Always go for legibility rather than length

Stopped.. . . .

Stay stopped until you have worked out what the application should do, as Winston said.

[Winston Gutkowski]

 

Farrukh Nadeem wrote:What I understood from WhatNotHow is that I should write down each and every scenario in which my stripped down classes could work along with corner cases in pseudo code or plain English.

Actually, you should do it before you have any classes to strip down. And it's not meant to be absolutely exhaustive, but you should have a clear idea of what you want to do before you start to code (because code is all about how).

Winston

[Farrukh Nadeem]

 

you should do it before you have any classes to strip down. And it's not meant to be absolutely exhaustive.

Please elaborate a little bit more, would be grateful for an example. I want to grasp it completely before going to drawing board again.
Thank you.

[Winston Gutkowski]

 

Farrukh Nadeem wrote:Please elaborate a little bit more, would be grateful for an example. I want to grasp it completely before going to drawing board again.

Well, it'll depend on your project but, for example: What does an Account do? Why is it there? What is its purpose?

If I remember my accounting right (and going partly from Wikipedia's description), it might go something like this:

"A bank account is a record of financial transactions between a Customer and a Bank, usually described in terms of the effect on the Bank's liability to the Customer. Depending on the type of account, transactions can take the form of cheques, direct (teller) transactions, standing orders or ATM activity, and the account keeps a running 'balance' (again, indicated in terms of the bank's liability). The general idea of an account is that it acts as secure storage for a Customer's money, so the pattern is usually that the Customer first deposits money and can then withdraw against it; but some accounts may also allow 'overdrafts', or even work as lines of credit, where the Customer pays interest on any outstanding debt. Savings accounts usually pay interest on balances kept above a certain limit, but in general do not allow overdrafts and may also impose restrictions on the number of transactions allowed."

Do you follow? The above describes what an account does, not how it does it - and my apologies to any accounting bods out there who can probably do it much better. Did you also notice that not once was a single Java class mentioned? This sort of stuff should generally be done before you write one line of Java code.

Do you also see why I said that a 'pin' has nothing to do with an Account?

HIH

Winston

[Farrukh Nadeem]

Very much Correct. The example shows what are class properties (fields) and behavior (methods) and what are its loopholes (where we need to place exceptions). Now, it is up to my need what fields, methods I want to use in the class and place plugs where something could go wrongs in worst case scenarios. Correct me if I am going wrong.

[Winston Gutkowski]

 

Farrukh Nadeem wrote:Very much Correct. The example shows what are class properties (fields) and behavior (methods) and what are its loopholes (where we need to place exceptions). Now, it is up to my need what fields, methods I want to use in the class and place plugs where something could go wrongs in worst case scenarios. Correct me if I am going wrong.

No, that sounds about right; but you should be doing the above for your entire Bank scenario before you write ANY code.

I get the feeling that your mind is still leaping ahead to what the code (or the class) is going to look like, and at this stage it's simply not important. Describe what a Bank does, not how you're going to code it in Java.

WhatNotHow (←click).

Winston

[Farrukh Nadeem]

Ok...Below will be the function of a Banking App.

Bank...a secure custodian of money of its Customers Maintaining various Accounts as following:
Current Account -> Where bank charges a penalty if the balance goes below certain level. Keeps checks on balances not to go below zero. No transaction limit.
Saving Account -> Where bank pays interest on balances either on daily basis or month end balances. Keeps checks on balances not to go below zero. Impose transaction limit.
Loan Account -> Where bank earns profit according to the amount withdrawn (overdraft). Balance always negative or zero.
Bank Income Account -> Where all penalties & interest earned are saved.
Bank Expense Account -> Where all expenses (interest paid) are saved.
Bank Asset Account -> Where consolidated figures of Loan Accounts are saved.
Bank Liability Account -> Where consolidated figures of Current & Saving Accounts are saved.

Bank saves all Transaction History, Accounts & Customers Personal information in a DataBase.
Customers operate accounts through Tellers, Cheques, ATM etc after verification. Customers pay amounts either to other people or bank.
At the instruction of Customers, Bank issues instruments (demand draft, pay orders, wire transfers etc.) to other people or other bank.

Above is the brief function of a typical bank.
Am I going right and do I miss something? If sufficient then please advise future course of action.

[Farrukh Nadeem]

I think my queries are too much for you people. I regret it.

[Winston Gutkowski]

 

Farrukh Nadeem wrote:I think my queries are too much for you people. I regret it.

Not at all. I can't speak for everyone, but I simply missed your response. We're all volunteers here, Farrukh; and I've been away on family business.

I would say that your previous post is a good start. Now, you need to go through each entity in turn and describe what it does in more detail. In the old days we used to call that part the "business" or "process" analysis, because it describes the processes that a Bank has to deal with. It's also likely to provide you with a lot of the methods for your classes.

Design is NOT simple; and if this was a real system, you'd probably have done at least six months of this sort of stuff before the first Java developer got involved (possibly more). For a classroom exercise, you do have to get down to coding at some point; just not straight away.

HIH

Winston