Model–view–viewmodel

Model–view–viewmodel (MVVM) is an <a href="/facts/Architectural_pattern/GnN0z06K">architectural pattern</a> in computer software that facilitates the <a href="/facts/Separation_of_concerns/Tx8jawNT">separation</a> of the development of a <a href="/facts/Graphical_user_interface/wBlQFWDP">graphical user interface</a> (GUI; the view)—be it via a <a href="/facts/Markup_language/WwhlNVIu">markup language</a> or GUI code—from the development of the <a href="/facts/Business_logic/D0eEdM3t">business logic</a> or <a href="/facts/Front_and_back_ends/QVUfH8gu">back-end</a> logic (the model) such that the view is not dependent upon any specific model platform.
The viewmodel of MVVM is a value converter, meaning it is responsible for exposing (converting) the <a href="/facts/Data_object/eX99dtAw">data objects</a> from the model in such a way they can be easily managed and presented. In this respect, the viewmodel is more model than view, and handles most (if not all) of the view's display logic. The viewmodel may implement a <a href="/facts/Mediator_pattern/E9ncaBAy">mediator pattern</a>, organizing access to the back-end logic around the set of <a href="/facts/Use_case/8pNHjsIr">use cases</a> supported by the view.
MVVM is a variation of <a href="/facts/Martin_Fowler_(software_engineer)/l8k3NRI1">Martin Fowler</a>'s Presentation Model design pattern. It was invented by <a href="/facts/Microsoft/nGIDDXdx">Microsoft</a> architects Ken Cooper and Ted Peters specifically to simplify <a href="/facts/Event-driven_programming/QlGL2Fu6">event-driven programming</a> of user interfaces. The pattern was incorporated into the <a href="/facts/Windows_Presentation_Foundation/KTs9FcFn">Windows Presentation Foundation (WPF)</a> (Microsoft's <a href="/facts/.NET_Framework/J6QDAUhP">.NET</a> graphics system) and <a href="/facts/Silverlight/SYKe8yL1">Silverlight</a>, WPF's Internet application derivative. John Gossman, a Microsoft WPF and Silverlight architect, announced MVVM on his blog in 2005.
Model–view–viewmodel is also referred to as model–view–binder, especially in implementations not involving the <a href="/facts/.NET/PDMQdfFu">.NET</a> platform. <a href="/facts/ZK_(framework)/BQk9xTAf">ZK</a>, a <a href="/facts/Web_application_framework/8f1CVHDX">web application framework</a> written in <a href="/facts/Java_(programming_language)/9ScgFyAL">Java</a>, and the <a href="/facts/JavaScript/XhhIIEsl">JavaScript</a> <a href="/facts/Library_(computing)/xRzL3P7q">library</a> <a href="/facts/KnockoutJS/Jdg4DfD5">KnockoutJS</a> use model–view–binder.

Model–view–viewmodel open-in-new

Model–view–viewmodel