What basic assumption underlies the "Model$-$View$-$Controller"? Select one: Program code, illustrations of the program code, and modifications of the code should be handled separately. O Sequence diagrams, illustrations of the diagrams, and errors in the program code should be handled separately. O Data, visualization, and user input should be handled separately. Data, sketches of the user interfaces, and errors in the program code should be handled separately. What are the main components of the "Model$-$View$-$Controller"? Select one: O Data, sketches of the user interfaces, and errors in the program code should be handled separately. O Sequence diagrams, illustrations of these diagrams, and analysing errors in the program code. Program code, illustrations of the program code, and modifications of the code. Data, visualisation, and dealing with user input. What is the basic idea behind the "Model$-$View$-$Controller"? Select one: The Model contains the program code, the view illustrates the program code, and the controller allows for modification of the code. O The Model contains the sequence diagram, the view illustrates the diagram, and the controller analyses errors in the program code. The Model contains the data, the view visualizes the data, and the controller deals with user input. The Model contains the data, the view is a sketch of the user interface, and the controller deals errors in the program code.