Difference between revisions of "Loose coupling"
From Wiki @ Karl Jones dot com
Karl Jones (Talk | contribs) (Created page with "In computing and systems design, loose coupling is the principle that each component has, or makes use of, little or no knowledge of the definitions of other separate...") |
Karl Jones (Talk | contribs) |
||
| Line 5: | Line 5: | ||
== See also == | == See also == | ||
| − | * [[Coupling (computer | + | * [[Coupling (computer programming)]] |
* [[Cohesion (computer science)]] | * [[Cohesion (computer science)]] | ||
* [[Connascence (computer programming)]] | * [[Connascence (computer programming)]] | ||
Latest revision as of 19:58, 3 September 2016
In computing and systems design, loose coupling is the principle that each component has, or makes use of, little or no knowledge of the definitions of other separate components.
Sub-areas include the coupling of classes, interfaces, data, and services.
See also
- Coupling (computer programming)
- Cohesion (computer science)
- Connascence (computer programming)
- XML
- Web Services
- ISO/IEC 11179 - metadata registry specification
- Data element
- Enterprise service bus
- Enterprise Messaging System
- Space-based architecture (SBA)
- Tightly Coupled Systems
- Interface (computer programming)
- UFCS
External links
- Loose coupling @ Wikipedia.org[[Category:Software engineering]
