Hi ranchers,
here we don't have only tight coupling but also bad encapsulation.
The adjusted/salesRate variables in the second class are public. So the first class can access it directly (first T).
What is really bad (tight) coupling, is that the classes interact too closely. The second class sets its salesRate variable using the doColorado method of the first class where the same salesRate variable is used.
Generally the classes should know of each other as little as possible, therefore all this access modifiers.
Something else, Vishwa nath.K, there is a certain policy about user names in the
Java Ranch, see:
http://www.javaranch.com/name.jsp On this page is also a link, where you can change your user name, so please do this.
Yours,
Bu.