| written 6.9 years ago by | • modified 6.9 years ago |
Subject: Object Oriented Modeling and Design
Difficulty: Medium
Marks: 4 Marks
| written 6.9 years ago by | • modified 6.9 years ago |
Subject: Object Oriented Modeling and Design
Difficulty: Medium
Marks: 4 Marks
| written 6.9 years ago by |
Relationships in the UML:
1. Dependency: A dependency relationship specifies that a change in the specification of one thing may affect another thing that uses it. Graphically, a dependency is rendered as a dashed line, directed to the thing that is dependent on.
Notation:

2. Association: An association is a structural relationship, specifying that objects of one thing are connected to objects of another. When an association connects two classes you can navigate from one object of one class to an object of another class and vice versa. Graphically an association is represented as a solid line connecting more than one class.
Notation:

3. Generalization: It is a relationship between a general thing (called the super class or parent) and a more specific kind of that thing (called the subclass or child). With generalization relationship a child can inherit all the structure and behavior of parent. A child may add new structure or behavior or it may modify the behavior of the parent. Graphically it is represented as a solid line with hollow triangle placed near to the super class.
Notation:

4. Realization: A realization is a schematic relationship between classifiers in which one classifier specifies a contract that another classifier guarantees to carry out. Graphically a realization is represented as dashed directed line with the hollow triangle pointing to the classifier that specifies the contract.
Notation:

5. Aggregation: Aggregation is a part whole relationship where an aggregate class connects multiple subclasses which are part of aggregate class. It is represented with a diamond towards aggregate class.
Notation:
