Short/quick explanation of .net mvc

Question

What would be the shortest explanation for .net mvc (for a manager to understand at a high level, how it works, benefits etc).

Answer 1

You might start here.

ASP.NET MVC enables you to build Model View Controller (MVC) applications by using the ASP.NET framework. ASP.NET MVC is an alternative, not a replacement, for ASP.NET Web Forms that offers the following benefits:

• Clear separation of concerns
• Testability - support for Test-Driven Development
• Fine-grained control over HTML and JavaScript
• Intuitive URLs

As curtisk points out in his answer, wikipedia has a good description as well:

Model–view–controller (MVC) is an architectural pattern used in software engineering. Successful use of the pattern isolates business logic from user interface considerations, resulting in an application where it is easier to modify either the visual appearance of the application or the underlying business rules without affecting the other.

Answer 2

Managers like code metrics, indicators and statistics. An important measure of code quality is coupling. Explain to your manager that MVC reduces coupling and this in turn makes your program more flexible in the long run.

There are a couple of metric calculators out there, here is one on codeplex.

Here is another software for software metrics and it also explains them. Check the metrics that refer to coupling.

Answer 3

In a nutshell, ASP.net MVC offers better modularity and testability than asp.net webforms. A drawback though is that you lose some of the abstractions that webforms offers you, so some things require a little more work to wire up.

Answer 4

First paragraph of http://en.wikipedia.org/wiki/Model-view-controller , and really MVC is not remotely tied to asp.net, just give the language agnostic pattern description