Skip to main content

UML - Association, Aggregation, Composition, Generalization, Specialization, Realization and Dependency


Association

Association is a simple relationship between two classes.

For example

A relationship between Professor Class and Student class is known as Association.
Both Classes can exist without each other, so Professor and Student are two independent classes. In this kind of relationships there will not be any owner class. Both classes have their own life cycle.

UML Notation:  

Aggregation

Aggregation is a special type of Association. It is known as “Has-A” relationship.

For example

A Department class can contain Professor Class. Here Department class is owner class. Here in this relationship even after deleting Department class, Professor Class can exits.

UML Notation:





Composition

Composition is a special type of Aggregation. It is known as “Is-A” relationship.

For example

A University Class has many Department class. Here University and Department objects are dependent on each other. If we delete University class then Department class don’t exits. Here University class is an owner class.


UML Notation:

Generalization

Generalization is the process of extracting shared characteristics from two or more classes, and combining them into a generalized superclass. Shared characteristics can be attributes, associations, or methods.

Generalization is a relationship between a Parent and its Derived class. It is nothing but inheritance.

UML Notation:




Specialization

Specialization means creating new subclasses from an existing class. If it turns out that certain attributes, associations, or methods only apply to some of the objects of the class, a subclass can be created.

Realization

Realization is a relationship between the blueprint class (Interface) and a class containing its respective implementation details.

UML Notation:




Dependency

Change in structure of a class affects other classes then there is a dependency between those classes.

UML Notation:

Comments

  1. KrrisshhhnaaFebruary 26, 2015 at 1:05 AM

    Best, Excellent, Outstanding Performance ....

    Thank you ......

    ...
    ..
    .

    ReplyDelete

Post a Comment

Popular posts from this blog

C# Generic Factory

Implement Factory pattern using generics     public interface IDoWork   {       string DoWork();   }     Declare an Interface first by abstracting the common  functionality    Here I am taking the example of DoWork     public class Manager : IDoWork   {     public string DoWork()     {         return "Manager Manages School" ;     }   }     Implement the IDoWork in concrete classes as shown      public class Teacher : IDoWork     {         public string DoWork()         {             return "Teacher teaches student in school" ;         ...
7 comments
Read more

SSIS package - set oledb connections at runtime

SSIS oledb connection manager does't allow user to connect to different oledb servers. If we store oledb connection sting in Config file then it will accepts server name, InitialCatalog and username. But it wont accept password. The is because oledb connection manager has not exposed the oledb password property. To over come this problem we have to override the OLEDB connection manager itself. So that it accepts connections to different oledb servers. Public Sub Main() Dim vars As Variables Dim oledbConnectionManager As ConnectionManager oledbConnectionManager = Dts.Connections("<oledb connection name>") ' ADDED TO MAKE oledb CONNECTION STRING DYNAMIC Dim oServerName As String Dim oUserName As String Dim oInitialCatalog As String Dim oPassword As String Dts.VariableDispenser.LockOneForWrite("oServerName", vars) oServerName = vars("oServerName").Value.ToString().Trim() vars.Unlock() Dts.VariableDispenser.LockOneForWrite("oInitia...
Post a Comment
Read more