![]() |
subject > pattern |
![]() ![]() | |||||||||||||||||
pattern comparison table |
Subject | decide | is a synonym of | is a subtopic of | have antipatterns | have name | write using | have problem | have context | understand by | constrain | has definition | illustrate using | have related patterns | allow | have forces | see also | have references |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
architectural pattern | architectural style | 9.5 - Architectural Patterns | A pattern used in software architecture | you to design flexible systems using components that are as independent of each other as possible | |||||||||||||
design pattern | 6.1 - Introduction to Patterns | zero or more antipatterns - solutions that are inferior or do not work in this context with the reason for their rejection | a narrative writing style | a sentence or two explaining the main difficulty being tackled | a context | A pattern useful for the design of software | a simple diagram | zero or more related design patterns | one or more forces | one or more references which indicate who developed or inspired a pattern | |||||||
multiplicity pattern | 5.3 - Associations and Multiplicity | ||||||||||||||||
software architecture | early in the design process, although it will continue to mature as iterative development proceeds | 9.4 - Software Architecture | software engineers | the overall efficiency, reusability and maintainability of the system | software architecture^3 |
Next subject: person or group Up: subject Previous subject: paradigm