Object Oriented Software Engineering   View all facts   Glossary   Help

subject > criterion > quality > software quality > coupling > content coupling > content coupling in Java

content coupling in Java
subject			fact

content coupling in Java	can be avoided by Ensuring everybody follows the rule that says not to modify the instance variables of objects that are themselves stored in instance variables of another objects Using the immutable or read only interface design patterns Making all instance variables private, and provide accessing methods such as getVal, and setVal. If you do this, you then have confidence that the only places where the variable is accessed and modified are in these methods
	can occur when you directly modify an instance variable of an instance variable
	can occur whenever you modify a public instance variable in a way that designers did not intend
	is a subtopic of 9.2 - Principles Leading to Good Design
	is a kind of content coupling
content coupling	should be avoided since any modification of data should be easy to find and easy to understand
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