(public).sospep.subjects ~ view article ~ what-is-MVC?

<h1 style="text-align: center;">Model View Controller(MVC)</h1>
<h2>[WHAT]</h2>
<ol>
<li>]&nbsp;MVC is a software development design pattern.&nbsp;The&nbsp;acronym MVC represents the 3 components of the pattern, the&nbsp;Model, the View and the Controller. When you design an application using the MVC pattern you seperate/organize&nbsp;most of your code into these seperate components. The different&nbsp;components then interact with one another to deliver the application. One of the prinicples of the pattern, is that&nbsp;each of the individual components, should not have any reliance/dependancy on either of&nbsp;the other components - ex the view doesnt need to know about the model, the model doesnt need to know about the controller.</li>
</ol>
<h2>[WHY]</h2>
<ol>
<li><strong><span style="background-color: #00ff00;">] SEPERATION</span> of concerns -</strong></li>
<ol>
<li>] seperate the different layers of your code/application logic to make for a more maintainable project</li>
<li>+] the philosopy behind "seperation", change the logic, dont have to touch the views, change the view, dont have to touch the logic,</li>
<li>] remove data from business logic, remove logic from presentation</li>
</ol>
<li><strong><span style="background-color: #00ff00;">] DRY</span> promote code useablitiy(1) </strong></li>
<ol>
<li>] the same code components can be resused in multiple pages, even on multiple different projects</li>
</ol>
<li><strong><span style="background-color: #00ff00;">] TDD</span> testability </strong></li>
<ol>
<li>]&nbsp;</li>
</ol></ol>
<h2>[WHY NOT]</h2>
<ol>
<li>]&nbsp;there are other design patterns that may be better suited dependant upon your applications needs, these include ...</li>
<li>] OTHER SIMILAR PATTERNS - ] MVVM, ] MVP,</li>
<li>]&nbsp;OLDER PATTERNS - ] nteir architecture (presentation, business rules, data access, ...)</li>
<li>] NEWEST - ] PUB/SUB (meteor, flux) ....</li>
</ol>
<h2>[WHERE]</h2>
<ol>
<li>] web applications, desktop applications</li>
</ol>
<h2>[WHEN]</h2>
<ol>
<li>] 1976 - smalltalk origins,</li>
<li>] today - widely used,&nbsp;web development, many MVC frameworks</li>
</ol>
<h2>[EXAMPLE]</h2>
<ol>
<li><strong>]&nbsp;<span style="background-color: #00ff00;">model</span> - represents (all) data for the application,</strong></li>
<ol>
<li>] data access, is updated by controller,&nbsp;</li>
<li>] controller pulls data required for various views,&nbsp;</li>
<li>] controller passes that data to view,</li>
</ol>
<li><strong>] <span style="background-color: #00ff00;">view</span> - presentation -&nbsp;</strong></li>
<ol>
<li>] presents data/ui elements to the&nbsp;user,</li>
<li>] generated by controller,</li>
<li>] a view = thhe current set of data and ui elements that are being presented</li>
<li>] template -</li>
<li>] view engine -</li>
</ol>
<li><strong>] <span style="background-color: #00ff00;">controller</span> -&nbsp;</strong></li>
<ol>
<li>] contains actions(methods) that update the model,</li>
<li>] contains actions that update the view</li>
</ol>
<li>] ? view event -&gt; controller</li>
<li>] controller event -&gt;</li>
<li>] data from business logic&nbsp;</li>
</ol>
<h2>[HOW-TO]</h2>
<ol>
<li>]&nbsp;</li>
</ol>
<h2>[REFERENCE]</h2>
<ol>
<li>]</li>
</ol>
<p>&nbsp;</p>
<p>&nbsp;</p>
<h1 style="text-align: center;">&nbsp;</h1>

~ view article ~ Chapter] ch-001-introduction FROM [ Book] asp.net IN [ libraries] technology-developer-www