Session 3

In this Session we will be discussing class diagrams. We will just scratch the surface.
Class diagrams are very important element in the design of any software। They serve as a common mechanism to understand the elements and it's

structure along with it's relationship to other elements.
Also, understanding class diagrams will allow us to represent almost all the design patterns in a standard way.

Summary of 3rd Session - {UML - CLass Diagram}
In this session we learnt about UML class diagrams and some basic notation that goes along with class diagram.
We learnt about tags {} (those cute curly braces which adds meaning to members of class).
We talked about Stereotype. Stereotype can be used as an alias. These are represented by not so cute double angled braces.<<>>
For e.g. to represent an interface the following stereotype can be used.
<>.

We have reiterated the importance of loose coupling and high cohesion.

We have created yet another bag of knowledge i.e. "The UML Bag" and we have added the following in this bag
- Class diagram

Incorrect use of relationships are always dangerous and you have to be careful in dealing with them :).

We have slightly touched upon the following types of realtionships while drawing class diagrams
- Association
- Generalization
- Realization
- Dependency

We will cover these subtle things in the future sessions.

You comments/suggestions are welcome.