hts.StevenWood.com

^MC™

Memo

Reference: HTS Bank 5   

Required parts:

1. Add error checks to all of your methods. Make sure that your values are acceptable. For example:
   1. Check to make sure that the customer does not withdraw more than is contained in the account.
   2. Check to make sure that the customer does not deposit more than $1 million (or the legal limit for a RESP) without authorization code (e.g. bank manager's password).
   3. set daily limits for withdrawals
2. Give users a chance to confirm changes. E.g.:
   Current name is: Ethan
   Press enter to keep or enter new name:
   **Name not changed **
3. Expand the number of useful attributes. (You need more than the "original 5" from HTSB2).
4. Expand the number of methods that you have. "Get" and "set" all reasonable items.
5. Set up a menu using a loop. Here is an example.
6. Have more than one of YOUR objects (e.g. 3 accounts, 3 RRSP, 3 loans, 3 exchanges, etc.) created by the user, being able to select and work with each. Here's an example.

Some things to try:

Note:  You do not have to do all of these, but do at least one.

1. Put your accounts into arrays so that you can prepare reports about your customers. Look back in your school notes on how to use arrays.
2. If you do not save the values entered in your program (see the item below), you MAY add a few "preset" objects directly in your main method. (e.g. Dog d1 = new Dog ("Fluffy", 4, "White"); // name, age, colour) and then demonstrate how your code can capture information for another object entered through the keyboard. Your code should allow you to find information about ANY of the objects created.
3. Add to your classes the ability to save information on disk. Look back in your school notes on how to use the File class. Here are some help to do this **advanced** topic:
   • File Writing pdf notes
   • File Reading pdf notes
4. Make a master HTS Bank program that will work with all accounts (savings, chequing, child), currency exchange, RESP and loan accounts. (You only need to make YOUR section actually do something.)
5. Implement one of the other classes (and some methods for them).
6. Something else that will show your version of HTSB is better than the others.

MAKE SURE YOU KEEP A COPY OF THIS MATERIAL FOR YOURSELF.

You will want to refer to the attached document (Rubric - HTS Memo 5) to see what I am looking for.

I expect this information to be in my hand by the date on the outline [click to find due date].