Object Oriented Software Engineering   View all facts   Glossary   Help
subject > criterion > quality > software quality > coupling > import coupling
Next couplinginclusion coupling    Upcoupling    Previous couplingexternal coupling   

import coupling
subjectfact 
import couplingcan be reduced by not importing packages or classes which you do not need2001-08-30 14:55:54.0
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 subsystem2001-08-30 14:55:54.0
has definition A form of coupling in which one component declares that it imports (makes use of the definitions in) another2001-08-30 14:55:54.0
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 change2001-08-30 14:55:54.0
is a weaker form of inclusion coupling2001-08-30 14:55:54.0
is a subtopic of 9.2 - Principles Leading to Good Design2001-08-30 14:55:54.0
is used by Java2001-08-30 14:55:54.0
is a kind of couplingstatus: put as a sub of inclusion coupling?, 2001-08-30 14:55:54.0
couplingimplies that if you want to reuse one component, you will also have to import all the ones with which it is coupled2001-08-30 14:55:07.0