CPIT601
HW
Architectural Pattern Vs.
Architectural Style
• An Architectural Style is the application design at the highest level of abstraction;
• An Architectural Pattern is a way to implement an Architectural Style;
• An architectural style is a conceptual way of how the system will be created / will work. An
architectural pattern describes a solution for implementing a style at the level of subsystems
or modules and their relationships
MVC
• The Model-View-Controller (MVC) is an architectural pattern that separates an application into three main
logical components: the model, the view, and the controller. Each of these components are built to handle specific
development aspects of an application.
• The Model component corresponds to all the data-related logic that the user works with. This can represent either
the data that is being transferred between the View and Controller components or any other business logic-related
data. For example, a Customer object will retrieve the customer information from the database, manipulate it and
update it data back to the database or use it to render data.
• The View component is used for all the UI logic of the application. For example, the Customer view will include
all the UI components such as text boxes, dropdowns, etc. that the final user interacts with.
Examples of MVC
• The Model-View-Controller (MVC) is an architectural pattern that separates an application into three main
logical components: the model, the view, and the controller. Each of these components are built to handle specific
development aspects of an application.
• The Model component corresponds to all the data-related logic that the user works with. This can represent either
the data that is being transferred between the View and Controller components or any other business logic-related
data. For example, a Customer object will retrieve the customer information from the database, manipulate it and
update it data back to the database or use it to render data.
• The View component is used for all the UI logic of the application. For example, the Customer view will include
all the UI components such as text boxes, dropdowns, etc. that the final user interacts with.
