Thanks to visit codestin.com
Credit goes to www.scribd.com

Scribd
Upload
154 views12 pages

MVVM in Software Development

The document discusses the Model-View-ViewModel (MVVM) pattern for software development. MVVM separates an application into three components: the model, which contains the business logic; the view, which defines the visual UI; and the view model, which connects the model and view and handles the user experience. Using MVVM allows for improved testability, maintainability, and ability to evolve the user experience compared to traditional approaches that more tightly couple the UI and behavior. The document demonstrates building a simple mapping application first with a traditional approach and then using MVVM.

Uploaded by

Imasiku Mombotwa
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
154 views12 pages

MVVM in Software Development

The document discusses the Model-View-ViewModel (MVVM) pattern for software development. MVVM separates an application into three components: the model, which contains the business logic; the view, which defines the visual UI; and the view model, which connects the model and view and handles the user experience. Using MVVM allows for improved testability, maintainability, and ability to evolve the user experience compared to traditional approaches that more tightly couple the UI and behavior. The document demonstrates building a simple mapping application first with a traditional approach and then using MVVM.

Uploaded by

Imasiku Mombotwa
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 12

Software Development and Design Using MVVM

Jeff Jackson
[email protected] @jeffjax

Overview

Why do we need MVVM? What is MVVM? Easy on slides, heavy on code MVVM in practice Questions Technologies
-

WPF, Silverlight, Windows Phone, WinRT (Metro)

Traditional WPF Approach

Resembles WinForms or VB Name all the UI controls Implement handlers for control events in codebehind Write code to populate the named controls

Demo Build a Simple Mapping App

Traditional Approach - Drawbacks

Can it be tested? Can it be maintained? Can the UX design evolve (Blendability)? Tightly coupled UI implementation (presentation + behavior)

User Interface

Model

Introducing the MVVM Pattern

Separate the UI into two components


Model the business logic of the application View the visual, what you see ViewModel drives the user experience, supports the view

Commands

View
DataBinding

ViewModel

Model

Demo Simple Mapping App Revisited

MVVM Implementation

ViewModel implements INotifyPropertyChanged View binds to properties on the ViewModel View executes methods on the ViewModel (Commanding) View and ViewModel are connected, usually through the Views DataContext

MVVM Advantages

Maintainability Testability Designability Decomposition

MVVM Organizes the Team

UX Designer

Developer

View

ViewModel

Model

Graphic Designer

Test Engineer

Questions?

You might also like