Dive into the MVC design pattern in just 1 hour! Learn the basics of Model-View-Controller and get ready to build awesome applications.
In this chill course, you'll get the hang of the MVC pattern super fast! It's easy-breezy and all about making design patterns less daunting.
Learn in an easy way the MVC pattern in just 1 hour. All you need to start learning about the MVC frameworks.
You will learn about the famous MVC design pattern which stands for Model-View-Controller. This pattern is widely used in software engineering and many people talk about it, but few people know how to use it properly. You will learn, in an easy way, the MVC pattern in just 1 hour !
Many programmers still develop software systems without following any pattern or architecture. You will see that the MVC pattern isolates the business logic from the user interface, and makes it easier to manage complexity of application through the separation of concerns.
Several commercial and non-commercial web application frameworks have been created that enforce this pattern, for example: ASP.NET MVC, Apache Struts, Spring MVC, Cake PHP, and many more. Therefore it is very important that you understand the MVC pattern before working with any framework that follows this architecture.
This course was created to be fast, objective and easy to understand. It is not tiresome for students like most of the courses about design patterns.
Get started to learn MVC design pattern today!
All videos are in English;
All videos contain English subtitles;
All source code utilized in this course is available to download.
Understand the MVC (Model-View-Controller) pattern.
Create your own applications using the MVC pattern.
Get the basic knowledge to work with frameworks based on MVC architecture, for example: ASPNET MVC, Apache Struts, Spring MVC, Cake PHP among others.
2 Lectures
7 Lectures
7 Lectures
1 Lectures
Experience:Director at Ocram Information Systems since 2006.University Professor of Systems Analysis and Design since 2011.Effective Member of Brazilian Computer Society since 2008.Professional Member of Association for Computing Machinery since 2014.IEEE Membership since 2014.Skills:Computer Science, Teaching, Software Engineering, UML, Programming, Java programming language, Design Patterns
Having received a diploma in Motor Vehicle Studies at Cambridge Regional College (1994-98) and worked as a automotive technician up until 2001, my career path has somewhat changed over the years.I was recruited by a Civil Engineering company where I worked with oil, fuel, and waste management systems before moving into the field of Construction, working as a hands on...
This course is great for a quick introduction to MVC
The price is too high for such small course
el dibuja y hay veces que no se comprende lo que dibuja
good and clear
Great course! Easy and fast to learn
Muito bom. Objetivo e muito claro.
You teach as if there was only 1 type of MVC pattern. The one you teach here, is not the most common. Here the controller is just a Mediator. But, in the most common MVC pattern :
Controller is responsible for handling View events (click, ...) OK, BUT also is responsible for registering the View as an Observer of the Model(which is indeed also an Observable), indeed the Model "only" knows Observers of itself. So this is not the controller that updates the View's (displayed) Business Data, but the View itself, as an Observer of the Model, that will be notified by the Model, via the View update method, in order to auto-update its IHM Data field(s). So in this case, the notion of Observer pattern is very important (as it isolates View from Model), and also the notion of Strategy pattern has to be pointed, while it is about choosing a specific Concrete Controller to handle the Views actions in a certain way, and also updates its look (but not its (displayed) business data). Also, there is a MVC version where the View knows its Controller, in order to send events to it. And finally, you missed a very important thing : MVC is based on Design Patterns, and you should have introduce Abstractions in here, Interfaces for example, in order that the classes that have to communicate can do it, just via certain authorized methods that are then the only thing that they know about each other ! When i began studying MVC i thought like you, that the MVC with Controller as Mediator was THE ONE. So, it would have been great to mention that the MVC pattern you teach here is not the only existing one, and the worst : you even said the contrary of that ! I nearly put 2 stars, but i want to encourage. May i would even say, that the pattern you teached is just a specific case of the Mediator Design Pattern.
Instructor presents the core concept (the MVC pattern) very well, and in straight forward way, along with a demo use case. It would have been nice to get a bit further in depth, for instance, by comparing and contrasting MVC with other development patterns. It would also be interesting to see an edge case where MVC would not be a good pattern choice, or perhaps, how to massage a different pattern into MVC and the advantages that could be gained this way. To restate, good intro.
Quick and to the point. Great coding examples. Quick response to questions.
Your email address will not be published. Required fields are marked *
Alex
It's a good basic course, not very in depth and the red writing for examples is a bit frustrating, but all in all a useful hour spent taking it in.