Coupling
A measure of how much one subsystem's behavior depends on the internal implementation details of another subsystem, rather than on a stable, defined interface. Tight coupling means a change in one subsystem is likely to unpredictably affect another; loose coupling means subsystems can change independently as long as their shared interface contract holds.
Defined in 2 GAGE programs, which carry 3 distinct definitions of it. The wording above is taught in Engineering Judgment and Professional Formation.
How each discipline defines it
The same term does different work depending on who is using it. These are the definitions as each program teaches them, unedited.
A measure of how much one subsystem's behavior depends on the internal implementation details of another subsystem, rather than on a stable, defined interface. Tight coupling means a change in one subsystem is likely to unpredictably affect another; loose coupling means subsystems can change independently as long as their shared interface contract holds.
The degree to which two pieces of code depend on each other's internal details. High coupling means a change in one requires a change in the other. Good package structure minimizes unnecessary coupling between packages while keeping related code together.
The degree to which two software modules depend on each other's internals, such that changing one requires changing the other. Low coupling is a primary design goal because it localizes the effect of every change.
Terms it appears with
Not an alphabetical neighbourhood: these are the terms taught in the same lessons, ranked by how often they appear together.