MVC in Software development using java swing

I'm developing a software project in java swing. I want to follow MVC design pattern for better maintainability, portability and reliability. I've looked upon MVC in Swing on internet and found some good results like THIS , THIS , THIS, THIS, THIS and few more (youtube too) and studied them. Then I built a design architecture for my project based on MVC design pattern. Here is the structure which simulate my actual requirements:

Here is little description about the architecture

• Main Controller: It is responsible to initialize and to start the application. It initialize MainView and some other sub-controller like StudentController,TeacherController. It Contains some methods like getStudentView(), getTeacherView() which provide viewable components of Student TAB, Teacher TAB to MainView
• Main View: It is the main view which is JFrame that contains JTabbedPane which uses MainController#getXXXView() to display view in its tabs. (Here XXX can be replaced by Student, Teacher or any other viewable component which is provided by Main Controller
• Student Controller: It controls the StudentView and Student model and Student model interface. It initialize the Student View and provides this view to Main Controller which is further provide view to Main View
• Student View: It is a JPanel which contains JTable to display the student information and some JButton like add Student, Edit, delete etc.
• Student: It is Student model class that has name, rollNo etc fields to store student information.
• Student Model Interface: It is service layer. It takes a Student argument and send/add it to Student Viewable Model and store into database using Student Database Model.
• Student Viewable data Model: It is a TableModel that is used to define JTable in Student View
• Student Database Model: Contains method to store/retrieve student information in/from database
• Teacher Controller: Just like Student Controller except it controls the teacher related tasks.
• Other Controller: Represents many Student Controller like controllers

NOTE Teacher Controller and other controllers have same hierarchy as that of Student Controller. These controllers access their models and view. For e.g. Teacher Controller have Teacher View, Teacher and Teacher Model Interface

Working of the project

• Firstly Main Controller initialize the Main View and all the sub-controllers and start the application.

• Student Controller implements ActionListener and act when there is an event in Student View. It is responsible to add, edit, delete student information. It takes information from Student View, wrap in Student object and pass it to Model Interface

• Model interface then pass Student Object to Student Database Model which store/update/delete the data in database. If it is successful, then Model Interface update Student Viewable data model which is a Table Model that reflects changes in Student View

So my question is whether it is a good design for this kind of application and if it is not, then what should do I do. How can I refine the design for better maintainability, reliability portability. What are some recommendations

I think its a straight and rigid question but I can't do better.