JavaRanch: Latest posts for the topic "coupling and cohesion in java"

coupling and cohesion in java

jeya prabha — Mon, Sep 1 2008 23:52:00 MDT

what is coupling and cohesion in java1.5
what is loose coupling,tight coupling?
please give me some sites for good materials for this.

coupling and cohesion in java

Jesper Young — Tue, Sep 2 2008 01:10:00 MDT

jeyaprabha, you have been warned to change your display name to make it conform to the JavaRanch naming policy multiple times, and yet you have not changed it.

Please read the naming policy carefully and change your display name. Specifically, your display name must consist of a first and a second name. Not just a first name.

If you do not change your display name immediately, your account will be locked.

coupling and cohesion in java

jeya prabha — Tue, Sep 2 2008 04:05:00 MDT

i have changed my display name

coupling and cohesion in java

Campbell Ritchie — Tue, Sep 2 2008 04:31:00 MDT

Originally posted by jeya prabha:
i have changed my display name

Thank you.

Now you can have an answer.

Cohesion means that the whole of a class sticks together (well, roughly). A class should be responsible for itself, should do one thing and as far as possible do everything for that one thing. A Car class should remember its make, colour, speed. It is responsible for changing speed; the speedUp() and slowDown() methods should be in the Car class; no other class should make your Car go faster or slower.

Cohesion is (to quote Sellars and Yeatman) A Good Thing.

Coupling means that one class gets at the implementation of another class.

Driver campbell = new Driver();
Car ford = new Car("Ford", "red");
 . . .
public class Driver
{
   Car myCar;
. . .
   public void goFaster(int speed)
   {
      myCar.speed += speed;
   }
. . .
}

The Car class has allowed access to its speed field and the Driver class changes its value directly. This means other classes gain access to the implementation of the Car class; any changes to that implementation will "break" the Driver class. This is "tight coupling" and tight coupling is A Bad Thing, because any changes to one class can mean that other classes would have to be altered too.
To avoid tight coupling

All classes should have as small a public interface as possible.

All non-constant fields should have private access.

Any alterations to the values of fields should be via method calls.

coupling and cohesion in java

camilo lopes — Tue, Sep 2 2008 06:12:00 MDT

simple,

coupling = is the how much your class know about other class. let say that you have one friend and you know a lot about this friend as: What she do in the bathroom?
but this you shoudn't know.
The same happen with the class, when one know a lot about other.

cohesion = is when you have one class focus, one objective. for exaple:

class AddCustomers{}

this is one class com high cohesion. because she has one focus. one class with low cohesion is when she does several somethinds example:
- add customers
- print list of the customers
- connect BD
all in one unique class this is one class com low cohesion.