*Liskov Substitution Principle* This Java code is poor! It violates the Liskov Substitution principle! Restructure this code as UML and draw a UML Class Diagram of restructured code that doesn't violat the Liskov Substitution principle. Draw a well-designed UML class diagram to represent this information. Provide the basic abstractions attributes, methods, relationships, multiplicities, and navigabilities as appropriate. "... and // ... means much code is omitted. This Java code is about reading CBZ files which are compressed comic books. They are a zip file of PNGs with ordered filenames. *Be sure to leave a note on the diagram highlighting how you address the violation* public interface Filecontent \& public Path getPath(); public byte[] getData(); \} public class Zipfile \{ // Work on the zip file File zipFile protected File zipFile; // Represents a single zip file for reading and writing public ZipFile(File zipFile) \{ // \} // Gets the file contents from the zipfile public Filecontent getFileContent(Path path) \{ //