Not Able to upload the Zip file. It would be helpful for me if someone give me an idea about the MVC part.

You are provided with a functioning Java application and your job is to re-engineer it to attempt to improve its design and to document a specific part of its code using a UML sequence diagram. The application allows the user to select a folder on their computer's hard drive and then displays the sizes of each sub-folder present in the selected folder. The information is displayed in a table and also in a choice of chart formats. The user is able to sort the data by the name of the subfolder or by size and all the displayed charts update accordingly. The user is able to show or hide any combination of the three available chart types: bar chart, line graph and pie chart. Initial state of application on launch Cheese Sort by name bye Choose folder BAR PEWchim Doumension 2021 LINE Va 2001 12010 22 943 83 research 347911 Conuertice 119.713020 project 414509166 2021 500.8 841 po 1.406,611310 D001 1526290514 State of application once user has selected a folder and chosen both bar and pie charts from the . BarChart Pie Chart There are two re-engineering tasks to accomplish: 1. The various charts are sub-classes of DataComponent. In the present implementation the main application creates and manages the instances of the chart objects itself. Change this so that all references to the concrete implementations of the charts are confined to a single factory class and so that new chart types can be incorporated solely by making changes to the factory class. There is an additional DataComponent class called SquareChart in the datadisplay package: once you have implemented your factory class you should add the SquareChart to the application without modifying any code except in the factory class itself. 2. The present application is almost entirely contained in a single class that extends JFrame. You are required to refactor this into (at least) three classes that represent the model, view and controller architecture, or an adaptation of it. You will need to decide what functionality belongs in each of these three layers. There is no right answer to this but you must justify your decisions and contrast them with alternatives you could have chosen. You are permitted to be flexible in how you apply the MVC architecture as long as you describe what you do and why (for example, you might think that an MVA architecture is more appropriate, or you might choose not to follow the "view -> controller -> model-> view" cycle of method calls rigidly)