Handed out: Thursday, February 7, 2008 Due: Wednesday February 13, 2008, by 10PM using Web Turnin This assignment is your first code implementation of a small piece of the interactive program called "ICritters". Create an Eclipse Project containing the classes listed on the Class Diagram. Your code will be expected to be able to execute the sequence given on the Sequence Diagram, and all of the methods listed on the Class Diagram. The sequence diagram shows a user (perhaps just a testing program (hint, hint)) interacting with the classes listed. An owner wishes to buy a cheap treat, and then proceeds to give the treat to his ICritter. Notice all of the "housekeeping" that is done by myICritter in the ICritter class to keep track of its reactions. A note on arrays in the Class Diagram - use ArrayLists as the concrete representations for this, see listTreats in the Owner class below. If a methods return type isn't listed, you can assume void. Some methods of note: In Owner: Owner() - Constructor should create a default ICritter and Owner should start with at least 1 credit. adjustCredits( Integer ) - takes the number of credits to adjust the Owner's credits by. addTreat( Treat ) - adds a treat to the Owner's list of treats. listTreats(): List - this should return a List of Treat objects possibly empty. buyCheapTreat( String ) - this requires a description of the treat, this description will be stored in the treat. In ICritter: getReaction( Treat ) - for now the ICritter will always be joyful (of some amount) with whatver treat it receives, yay! addMemoryReaction( Treat, ICritterReaction ) - we want the ICritter to keep track of its experiences, it will keep track of these values (Treat, ICritterReaction) in ICritterMemoryEvent objects, which it stores in its memories. Administrative: + You will be turning in your Eclipse Project, using Web Turnin. Turn in your project by 10PM Wednesday. Your turnin folder *and* eclipse project name will be: ___hw2 Follow this template or lose points. Grading: + We will be running your code against test code - functioning code will be part of the grade. + Code style will also be a part of the grade. Tips: + Since your code will be run against test cases, method signatures are important. + Check the newsgroup for updates and clarifications, but please, don't post your code to the newsgroup! V1.3 - iv