Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Coupling (computer programming)
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
{{short description|Degree of interdependence between software modules}} In [[software engineering]], '''coupling''' is the degree of interdependence between software [[Modular programming|modules]], a measure of how closely connected two routines or modules are,<ref name="ISO_24765"/> and the strength of the relationships between modules.<ref name="ISOIECTR19759_2005"/> Coupling is not binary but multi-dimensional. <ref name=":0">{{Cite book |last=Hohpe |first=Gregor |title=Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions |publisher=Addison-Wesley Professional |isbn=978-0321200686}}</ref> [[File:CouplingVsCohesion.svg|thumb|Coupling and [[cohesion (computer science)|cohesion]]]] Coupling is usually contrasted with [[cohesion (computer science)|cohesion]]. [[Loose coupling|Low coupling]] often correlates with high cohesion, and vice versa. Low coupling is often thought to be a sign of a well-structured [[computer system]] and a good design, and when combined with high cohesion, supports the general goals of high [[computer programming#Readability of source code|readability]] and [[maintainability]].{{Citation needed|date=October 2013}}
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)