Separates concerns to improve modularity, maintainability, and scalability of software applications.

Communicates the architectural structure and responsibilities of components in a software system.

When designing or refactoring a software application that requires separation of concerns, especially UI-heavy applications.

Used in web, desktop, and mobile application development; common in frameworks like Ruby on Rails, ASP.NET MVC, Angular, iOS UIKit.

Tripartite separation of concerns into Model, View, and Controller components.

Model (data and business logic), View (presentation/UI), Controller (input handling and flow control).

[Model], [View], [Controller]

• framework
• architecture
• pattern
• MVC
• Rails
• Django
• ASP.NET

• Model-View-Presenter (MVP)
• Model-View-ViewModel (MVVM)

Overloading the Controller with business logic, tightly coupling View and Model, neglecting proper separation of concerns.

Model-View-Presenter (MVP), Model-View-ViewModel (MVVM), Hierarchical Model-View-Controller (HMVC), Model-View-Intent (MVI)

Confusing MVC with MVP or MVVM can lead to incorrect responsibility assignments.

• Model-View-Controller
• Model-View-Presenter
• Model-View-ViewModel

Emphasizes separation of concerns but allows flexibility in how tightly components are coupled.

Communicates a clear architectural intent, guiding team structure and code organization.

Think of a triad: Model (data), View (UI), Controller (input).

Implementations may vary in how strictly they separate concerns, so be mindful of coupling between View and Model.

Model-View-ViewModel (MVVM)