I'm actually struggling to come up with better definitions. These
terms were possibly introduced by Erich Gamma et al. (the "Gang of
Four") in "Design Patterns: Elements of Reusable Object-Oriented
Software".
Tight coupling -- This means there are many interdependencies (direct
and indirect) between different software components. think of it as
big interfaces with high fan-in.
Poor cohesion - This means that the job a particular component does
is poorly defined or that a component has many responsibilities that
are not clearly related. (Could this be big implementations with high
fan-out?)
===
Gregory Woodhouse
[EMAIL PROTECTED]
"The policy of being too cautious is
the greatest risk of all."
--Jawaharlal Nehru
On Jul 12, 2005, at 12:06 PM, James Gray wrote:
I should have been more clear in my question. I am more interested
in what you mean by the terms "tight coupling" and "poor
cohesion". I am aware of most of these specific problems in Vista
(except for the the Lab one). I am becoming more and more aware of
the tangled mess in some of the RPC calls in the OR* namespace. I
assume that amounts to tight coupling. I doubt I would know what
poor or good cohesion was when I saw it. I do know when the code
is hard to read.
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
