title: How ASP .NET MVC architecture fits into the traditional multi layered architecture
body: <p>Moving from the traditional way of architecting web applications with a Business Layer, Service Layer, Data Access Layer and a Presentation Layer to the MVC design pattern, I find it difficult to understand how it fits in the old model.</p>
  
  <p>It seems to be that the MVC model itself already has done allot of the separation of concerns that is needed and used to be achieved via a layered architecture. Can someone shed some light on this subject please?</p>
  
  <p><strong>As a reference, below is how I understand it, please share your view on this</strong></p>
  
  <p>MVC Views and Controllers along with View Models -are- <em>Presentation Layer</em></p>
  
  <p>MVC Models - could be - <em>Data Access Layer or Business Layer or even Service Layer</em></p>