MVC, to my knowledge, was created for Desktop Application but the original scoped was limited to one widget. For example: There is one widget (let's call it a

MVC, to my knowledge, was created for Desktop Application but the original scoped was limited to one widget. For example: There is one widget (let's call it a Table) that displays data. The breakdown is as follow: Model => Data View => Table Controller => Something that updates view based on changes in model (undefined originally) Even if it wasn't limited to one widget, it was limited to a one simple View of the app (the other popular example is to use the DocumentWidget and DocumentModel "real-life" sample). The original MVC was definitely not well-thought for rich desktop application PLUS automated testing with limited dependency to the Presentation layer (or view). I believe Java SWING library utilizes MVC model at the widget levels.