ASP.NET MVC application architecture

I read too many article to understand the MVC architecture in simple word. Many ASP.NET developer things, if you know the ASP.NET then you can easily learn MVC but many of them just don't get the stuff :). The concept of Views, Controllers, Models etc is clear for many of them but most of them are bit confused with the syntax and flow of MVC. 
Honestly I'd say learn more about ASP.NET MVC if you see the Classic ASP and MVC as similar beasts like no user control, just have to use HTML controls and tags. but the difference is architectural style and modern day of programming techniques. If you will see MVC, MVC is more focused of "Separation of Concerns", here the concerns are the different aspects of software functionality like the "business logic" of software is a concern. The separation of concerns is just keeping the code for each of these concerns separate that means Changing the interface should not require changing the business logic code, and vice versa.
Here HTML and CSS are the example of separation of concerns, HTML file is defines the document structure where as CSS file defines how the document is presented on your screen. Todays Model-View-Controller (MVC) design pattern is an excellent example of separating these concerns for better software maintainability.
MVC has been the most productive and conceptually, the simplest to grasp programming pattern. I will not go in depth in 'beauties' of MVC. but just basic of MVC. so lets start MVC'ing :)

When we see more closer to Views and Controllers, their ownership itself explains separation. View are just presentation form of application. Controller is only provides the services. The model is independent of view and controllers its just a business entities. Controller is independent of view and model, its purpose is to handle the requests as per routes defined and rendering view if needed. so here model, controller and view independent of each other.
As grammatically guidelines, your views should only contain display code not data retrieval or processing logic for(e.g. calculation, datetime formatting, currency calculations, html attribute color changes logic etc.). The controllers should take care of the non-display logic.

Below diagram will explain traditional way (classic ASP, WebForms) and MVC way of routing,

Request-response flow of MVC, 

The browser, as usual, sends a request to IIS. IIS searches for the route defined in the MVC application and es the request to the Controller per the route. The Controller communicates with the Model and es the populated Model (entity) to the View (front end). Views are populated with Model properties, and are rendered on the browser, ing the response to the browser through IIS via Controllers that invoke the particular View.