Association versus Dependency
From CSSEMediaWiki
(Difference between revisions)
Erikaveiga (Talk | contribs) |
m (Reverted edits by Ebybymic (Talk); changed back to last version by Matthew Harward) |
||
| (3 intermediate revisions by 3 users not shown) | |||
| Line 3: | Line 3: | ||
Association by definition does not suggest a dependency. | Association by definition does not suggest a dependency. | ||
| + | |||
| + | |||
[[Image:Association.png]] | [[Image:Association.png]] | ||
| + | |||
| + | {{Nomenclature}} | ||
| + | |||
| + | [[Category: Nomenclature]] | ||
Latest revision as of 03:11, 25 November 2010
Dependency is defined as "Dependency exists between two elements if a Change in one may cause change to other." Quote from Fowler (Pg47) With classes, dependencies exists for various reasons: One Class sends a message to another;one class has another as part of its data;one class mentions another as parameter to an operation.
Association by definition does not suggest a dependency.
| Nomenclature | |
|---|---|
| Techniques: Abstraction | Aggregation versus Composition | Association versus Dependency | Coupling | Encapsulation | Information hiding | Inheritance | Multiple Inheritance | Overloading | Polymorphism
Features: Abstract class | Class versus Object | Component versus Module | Instance | Interface | Method | Package versus Namespace | Superclass | Subclass | |
