type use coupling | can be reduced by - ensuring that a class is only type-coupled to classes in a relatively small number of packages
- declaring the type of a variable to be the most general possible class or interface that contains the required operations
| ![2001-08-30 14:58:06.0](facet.gif) |
cannot be avoided | ![2001-08-30 14:58:06.0](facet.gif) |
has definition A form of coupling in which several components make use of the same globally-defined data type | ![2001-08-30 14:58:06.0](facet.gif) |
has disadvantage if the type definition changes, then the users of the type may well have to change. | ![2001-08-30 14:58:06.0](facet.gif) |
is less problematic than common coupling | ![2001-08-30 14:58:06.0](facet.gif) |
is similar to common coupling, but instead of data being shared, only data types are shared | ![2001-08-30 14:58:06.0](facet.gif) |
is a subtopic of 9.2 - Principles Leading to Good Design | ![2001-08-30 14:58:06.0](facet.gif) |
is a kind of coupling | ![2001-08-30 14:58:06.0](facet.gif) |
occurs when a class declares a variable as having another class as its type | ![2001-08-30 14:58:06.0](facet.gif) |
occurs in typed languages such as Java | ![2001-08-30 14:58:06.0](facet.gif) |
coupling | implies that if you want to reuse one component, you will also have to import all the ones with which it is coupled | ![2001-08-30 14:55:07.0](facet.gif) |