Please enable JavaScript.
Coggle requires JavaScript to display documents.
Chapter 9 Interaction-oriented Architecture - Coggle Diagram
Chapter 9
Interaction-oriented Architecture
PAC
https://www.tutorialspoint.com/software_architecture_design/interaction_oriented_architecture.htm
developed
from MVC to support the application requirement of multiple agents in addition to interactive requirements.
Model View Controller
MVC-I
https://phamvantai2016.wordpress.com/2018/02/08/tim-hieu-ve-mo-hinh-mvc-so-sanh-mvc1-va-mvc2/
MVC-II
overview
Key Idea
View: deal with graphic representation
Controller: contains the interface between model and view
Model: model of application’s logic
Concept for model:
Model manages
behavior and data of the application domain.
model responds
requests for information about its state (usually from the view)
View renders
ypically a user interface element.
model into a form suitable for interaction
Multiple views
can exist for a single model for different purposes.
Benefits
Very effective for developments (team working by different professionals)
Easy to plug in new or change interface views
Limitations
Does not fit agent-oriented application such as robotics applications
Multiple pairs of controllers and views make data model change expensive
The division between the View and the Controller is not very clear in some cases
Difference of MVC and PAC
They differ in their flow of control and organization.
PAC is an agent based hierarchical architecture
whereas MVC does not have any clear hierarchical architecture. All three modules are connected together.