MVC Design Pattern, Vietnam Software Outsource

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

1 comments

Comments 1 - 1 of 1 previous next Post a comment

Post a comment
Embed Video
Edit your comment Cancel

Favorites, Groups & Events

MVC Design Pattern, Vietnam Software Outsource - Presentation Transcript

  1. MVC DESIGN PATTERN © 2007 TUVINHSOFT 1a-LT/TL/TUVINHSOFT Authors: Nguyen Huu Dung Version: 1.0 Last Updated: 18-Aug-2008 Instructor: Ta Duc Phuong
  2. MVC PATTERN INTRODUCTION
    • Model-View-Controller ( MVC ) is an architectural pattern used in software engineering.
    • The First Pattern was first described in 1979 by Trygve Reenskaug.
  3. INTRODUCE MVC PATTERN
    • Model View Controller MVC is a time tested method of separating the user interface (UI) of an application from its Domain Logic.
    • The primary goal of MVC is to isolate UI changes and prevent them from requiring changes to the Domain Logic of the application.
    • The primary reason for this division is that the user interface and Domain Logic have different drivers for change and different rates of change. By making this separation, you can change the UI without touching the Domain Logic and vice versa.
  4. INTRODUCE MVC PATTERN
    • MVC PATTERN contains:
    • 4 main classes :
    • - FILE.CONTROLLERS
    • - FILE.VIEWS
    • - FILE.MODELS
    • - FILE.SQLS
    • 2 library classes
    • - FILE.SKINS
    • - FILE.INCLUDE
  5. MVC PATTERN
  6. CLASS CONTROLLERS
    • Controller class control models class and views class.
    • In MVC, The controller is not a Mediator between the view and the model. The controller does not sit in between the model and the view. Both the controller and the view have equal opportunity to access the model. The controller does not copy data values from the model to the view, although it may place values in the model and tell the view that the model has changed.
  7. CLASS VIEWS
    • Class Views renders the model into a form suitable for interaction, typically a user interface element. Multiple views can exist for a single model for different purposes.
  8. CLASS MODELS
    • The goal of MVC is to make the model independent of the view and controller which together form the user interface of the application.
    • The Model class representation of the information that the application operates.
    • The Model class control the sqls class.
  9. CLASS SQLS
    • Class SQLS interact with the database through queries sentense.
  10. LIBRARY CLASS
    • “ File skins” contain many template which class View uses.
    • “ File include” may contain classes such as js, ajax,..etc.
  11. Overview
    • MVC is often seen in web applications, where the view is the actual HTML page, and the controller is the code that gathers dynamic data and generates the content within the HTML. Finally, the model is represented by the actual content, usually stored in a database or XML files.
    • By decoupling models and views, MVC helps to reduce the complexity in architectural design, and to increase flexibility and reuse.

+ Phuong VyPhuong Vy, 2 years ago

custom

1044 views, 0 favs, 1 embeds more stats

Your first choice for Software Outsourcing to Vietn more

More info about this document

© All Rights Reserved

Go to text version

  • Total Views 1044
    • 1021 on SlideShare
    • 23 from embeds
  • Comments 1
  • Favorites 0
  • Downloads 33
Most viewed embeds
  • 23 views on http://blog.tuvinh.com

more

All embeds
  • 23 views on http://blog.tuvinh.com

less

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

Cancel
File a copyright complaint
Having problems? Go to our helpdesk?

Categories