software architecture Comparison Table

subject > pattern > software architecture

Next pattern: architectural pattern Up: pattern Previous pattern: multiplicity pattern

software architecture comparison table

Subject increases facilitate has definition separate reduce relate to is a subtopic of abbreviate as

distributed architecture reuse because it is often possible to find suitable frameworks on which to build good distributed systems divide and conquer since dividing the system into processes is a very strong way to divide the system up coupling since there is usually only one communication channel between distributed components although you have to watch out for control coupling 9.5 - Architectural Patterns

Model-View-Controller reuse because the view and controller normally make extensive use of reusable components for various kinds of UI controls divide-and-conquer because the three components can be independently designed A architectural pattern used to separate the functional layer of the system (the model) from two aspects of the user interface, the view and the controller the functional layer of the system (the model) from two aspects of the user interface, the view and the controller the coupling between the user interface layer and the rest of the system, as well as between different aspects of the UI itself the multi-layer architecture 9.5 - Architectural Patterns MVC

stable architecture An architecture that permits changes to a system to be made without the architecture having to change 9.4 - Software Architecture

Subject	increases	facilitate	has definition	separate	reduce	relate to	is a subtopic of	abbreviate as
distributed architecture	reuse because it is often possible to find suitable frameworks on which to build good distributed systems	divide and conquer since dividing the system into processes is a very strong way to divide the system up			coupling since there is usually only one communication channel between distributed components although you have to watch out for control coupling		9.5 - Architectural Patterns
Model-View-Controller	reuse because the view and controller normally make extensive use of reusable components for various kinds of UI controls	divide-and-conquer because the three components can be independently designed	A architectural pattern used to separate the functional layer of the system (the model) from two aspects of the user interface, the view and the controller	the functional layer of the system (the model) from two aspects of the user interface, the view and the controller	the coupling between the user interface layer and the rest of the system, as well as between different aspects of the UI itself	the multi-layer architecture	9.5 - Architectural Patterns	MVC
stable architecture			An architecture that permits changes to a system to be made without the architecture having to change				9.4 - Software Architecture

Next pattern: architectural pattern Up: pattern Previous pattern: multiplicity pattern