cpsc2150 Lab 11-Model-View-Controller architectural pattern Solved

 In this lab you will be working with the Model-View-Controller architectural pattern with a Graphical User Interface created using Java Swing. The View (GUI) is provided for you, and you have already completed the Model. For this lab, you will just need to complete the Controller.

 

Instructions 
 You will need to create a new project with a package called cpsc2150.banking. Add your Mortgage and Customer classes and interfaces from lab 6 to that package. (Note: You will need to create the models folder for these files to match their package structure.) Add the IMortgageView and IMortgageController interfaces from last week’s lab to the package and the provided MortgageGUIView class to the package as well to be your Graphical User Interface.  

 

MortgageGUIApp.java 
 MortgageGUIApp will be a very simple class. It will contain our main method that will be the entry point of the program. All it will do is declare an instance of IMortgageView and IMortgageController, and connect them. After that the system will wait for an event from the IMortgageView object. The code should look like:

 

package cpsc2150.banking; 

 

public class MortgageGUIApp { 

    public static void main(String[] args) {         IMortgageView view = new MortgageGUIView(); 

        IMortgageController controller = new MortgageGUIController(view);         view.setController(controller); 

    } 

} 

 

 This type of set up is common when using MVC architectural pattern in Java. We just need the entry point to set up our Controller and View. Set up your configuration so this is the entry point for your program.

 

IMortgageView.java and MortgageGUIView.java 
 This interface and implementation will serve as the View layer of our system. They provide several methods to get input from the user and display output to the screen. The View layer does not provide any input validation. That will need to be handled by the Controller.

 Inspect the interface to make sure you understand what methods are available to you. Read through the code for the view as an example of building an interface in Java Swing. You should not need to make any changes to these files. 

 

Note: The IMortgageView and MortgageGUIView files should be placed inside a new views folder to match the package cpsc2150.banking.views.

 

MortgageGUIController.java 
The MortgageGUIController class implements IMortgageController and serves as the Controller layer in our MVC architecture. It controls the flow of control in our program. This class is able to use both the view and the model layers to accomplish this task. This class will check to make sure the data that the user provides (through the View layer) meets the preconditions that exist in our Model layer. If the input is not valid, the Controller will (through the View) alert the user to the error and wait for them to correct their input and resubmit. If there are multiple errors the Controller only needs to report one to the user. The MortgageGUIController class will also use the Model layer (Mortgage and Customer class) to apply for the mortgage. After a mortgage has been applied for, the Controller will (through the View layer) say whether the loan was approved or not. If the loan was approved, then the rate and monthly payments will be displayed as well. If the loan was denied then 0 will be displayed for the rate and monthly payment.

 The MortgageGUIController class will have one private field, an IMortgageView object, which is set by an argument passed into the constructor. The MortgageGUIController class will have one public method, called submitApplication() which is called after the user hits the submit button. The view layer is already observing the submit button, and will call submitApplication when the user clicks the submit button. Remember, in last week’s lab we were following procedure-driven control and now we will be following event-driven control. submitApplication() will just be responding to one click of the button, not running several applications.

 All the logic concerning validating the Model’s preconditions, and the order of events, is handled by the Controller layer. The logic concerning the mortgage application or the customer itself are handled by the Model Layer.  

                Your starter code for the Controller layer is as follows:

 

package cpsc2150.banking.controllers; 

 

public class MortgageGUIController implements ImortgageController {     private IMortgageView view; 

 

    public MortgageGUIController(IMortgageView v) {         view = v; 

    }  

    public void submitApplication() { 

          //Your code here 

    } 

}  

Note: The IMortgageController and MortgageGUIController files should be placed inside a new controllers folder to match the package cpsc2150.banking.controllers.  

                 

TIPS and additional Requirements
-          You do not need to provide a makefile for this assignment, nor do you need to test your code on SoC Unix (GUIS and Unix don’t play well).

-          You will zip up your IntelliJ project directory and submit that on handin.

-          You do not need to provide any automated testing, although you should test your program.

-          You do not need to provide any contracts for your code as they should be available from other assignments.

-          You DO need to comment your code

-          You need to follow the Model-View-Controller architectural pattern for this assignment.

o   All interaction with the user goes through the View class. View does not have access to the Model.

o   Controller handles input validation, and the order of events of the program. The Controller has access to the View and the Model, so it is the go between for those two layers

o   The Model handles our entity objects and the “lower level” logic. It does not have any access to the other two layers.

-          Follow our best practices: No magic Numbers, information hiding, separation of concerns, etc.

-          The Controller will be very different from lab 10, as the flow of control is very different now that we are using a GUI and are reacting to button clicks.

-          Make sure to understand what all the methods in our View layer do. They will be very helpful.

-          Depending on the resolution of your screen, it may be difficult to read the text on the GUI. Java Swing is not great with font sizes.

-          You may not need all the methods provided by the IMortgageView interface to complete this assignment. It is fine to not call all of the methods provided.  

 

Partners
You are required to work with one partner on this lab assignment. Make sure you include both partners' names on the submission. You only need to submit one copy. Remember that working with a partner means working with a partner, not dividing up the work.