UML crib #2 – UML transformed to C# (1)

 

This article should contain, what generates Enterprise Architect, when you created UML design. It demostrates what means relations between classes. Generating of classes you can execute from menu Element->Source code engeneering ->Generate selected files. Another articles from this cathegory you can find here.

Association

  public class ClassA {
     public ClassA(){}
     ~ClassA(){}
     public virtual void Dispose(){}
   }//end ClassA

  public class ClassB {
     public ClassA m_ClassA;
     public ClassB(){}
     ~ClassB(){}
     public virtual void Dispose(){}
  }//end ClassB

 

 

Aggregation

public class ClassC {
   public ClassC(){}
   ~ClassC(){}
  public virtual void Dispose(){}
}//end ClassC

 

public class ClassD {
   public ClassC m_ClassC;
   public ClassD(){}
   ~ClassD(){}
   public virtual void Dispose(){}
}//end ClassD

 

 

Composition

public class ClassD
{
   public ClassC m_ClassC;
   public ClassD(){}
   ~ClassD(){}
   public virtual void Dispose(){}
}//end ClassD

 

public class ClassE
{
   public ClassE(){}
   ~ClassE(){}
  public virtual void Dispose(){}
}//end ClassE

 

Nested class

  public class ClassG { 
      public class ClassH {
        public ClassH(){}
        ~ClassH(){}
       public virtual void Dispose(){}
      }//end ClassH

  public ClassG(){}
  ~ClassG(){}
  public virtual void Dispose(){}
}//end ClassG

 

 

 

Generalization

Inheriting classes.ClassK iherits from ClassJ.

public class ClassJ {
  public ClassJ(){}
  ~ClassJ(){}
  public virtual void Dispose(){}
}//end ClassJ

 

public class ClassK : ClassJ {
  public ClassK(){}
  ~ClassK(){}
  public override void Dispose(){}
}//end ClassK

 

 

Realize

public class ClassM {
  public ClassM(){}
  ~ClassM(){}
  public virtual void Dispose(){}
}//end ClassM

 

public class ClassN : ClassM {
   public ClassN(){}
   ~ClassN(){}
   public virtual void Dispose(){}
}//end ClassN

 

 

 

Dependency

public class ClassO {
   public ClassO(){}
   ~ClassO(){}
   public virtual void Dispose(){}
}//end ClassO

 

public class ClassP {
   public ClassP(){}
   ~ClassP(){}
   public virtual void Dispose(){}
}//end ClassP

 

 

Derive

Implementing of interface

public interface Interface1 {
}//end Interface1

public class ClassN {
   public ClassN(){}
   ~ClassN(){}
   public virtual void Dispose(){}
}//end ClassN

 

 

 

 

 

Abstract class

public abstract class AbstractClassR {
   public AbstractClassR(){}
   ~AbstractClassR(){}
  public virtual void Dispose(){}
}//end AbstractClassR

 

 

Singleton

/// <summary>
/// This class (a) defines an Instance operation that lets clients access its
/// unique instance, and (b) may be responsible for creating its own unique
/// instance.
/// </summary>
public class Singleton {
  private int singletonData;
  private static int uniqueInstance;
  public Singleton(){}
  ~Singleton(){}
  public virtual void Dispose(){}
  public void GetSingletonData(){}
  public static void Instance(){
  //return uniqueInstance
  }
  public void SingletonOperation(){}
}//end Singleton

 

Links

• UML cribs

UML crib 1

This is my UML crib, taht is devoted to relationships between entities. Be careful, I don’t recognize between analyze and design disciplines in this crib. 

I found nice links here:

• UML tutorial
• OOP Concepts

Association

NOTE:  Undefined line between entity (no arrow) is used in Architecture. But in the design dicipline it has no sense. In the design discipline it means bi-directional arrow <->. Or nothing. In the all cases. Use it in Analyse discipline, but not in the design discipline. 

Aggregation

 

Composition

 

NOTE: By my opinion. It has no sense in the analyse discipline. Use it in the design discipline.

Specialization

 

Association versus Aggregation

 

Aggregation versus Composition