Object Oriented Software Engineering   View all facts   Glossary   Help

subject > criterion > quality > software quality > coupling > tight coupling

tight coupling
subject			fact

tight coupling	causes a system to be hard to understand and change because changes in one place will require changes somewhere else. Requiring changes to be made in more than one place is problematic since it is time-consuming to find the different places that need changing, and it is likely that errors will be made A network of interdependencies makes it hard to see at a glance how some component works
	is a subtopic of 9.2 - Principles Leading to Good Design
	is a kind of coupling
coupling	implies that if you want to reuse one component, you will also have to import all the ones with which it is coupled
software quality	is hard to assess