Drawing Class Diagram - Exercise
Define all class data for the Checkbook Manager program
Objective: Define the class data for all the classes of your Checkbook Manager program.
This exercise is not scored. It's an opportunity for you to check your understanding of the material covered in the preceding lesson.
When you are finished, click the Submit button to view the suggested results.
In a previous lesson, we identified the following real-world entities that are involved in managing a checkbook: account, checking account,
savings account, CD, money market account, credit card, charge card, Visa, MasterCard, American Express, Discover, stock, bond, social security
number, money, check, ATM card, budget, mutual fund, bank, loan, mortgage, checkbook, ledger, cash. Since then, you narrowed the list to
Bank. You improved the design of
Check by creating classes
Date to hold attributes of
Check. (It's not uncommon to discover additional classes you need at later
stages of modeling.)
Draw class diagrams for these six classes (
Date) and any others you feel belong in the system. The diagrams should indicate the names of the classes, the names of the attributes,
and the types of each attribute. When an attribute is an instance of another class, draw a line to that class. You may prefer to create separate
detailed diagrams for each class and an overview diagram for the relationships.
The following three classes should be included in your project, but we've spelled them out for you because you probably wouldn't come up with
them with unless you are familiar with object-oriented design.
Your project should include a
Bank class that represents any institution where an account is stored and a
DepositList class that hold lists of checks and deposits respectively.
Money class is simple, just two integer attributes:
We represent a bank by a name, a phone number, and an address, all three stored as strings.
Recall that although we speak of a phone number, no arithmetic is ever performed on it, and it may contain punctuation, spaces, and alphabetic
characters as well as digits: for example, (800) JKL-BANK. Therefore, a phone number is really a string data type, not a number.
Next come the list classes. Note that I do not specify any algorithm for storing the list at this point.
The list might be a growable array, a linked list, a hash table, or something else. Implementation details can wait for a later time.
On the other hand, you do need some means of indicating a list, so I've adopted the convention of using array brackets, .