• Understand the rationale for object-oriented design and programming.
• Understand data abstraction and abstract data types.

You should implement and test two classes. The Transaction class represents a transaction that may take place in a checking account. The class should accessors and mutators (get and set) for the following fields: date (GregorianCalendar), payee (String), amount (double), category (String), memo (String), status (byte where 0 represents reconciled). For example, the class should have a getPayee() method which returns a String containing the payee's name and a setPayee(String name) that sets the payee field of the object to the name that was passed to the method.

The CheckingAccount class is described by the following UML class diagram:

+--------------------------------------------------------------------------------------------+
|                                      CheckingAccount                                       |
+--------------------------------------------------------------------------------------------+
| You decide appropriate fields                                                              |
+--------------------------------------------------------------------------------------------+
|+CheckingAccount(name: String, initialDeposit: double, date: GregorianCalendar)             |
|+transact(transaction: Transaction) : void                                                  |
|+getCurrentBalance() : double                                                               |
|+getBalanceOn(day: GregorianCalendar) : double                                              |
|+getTransactionsBetween(start: GregorianCalendar, end: GregorianCalendar) : Transaction[]  |
|+getTransactions(quantity: int) : Transaction[]                                            |
|+getAdjustmentsBetween(start: GregorianCalendar, end: GregorianCalendar) : Transaction[]   |
|+getAdjustments(quantity: int) : Transaction[]                                             |
|+getCreditsBetween(start: GregorianCalendar, end: GregorianCalendar) : Transaction[]       |
|+getCredits(quantity: int) : Transaction[]                                                 |
|+getDebitsBetween(start: GregorianCalendar, end: GregorianCalendar) : Transaction[]        |
|+getDebits(quantity: int) : Transaction[]                                                  |
|                                                                                            |
| You decide appropriate private methods                                                     |
+--------------------------------------------------------------------------------------------+

• Transactions take three forms:
  1. Adjustments - Bank created transactions for assessing fees and crediting interest. The category field of an adjustment transaction should begin with "Interest Earned", "Bank Fee:", or "Bank Credit:"
  2. Credits - Any non-adjustment transaction that increases the balance of the account.
  3. Debits - Any non-adjustment transaction that decreases the balance of the account.
• Interest should be calculated at the end of each month. The annual interest rate is 1.06% and should be calculated based on the average daily balance in the account for the month.
• In any given month, if the average daily balance is below $1500, no interest is earned.
• In any given month, if the average daily balance is below $500, a $3.95 fee is assessed at the end of the month.
• A $10 fee is assessed for each withdrawal that forces the account balance to become negative.
• You should accept withdrawals, even if the balance is negative.
• A $10 fee is assessed for each withdrawal on an account with an already negative balance.
• Your class should handle up to 2000 transactions (including adjustments).
• *You may assume that all transactions are entered into a checking account in chronological order. That is, if CheckingAccount::transact(transaction) is called where transaction has the date of December 2, 2004, CheckingAccount::transact(transaction2) will only be called when transaction2 has a date of December 2, 2004 or after.
• *You may also assume that no transaction will be entered on a date prior to any of the previous calls to CheckingAccount::getBalanceOn(date).

Constructor that creates a CheckingAccount object known as name with and initial balance of initialDeposit on date.

Adds the transaction (either a credit, debit, or adjustment) to the account.

Returns the current balance in the checking account.

Returns the balance in the checking account at the end of the day.

Returns an array with all of the transactions that occurred between the beginning of start and just prior to the beginning of end.

Returns an array with the last quantity transactions.

The remaining getXxxxBetween(start, end) and getXxxx(quantity) methods should operate like they getTransactionsBetween(start, end) and getTransactions(quantity) methods except that they should only return the appropriate transactions, e.g., (getDebits(quantity) returns an array of the previous quantity transactions that are debits.

In addition to these methods, you may choose to create additional methods. This is fine, however, any additional methods should be private.

You should write a program to test the implementations of the two classes you are required to write as part of this assignment. Keep in mind that you do not need to implement the classes before writing the test program.

Use the lab 1 template file to use as a starting point for this report. You can just leave the the other sections blank.

Continue using the XML file that you submitted in week 2.

The lab report need not be self-contained. Your report should include:

• Discussion (sample program output, problems you encountered (and how they were overcome), etc.)
• An activity log indicating how much time you spent on each phase of the assignment. You should use the format found in the template XML file and report the time in the following categories:
  • Design
  • Coding
  • Debug (before you think it's working)
  • Test (after you think it's working)
  • Writing Report
  • Other
• Conclusions (what you learned, suggestions of how the assignment could be improved, things you would have done differently, etc.)
• Documented source code for your program.

As with any report you submit, correct spelling and grammar are required. In addition, your report should be submitted electronically following the Electronic submission guidelines. (You may wish to consult the XML help video and/or sample report before submitting your report.) Be sure to keep copies of all your files, in case something gets lost.

Your grade will depend on quality of design, clarity of code and documentation, as well as whether your program produces the correct results. If you have any questions, consult your instructor.

This laboratory assignment was developed by Dr. Chris Taylor.

© 2001-2006 Dr. Christopher C. Taylor

Office: CC-36C

Phone: 277-7339