import coupling | can be reduced by not importing packages or classes which you do not need | ![2001-08-30 14:55:54.0](facet.gif) |
can cause a system to suddenly fail if a new item is added to an imported file, and this new item has the same name as something you have already defined in your subsystem | ![2001-08-30 14:55:54.0](facet.gif) |
has definition A form of coupling in which one component declares that it imports (makes use of the definitions in) another | ![2001-08-30 14:55:54.0](facet.gif) |
has disadvantage if the imported component changes something on which the importer relies, or adds something that raises a conflict with something in the importer, then the importer must change | ![2001-08-30 14:55:54.0](facet.gif) |
is a weaker form of inclusion coupling | ![2001-08-30 14:55:54.0](facet.gif) |
is a subtopic of 9.2 - Principles Leading to Good Design | ![2001-08-30 14:55:54.0](facet.gif) |
is used by Java | ![2001-08-30 14:55:54.0](facet.gif) |
is a kind of coupling | ![status: put as a sub of inclusion coupling?, 2001-08-30 14:55:54.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) |