10-152-312 - Object-Oriented Programming 2

Refactoring the movement algorithms

1. Create the static MoveHelper class as shown in the diagram above
2. Take the code from Animal's Fly(), Pace(), and Swim() methods and put it inside the appropriate method in the MoveHelper
3. Alter the algorithms to use the passed-in animal parameter
4. Remove the Fly(), Pace(), and Swim() from Animal, as that code has been encapsulated and is no longer needed
5. Call the appropriate MoveHelper method from each animal's Move method
6. Run your application and test that the animals still move as they did before

Moving animals with timers

1. Add the RepaintHandler to the AnimalCageWindow as shown in the diagram above
2. Type the following code in the RepaintHandler to handle threading issues between painting and timer threads

3. Add the repaint timer to the AnimalCageWindow as shown in the diagram above
1. In the constructor, initialize the timer to a new timer with an interval of 1 second
2. Add the RepaintHandler to the timer's Elapsed event handler (using += notation)
3. Start the timer
4. Add the NonSerialized attribute to the timer
4. Remove the moveAnimals and repaintAnimals buttons and their click handlers (the timers are replacing that functionality)
5. Alter the animalGrid so that it fills the entire window
6. Add the MoveHandler to Animal as shown in the diagram above and call the Move() method from it
7. Add the move timer to Animal as shown in the diagram above
1. In the constructor, initialize the timer to a new timer with an interval of 1 second
2. Add the MoveHandler to the timer's Elapsed event handler (using += notation)
3. Start the timer
4. Add the NonSerialized attribute to the timer
8. Add a window_SizeChanged event handler to the AnimalCageWindow and call DrawAllAnimals() from it
9. Run your application and test that the animals move and are repainted automatically every second

Implementing the strategy pattern with animal movements

1. Create the IMoveBehavior interface as shown in the diagram above
2. Create the three move behavior classes and implement the interface as shown in the diagram above
3. Add an IMoveBehavior field and read/write property to Animal
4. Set each animal's MoveBehavior property to the appropriate behavior in its constructor, using inheritance and overriding where appropriate
5. Refactor the movement algorithms in the MoveHelper into the MoveHorizontally() and MoveVertically() methods and use the moveDistance parameter where appropriate
6. Call the MoveHorizontally and MoveVertically methods from the move behavior's Move() methods in a way that preserves each movement
7. Remove all Move() methods from descendant animals (to reduce redundancy)and implement Animal's Move method by calling MoveBehavior's Move method
8. Run your application and test that the animals still move as they did before

Testing the strategy pattern

1. Create an enum of move behavior types as shown in the diagram above
2. Create the MoveBehaviorFactory as shown in the diagram above (it will function similar to the AnimalFactory)
3. Add a combo box to the MainWindow and populate it with the MoveBehaviorType enum
4. Add a button to the MainWindow that changes an animal's move behavior
1. Use the animal selected in the list box
2. Set its MoveBehavior to the type chosen in the combo box
5. Run your application and test that an animal's move behavior changes when the button is clicked

Implementing the strategy pattern with more animal behaviors

1. Implement the pattern with the following reproduction behaviors
1. GiveBirthBehavior
2. LayEggBehavior
2. Implement the pattern with the following eating behaviors (move weight gaining code to Eat methods)
1. ConsumeBehavior
2. BuryAndEatBoneBehavior
3. ShowAffectionBehavior

Birthing animals

1. Add a button to the MainWindow that births an animal
1. Use the animal that is selected in the list box
2. Find the vet employee
3. Birth the selected animal if it is actually pregnant
4. Add error handling and/or null checks where appropriate

3.3 Zoo Assignment: Package Diagram

Create/revise the classes as indicated by the following UML package (class) diagram.

Notes

• Create WPF Window classes if class names end with Window; otherwise create basic classes.
• Note that not all classes need to be on a class diagram; if classes which existed previously do not appear on this particular diagram, they should not be deleted, as they are simply not relevant to this assignment, but may again be used in future assignments.

3.3 Zoo Assignment: Class Diagram

Create/modify the classes as specified in the following UML class diagram.

3.3 Zoo Assignment: Wireframe

Design the user interface per the following diagram.

Grading and Submission

1. Build/compile your program
2. Debug/test your program against the following rubric:

3. Make your code StyleCop-compliant
4. Close your Visual Studio solution
5. Compress your Visual Studio solution to a zip file
6. Submit the zip file via Blackboard