CSC/ECE 517 Summer 2008/wiki3 4 bk: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
=Cohesion Explained= | |||
Cohesion is an element of object-oriented programming related to how well or how poorly a component of a program is compartmentalized. High cohesion is the preferable state in which a component's implementation and "awareness" is contained within the respective component. Low cohesion is the undesirable state in which the implementation crosses over the boundaries of the component into the rest of the program. In short, the component [http://en.wikipedia.org/wiki/Encapsulation_%28classes_-_computers%29 encapsulates] its implementation. | Cohesion is an element of object-oriented programming related to how well or how poorly a component of a program is compartmentalized. High cohesion is the preferable state in which a component's implementation and "awareness" is contained within the respective component. Low cohesion is the undesirable state in which the implementation crosses over the boundaries of the component into the rest of the program. In short, the component [http://en.wikipedia.org/wiki/Encapsulation_%28classes_-_computers%29 encapsulates] its implementation. | ||
Revision as of 23:20, 23 July 2008
Cohesion Explained
Cohesion is an element of object-oriented programming related to how well or how poorly a component of a program is compartmentalized. High cohesion is the preferable state in which a component's implementation and "awareness" is contained within the respective component. Low cohesion is the undesirable state in which the implementation crosses over the boundaries of the component into the rest of the program. In short, the component encapsulates its implementation.