MVC

The idea of supporting the MVC pattern was developed as a part of Trygve Reenskaug's research in which he concluded the following key idea:

"MVC was conceived as a general solution to the problem of users controlling a large and complex data set. The hardest part was to hit upon good names for the different architectural components. Model-View-editor was the first set. "

– http://heim.ifi.uio.no/~trygver/themes/mvc/mvc-index.html

One of the biggest problems in computer science is related to naming things, which is why the original name was Model-View-Editor. It later evolved into MVC, as mentioned in the preceding link:

"After long discussions, particularly with Adele Goldberg, we ended with the terms Model-View-Controller."

MVC is a software architectural pattern that makes it possible to establish a clear separation between the domain objects of an application (where the business logic resides) and the elements that are used to build the UI. 

With this concept in mind, the isolation and separation of concerns between these parts are quite important. They also constitute the underlying principles to build applications using this pattern. In following sections, let's review how the business logic and presentation layer of an application fits within the MVC pattern.