Best Answer: Informally, cohesion is generally considered a good thing, creating a software component that combines related functionality into a single unit. The goal, which is one of the core principle of object-oriented programming, is to create a component that encapsulates implementation details and presents a simple external interface. Coupling (or more specifically, unnecessary coupling) is generally considered a bad thing: having software components be dependent upon specific details of other components. Keeping external interfaces simple and general will help reduce coupling to a minimum. The best way to understand Cohesion and Coupling is: Classes and objects as we use in C++ & Java programming signifies cohesion i.e. The degree to which the responsibilities of a single component form a meaningful unit.[OBJECT] Functions as we use in C++ & Java programming signifies coupling i.e.

Relationship between software components.[FUNCTIONS/METHODS] The above just gives a method in which cohesion and coupling in a software is understood. There are more things also that are added into this context. Basically 'coupling' and 'cohesion' are part of maintenance. 'coupling' means to make intralinking between different components within a system. The highly coupled system is considered as not good because it is hard to make changes in a system which is strongly coupled.

Presentation OfSoftware engineering Topic: Cohesion & Coupling Jagnesh Chawla(jagneshchawla@gmail. Trillian Vst Serial here. com). Umar Sharif Video Clip Download there.

Where as 'cohesion' means to have intra linking between sub components or modules within a component. How strong is the bonding or linkages between sub modules or sub components of a large component. Are they working indepedently or are working as single unit. Cohesion should be high, because if cohesion will be weak, then the changes in the software system will be difficult. Coupling in a software system must be low because when you need to make any changes in a component, it will not effect other component and maintaince will be possible. Pls note that in SDLC, software spends most of the time in maintaince phase, as the software enters the operation, after delivery and acceptance, you need to keep its maintaince in view and this is only possible if coupling is low and cohesion is high.