Editing Coupling (computer programming) (section)

=== Object-oriented programming ===
;{{anchor|Subclass coupling}}Subclass coupling: Describes the relationship between a child and its parent. The child is connected to its parent, but the parent is not connected to the child.

;{{anchor|Temporal coupling}}Temporal coupling: It is when two actions are bundled together into one module just because they happen to occur at the same time.

In recent work various other coupling concepts have been investigated and used as indicators for different modularization principles used in practice.<ref name="Beck_2011"/>

==== Dynamic coupling ====
<!-- Section title used in redirects -->
The goal of defining and measuring this type of coupling is to provide a run-time evaluation of a software system. It has been argued that static coupling metrics lose precision when dealing with an intensive use of dynamic binding or inheritance.<ref name="Arisholm_2004"/> In the attempt to solve this issue, dynamic coupling measures have been taken into account.

==== Semantic coupling ====
<!-- Section title used in redirects -->
This kind of a coupling metric considers the conceptual similarities between software entities using, for example, comments and identifiers and relying on techniques such as [[latent semantic indexing]] (LSI).

==== Logical coupling ====
<!-- Section title used in redirects -->
{{anchor|evolutionary coupling|Change coupling}}Logical coupling (or evolutionary coupling or change coupling) analysis exploits the release history of a software system to find change patterns among modules or classes: e.g., entities that are likely to be changed together or sequences of changes (a change in a class A is always followed by a change in a class B).