Draw a class diagram for the following Java code:class Account {
public String PIN;
public String name;
public int balance = 0;
}
interface CardUse {
public int read(String PIN);
public void reduceBy(int amount, String PIN);
}
class BankCard implements CardUse {
private int usage = 0;
private String owner;
private Bank bank;
public int read(String PIN) {...}
public void reduceBy(int amount, String PIN) {...}
}
class Bank {
private Account [] accounts = new Account [10];
private int number = 0;
private Account findAccount(String name, String PIN) {...}
public int getBalance(String PIN, String name) { ... }
public String createAccount(String name, int startAmount) { ... }
public CardUse getBankCard(String name, String PIN) { ... }
}
- Initial values may be given in the attribute specification.
- Check the visibility! It is represented by different icons in Rational Rose.
- An interface is modeled by a class with a stereotype "interface" (set
"Show Sterotype" for the class). Its implementation is a special inheritance
relationship.
- Attributes in Java may become associations in UML (e.g., BankCard.bank, Bank.accounts).
- The use of a class in an operation signature (e.g., Bank.getBankCard) introduces a
dependency relationship (e.g., Bank is dependent on CardUse).
