reza1975 / 03-inheritance

This is an assignment to the class Programmieren 3 at the University of Applied Sciences Rosenheim.

Assignment 3: Inheritance revisited

In this assignment we'll be looking at

• a classical refactoring situation: you have code that works, but with bad implementation
• abstract classes
• final classes
• when to use abstract base classes

Given is a class Animal which represents an animal with a lifecycle. The class is borrowed from a zoo game as you see when you inspect the given methods. As (game) time progresses, the main game engine calls .tick() on every animal to simulate the progress of time. In the following you can see the lifecycle of the animal modeled as state machine.

1. it starts in a sleeping state
2. after a certain time it awakes and is hungry
3. if you feed it in time it starts to digest otherwise it's dying
4. again after a certain time it has finished digesting and is getting in a playful mood (now you could collect() money)
5. once again after a certain time it's getting tired and goes back to sleep

Setup

1. Create a fork of this repository (button in the right upper corner)
2. Clone the project (you're getting the link by clicking the green Clone or download button)
3. Import the project to your IDE (remember the guide of the first assignment)

Your Assignment

First, understand the given implementation of the Animal.tick() method which is based on a switch-case; see the AnimalTest class for example state transitions. Your job is to replace the existing switch-case by a clever polymorphism construct (which might be difficult to understand in contrast to the relatively simple state machine). To get you an idea how this is possible, consider the UML diagram below. It models an abstract base class State which implements (!) the tick() method and has an abstract method successor(). This method is needed to get the successor state if enough time passed (e.g. the animal has completed digesting and is getting in playful mood).

Note that the State.tick() method should be marked final; why is that?

Hint: there's still one special case: when the animal was fed it's switching to the digesting state immediately no matter how long it was hungry before.

The test suite to ensure that the behavior is still the same is given, too. That's a classical refactoring situation. You want to replace an existing implementation by a better one but the behavior shouldn't change. Now you might get an idea why test cases are important beside the fact that they ensure that you're implementation is working correctly when you do it the first time.