In this phase of the project, you learn about basic software architecture patterns by starting to create a backend for the PetClinic application based on the existing PetClinic website.
These patterns ensure our software is extensible, robust, maintainable and reusable.

PetClinic Reference Application

• Implement a 3-Tier pattern by completing the TODOs below.
• Implement an MVC pattern by completing the TODOs below.
• Implement a simple inheritance pattern by completing the Coding to Interfaces - Repository section below.
• Implement simple Coding to Interfaces patterns by completing the Coding to Interfaces - Service and Coding to Interfaces - Controller sections below.

• Implement unit test stubs by completing bonus activity 1.
• Identify software design flaws/limitations by completing bonus activity 2.

• Starter code for all models.
• Starter code for all controllers.
• Starter code for all services.
• Starter code for all repositories.
• Starter code for the driver class.
• A FakeDatabase used to store data.

• Complete the TODOs in the model package.
• Complete the TODOs in the repository package.
• Complete the TODOs in the service package.
• Complete the TODOs in the controller package.
• Complete the TODOs in the PetClinicDriver class.

• In your repository package, create a new abstract class called BasicRepository.
• In the BasicRepository, add one field - a protected FakeDatabase.
• In the BasicRepository, add a default constructor that initializes the fakeDatabase field to an instance of the FakeDatabase.
• Have each of your Repositories extend your new BasicRepository.
• Remove the FakeDatabase field from each of your repositories.
• Remove the constructor from each of your repositories.

• Inside your service package, create a new interface called BasicService.
• BasicServce is a generic class that defines the following methods:
  • T add(T t);
  • T get(int id);
  • T modify(T t);
  • boolean delete(T t);
  • List<T> getAll();
• Modify each of your services to implement BasicService.

• Inside your controller package, create a new interface called BasicController.
• BasicController is a generic interface that defines the following methods:
  • T add(T t);
  • T get(int id);
  • T modify(T t);
  • boolean delete(T t);
  • List<T> getAll();
• Modify each of your controllers to implement BasicController.

Create test classes for each of the controllers you added by completing the following:

• Place your cursor on the class name in the class header of the source code of the class you want to create the test for.
• Hit Alt-Enter.
• Select create test then select all of the methods listed then click OK.
• Do this for each of your controllers.
• You do not need to implement any code for the tests - we're just creating the test stubs.

• There is a design flaw in the FakeDatabase and how it stores data. See if you can figure out what it is.
• Hint: It has nothing to do with the code in the FakeDatabase itself. It has to do with how models are stored in the FakeDatabase.

• Use the existing code as a pattern to complete the rest of your code.
• We are NOT creating a front end for this application. The PetClinicDriver acts as the front end (or view) for this application. Feel free to add to the driver as needed.
• In this phase, you do NOT use Spring or Spring Boot. Just plain ol' Java.
• In this phase, don't worry about handling errors.