Home > ASP.NET MVC, Introduction > ASP.NET # MVC # 1 – MVC Design Pattern Introduction

ASP.NET # MVC # 1 – MVC Design Pattern Introduction

MVC Design diagram

**Model–view–controller (MVC) is a software architecture,currently considered an architectural pattern used in software engineering. The pattern isolates domain logic (the application logic for the user) from the user interface (input and presentation), permitting independent development, testing and maintenance of each (separation of concerns ).

*It is a classic design pattern often used by applications that need the ability to maintain    multiple views of the same data

* separation of concerns means keeping Database logic,Business logic and UI logic independent of  each other

* You can find MVC in java as well as c++ and in asp.net also


What is Model-View-Controller?

1)Model:-It is a set of classes those represent the Data that we working with as well as the business rules how the data will be exchanged ,changed and manipulated.

2)View:- It is the application’s user interface(UI)


      The Controller communicates with the front end of the model and loads the appropriate    data


Advantage of MVC Design pattern:-

*Because of the separation, multiple views and controllers can interface with the same model. Even new types of views and controllers that never existed before can interface with a model without forcing a change in the model design.

*You can distribute development effort to some extent, so that implementation changes in one part of the Web application do not require changes to another. The developers responsible for writing the business logic can work independently of the developers responsible for the flow of control, and Web-page designers can work independently of the developers.

*You can more easily prototype your work. You might do as follows, for example:

  1. Create a prototype Web application that accesses several workstation-based programs.
  2. Change the application in response to user feedback.
  3. Implement the production-level programs on the same or other platforms.

Outside of the work you do on the programs themselves, your only adjustments are to configuration files or name-server content, not to other source code.

*You can more easily migrate legacy(Transforming from one technology to other) programs, because the view is separate from the model and the control and can be tailored to platform and user category.

*You can maintain an environment that comprises different technologies across different locations.

*The MVC design has an organizational structure that better supports scalability (building bigger applications) and ease of modification and maintenance (due to the cleaner separation of tasks).

I hope this will help you understanding design pattern.

Thank You.

Categories: ASP.NET MVC, Introduction
  1. June 24, 2011 at 2:55 pm

    Its really cool and easy to understand !!!!

  2. Atul
    June 26, 2011 at 9:15 am

    it was very helpful

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: