Model-View-Controller Architecture

Last updated Nov 8, 2022 Edit Source

1. Tight coupling between UI and application logic
2. Observer Pattern: Need for UI to update when state changes
3. Strategy Pattern: Need for UI to support different functionalities depending on the user input

View:

• Manage how data is presented
• Observes the Model and updates their graphical representation Model:
• Provides the operations to register and unregister observers
• Implements a notify method to call observers update Controller:
• Captures input and passes them to the view and model

1. Support for simultaneous development
2. Support for multiple views with just 1 Model
3. High cohesion: grouping of related actions
4. Low coupling

1. Code navigability
2. Maintaining multi-artefact consistency: decomposition of features results in scattering