OverviewThe exercise will create a program to keep track of the animals for sale in a pet store. Our pet store only sells mammals – specifically dogs, cats and rabbits. The program will have an interface for Mammal that can be implemented for our Cat, Dog and Rabbit classes. The implemented classes of Cat, Dog and Rabbit will be abstract classes, which will form the base class for concrete extended from those classes. For example, the Cat class will implement the Mammal interface. From there, we can have a specific type of cat such as a Persian that will be the concrete class. Someone who adopts an animal from our pet store would adopt a specific cat that is the breed of Persian.Either the Mammal class or an implemented class will implement the Comparable<T> interface. The Mammal interface will contain abstract methods that should be found in any kind of mammal (cat, dog, rabbit and so on). The base class that implements Mammal will contain the elements that are common to all of the subclasses. The concrete classes will represent the variety of forms of the implemented class. The compareTo() method will be implemented either in the base class or in the subclasses to compare attributes that are shared between the classes in the inheritance chain.SpecificationsThe project will create an interface called Mammal that can be implemented for the types of animals that we sell in our pet shop – cats, dogs and rabbits. The Mammal interface should have all of the method headers for attributes or actions that are shared commonly amongst all of the animals. There should be at least 3 methods in the Mammal interface. For example, all mammals must eat, so there may be a method for eating that when implemented, will update an attribute in the implemented animal class.The program will have at least 3 abstract class that extend from Mammal that represent cats, dogs and rabbits. The abstract classes will be the base classes for the variety of specific animals in each category. The concrete animal classes will extend from one of the base classification abstract classes. Either the abstract classes or the concrete classes will implement the Comparable<T> interface and have a compareTo() method to compare some attribute(s) of the animals. Each abstract base class should have at least 3 concrete animal classes that extend from them.The tester class, containing the main method, should be used to print the information stored and generated by the subclasses. Polymorphism should be used to create a data structure, such as an ArrayList or an array, to hold the objects that will be used to generate the output for the program. The user should be presented with a menu that will allow them to, at a minimum, see the animals available for adoption or view a specific animal in the list. The abstract base class should have at least 5 attributes for the base class. Attributes can include such things as breed, name, age or other information common to the concrete classes based on the abstract class. You have the flexibility to add as many attributes as you determine appropriate, as long as there are a minimum of 5 attributes in the base class. The program should have at least the 3 specified concrete animals with one of the concrete subclasses extending another subclass. For example, the abstract Cat class implements Mammal. The concrete class Siamese extends Cat. The concrete class Tabby_Pointed_Siamese extends Siamese, because a Tabby_Pointed_Siamese “is-a” Siamese, which “is-a” Cat.The subclasses should use the private instance variables in the base classes rather than creating duplicate instance variables in the subclasses as appropriate. HINT: Remember, public getter and setter methods in the base classes will be inherited in the extended classes. The extended class should only have instance variables for the attributes not stored in the super() class. At least 2 of the 3 extended classes should have a minimum of one additional instance method not found in the base class and unique to the subclass. The subclasses should implement or inherit the compareTo() method as appropriate. The nature of the comparison is up to you. Also, the extended classes should override the default toString() method to print specific information about the object using any of the instance variables available.The user should be presented with a menu of options for output. The output for this project should include the information stored in both the instance variables in the super() classes and any instance variables in the subclasses as well as the result of the comparison using the compareTo() method.Expected Output: The expected output should contain the contents of the instance variables for the base classes and the extended classes. The output should also contain the result of the use of compareTo() and the overridden toString(). The output should include all of the data stored in the instance variables in a way that makes sense to the user based on the menu options presented to the user.Java RequirementsThe program must contain the Mammal interface, the abstract base classes of Cat, Dog and Rabbit that implement Mammal and the subclasses that extend from the base classes.Have an interface called MammalThe Mammal class should have at least 3 methodsThere are at least 3 abstract classes extended from the Mammal class – Cat, Dog and RabbitThe concrete animal classes extend from an abstract classAt least one concrete class extends from another concrete classThe abstract classes and concrete classes are created correctly – including private instance variables and the constructorThe abstract classes or concrete classes implement the Comparable<T> interfaceThe abstract classes or concrete classes implement have a compareTo() methodThe subclasses use private instance variables correctly and have at least 5 attributes.The tester class has a data structure that uses polymorphism to store objectsThe output includes a menu allowing the user to print the information stored in the instance variables in the super class and the subclasses, as well as the result of the comparison using the compareTo() method as appropriateOnce you have it working as expected upload the .java file to this assignment drop box. You must also submit a Word doc or text file containing the Java code. Assignments not containing both the Java code and the text or Word file will be assigned a 0 for a grade.RubricCriteriaRatingsPtsThis criterion is linked to a Learning OutcomeMammal interface correctly created10 ptsFull MarksThe Mammal class is an interface that has at least 3 abstract methods5 ptsPartial CreditThe Mammal class is not an interface or it does not have at least 3 abstract methods0 ptsNo MarksThe Mammal class is not an interface and it does not have at least 3 abstract methods10 ptsThis criterion is linked to a Learning OutcomeThere are at least 3 abstract classes extended from the Mammal class – Cat, Dog and Rabbit10 ptsFull MarksThere are 3 or more abstract classes extended from the Mammal class5 ptsPartial CreditThere are at least 2 abstract classes extended from the Mammal class from the required abstract classes0 ptsNo MarksThere are 1 or no abstract classes extended from the Mammal class10 ptsThis criterion is linked to a Learning OutcomeThe concrete animal classes extend from an abstract class based on Mammal with one of the classes extended from a concrete class10 ptsFull MarksThe concrete animal classes extend from an abstract class based on Mammal with one of the classes extended from a concrete class5 ptsPartial CreditThe concrete animal classes extend from an abstract class based on Mammal or one of the classes extended from a concrete class0 ptsNo MarksThe concrete animal classes are not extended from an abstract class based on Mammal10 ptsThis criterion is linked to a Learning OutcomeThe abstract classes or concrete classes implement the Comparable<T> interface and they have a compareTo() method10 ptsFull MarksThe abstract classes or concrete classes implement the Comparable<T> interface and they have a compareTo() method5 ptsPartial CreditThe abstract classes or concrete classes do not implement the Comparable<T> interface or they do not have a compareTo() method0 ptsNo MarksThe abstract classes or concrete classes do not implement the Comparable<T> interface nor do they have a compareTo() method10 ptsThis criterion is linked to a Learning OutcomeThe subclasses use private instance variables correctly including appropriate constructor(s) and have at least 5 attributes10 ptsFull MarksThe subclasses use private instance variables correctly including appropriate constructor(s) and have at least 5 attributes5 ptsPartial CreditThe subclasses use private instance variables correctly including appropriate constructor(s) or the class has at least 5 attributes0 ptsNo MarksThe subclasses do not use private instance variables correctly nor is there an appropriate constructor and there is not at least 5 attributes10 ptsThis criterion is linked to a Learning OutcomeThe tester class has a data structure that uses polymorphism to store objects10 ptsFull MarksThe tester class has a data structure that uses polymorphism to store objects0 ptsNo MarksThe tester class does not use a data structure that uses polymorphism to store objects10 ptsThis criterion is linked to a Learning OutcomeThe output includes a menu allowing the user to print the information stored in the instance variables in the super class and the subclasses, as well as the result of the comparison using the compareTo() method as appropriate10 ptsFull MarksThe output includes a menu allowing the user to print the information stored in the instance variables in the super class and the subclasses, as well as the result of the comparison using the compareTo() method as appropriate5 ptsPartial CreditThe output does not include a menu or it does not include the information stored in the instance variables in the super class and the subclasses nor does it include the result of the comparison using the compareTo() method0 ptsNo MarksThe output does not include a menu nor does it include the information stored in the instance variables in the super class and the subclasses nor does it include the result of the comparison using the compareTo() method10 ptsThis criterion is linked to a Learning OutcomeCode compiles and runs without errors5 ptsFull MarksCode compiles and runs without errors0 ptsNo MarksCode does not compile and is automatically assigned 0 points for the overall grade5 ptsThis criterion is linked to a Learning OutcomeCode is properly commented10 ptsFull MarksCode is properly commented including all required header information5 ptsPartial CreditCode has some of the required comments but is sparsely commented or missing the correct header information0 ptsNo MarksCode is sparsely commented or not commented at all and is missing all or most of the correct header information10 ptsThis criterion is linked to a Learning OutcomeProgram is properly designed and uses whitespace effectively15 ptsFull MarksProgram is properly designed and uses whitespace effectively8 ptsPartial CreditProgram is not properly designed or it does not use whitespace effectively0 ptsNo MarksProgram is not properly designed and it does not use whitespace effectively15 ptsTotal Points: 100

Instructions are attached. They should be everything that is needed. If there any questions please do not hesitate to ask.

On this assignment I have partial code and just need to code completed and returned.Below is the instructions and files of the partial code is aComplete Lab 3 –Rental Car Client/Server. A complete set of instructions can be found in the Lab Overview under Week 3. Submit your lab. ------------------ This week’s assignment is to design and build a rental car management system using TCP and appropriate data streams. This is a multipart assignment. In the last phase of this assignment, you will have the opportunity to add threads and synchronization to this application. The application will be a rental car inventory management system. Cars can be added to the pool of cars available to rent. A car can be rented, and a car can be returned after rental. Any employee at the rental agency can do any one of these operations. More than one employee is expected to be performing these operations at the same time, so access to the information about the car inventory will need to be synchronized (when threads are added). Required data per vehicle: ID number which uniquely identifies it (i.e., VIN).Year / Make / Model info (i.e., 2004 Toyota Camry)Rental Type – Truck, Luxury Car, Mid-size Car, Compact CarMileage at Last Check-out or Check-inRental Status: Available, RentedRenter’s Name and Driver’s License Number Server inventory data: List of rented and available vehicles in the current inventory. Output Submit a Word document which contains the following: the written description of the message exchange from phase 1, the Message class code from Phase 1, screen shots of the output of both the client and the server programs from Phase 2, and your source code for the client and server from Phase 2. Benefits Understand how the client/server architecture is implemented and works. iLAB STEPS Implementation Back to Top (Links to an external site.)Links to an external site. The following phases should be implemented for this week: Phase 1: Design the message exchange between the client and the server. For each of the operations described in this document, specify the details of what values the client sends to the server and what possible values the server sends back to the client. Make sure you consider any error returns from the server. Design your Message class based on this specification. Turn in a short written description of the Message exchange and your Message class source code. Your written description should be no more than one page. Phase 2: Implement the TCP and Object stream network communication between the client and server. At this point, you should be able to send message objects between the client and the server and vice versa. Have your client sending a real add, get, rent, and return message. The server should display the contents of the received message, and return a message indicating the requested operation failed. The client should display the returned message content appropriately. Turn in screen shots of the client and server which illustrate the message exchange. Also turn in your client and server source code. The following operations should be implemented on the server side: Add Vehicle: the client must provide a unique ID number, the year – make – model info, the type of rental vehicle, and the current mileage. The server will add a new vehicle to its list of available vehicles. The server should verify that the VIN is unique. The client should receive an indication of success or failure from the server.Get Vehicle Data: the client can request to see the next vehicle’s data. The client must specify a state (i.e., Available, Rented, Any) and a specific rental type (i.e., SUV, Truck, Any). The server must keep track of the client’s position when scanning through the inventory. The server returns the next vehicle’s data which matches the requested search criteria along with any rental information. If nothing matches, the server returns a failure indication to the client.Rent Vehicle: the client must provide the ID number of the vehicle being rented, along with the renter’s name and driver’s license number. The server must check to make sure the requested vehicle is available, and if so, places the vehicle into the rented state. The server returns an indication of success or failure to the client.Return Vehicle: the client must provide the ID number of the vehicle being returned, along with the current mileage of the vehicle. The server updates the vehicle’s inventory data accordingly, returning the vehicle to the available state. If successful, the server returns the miles driven by the renter. Otherwise, an error indication is returned. User interfaces Some of the source code that is required for the development of the client side GUI has been provided. The CarInventoryClient.java file is set up to be part of the default package of a CarInventoryClient project. This means that you need to create a project called CarInventoryClient, and copy the CarInventoryClient.java file into that folder. All other classes needed for the client should be part of this project.