Question

Programming Assignment 5: UML Diagram

Objectives: After successfully completing this assignment, students will practice Object Oriented design by creating an UML diagram for a Java program.

Program Statement: Bank System You were asked to create a simple UML diagram for a bank system. Each bank has a specific identification number, a name, and a location that needs to be stored. Tellers serve customers’ loans, checking and savings accounts. The bank must know each tellers’ name and identification number for record keeping. Each account type has a unique identification number, an opening date, a balance, and the customer’s id associated with it. Checking accounts must also store a checkbook ID. Each loan must store its identification number, type, total loan amount, remaining loan balance, interest rate, and the customer id associated with it. The bank needs to know and store each customers’ identification number, name, address, and phone number.

Once a customer enters the bank, a teller needs to be able to open an account, collect money from the customer, close an account, process a loan request, provide account information, and issue a bank ID card. The customer needs to be able to ask a general inquiry, deposit, withdraw, open and close an account, and apply for a loan.

Create a UML diagram to the best of your abilities following the information given in class. Include at least all classes, attributes, and methods mentioned and deduced from the problem. Make sure to use the standard Java naming convention for all your variables, methods, parameters, and classes. Also, remember to use the right type of arrows and notation for associations, etc.

Furthermore, although only the most important methods are generally added to UML diagrams to keep them more readable and less clogged, for this assignment you should add all constructors, getters, and setters to reinforce the concept of their importance in all Java classes.

Common mistakes to avoid:

• Not sending the right file format (JPG or PDF)

• Not adding multiplicities in all sides of connections (lines)

• Using wrong naming or syntax

• Forgetting to add one or more classes

• Not adding get-set methods

• Not adding constructor methods

• Not setting most variables as private

• Using wrong symbols or line types-arrows

• Having a confusing diagram with too many crossing lines

Answer 1