ASP.NET Core

Search results

Uml Diagram Shapes

Uml Class Diagram Shapes

Class diagram is used to represent the static view of an application. The class diagrams are widely used in the modelling of object oriented systems because they are the only UML diagrams which can be mapped directly with object-oriented languages. Diagram supports to generate the class diagram shapes from business logic.

The UML class diagram shapes are explained as follows.

Class

A class describes a set of objects that shares the same specifications of features, constraints, and semantics. To define a class object, you should define the classifier as class.
Also, define the name, attributes, and methods of the class using the class property of node.
The attribute’s name, type, and scope properties allow you to define the name, data type, and visibility of the attribute.
The method’s name, parameters, type, and scope properties allow you to define the name, parameter, return type, and visibility of the methods.
The method parameters object properties allow you to define the name and type of the parameter.
The following code example illustrates how to create a class.

tagHelper

class.cs

<ejs-diagram id="container" width="100%" height="700px" nodes="@ViewBag.nodes">
</ejs-diagram>

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.Mvc;
using Syncfusion.EJ2.Diagrams;
namespace sample1.Controllers
{
    public class NodeController : Controller
    {
        // GET: Node
        public ActionResult Node()
        {
            List<DiagramNode> nodes = new List<DiagramNode>();
            List<UMLProperty> patientProperty = new List<UMLProperty>();
            patientProperty.Add(CreateUMLProperty("accepted", "Date"));

            List<UMLMethods> patientMethods = new List<UMLMethods>();
            patientMethods.Add(CreateUMLMethod("getHistory", "History"));

             nodes.Add(
                new DiagramNode()
                {
                    Id = "Patient",
                    OffsetX = 200,
                    OffsetY = 250,
                    Shape = new UmlClassifierShapeModel()
                    {
                        Type = "UMLClassifier",
                        Class = new Class()
                        {
                            Name = "Patient",
                            Attributes = patientProperty,
                            Methods = patientMethods
                        },
                    },
                }
            );
            ViewBag.Nodes =  Nodes
            return View();
        }
         public UMLProperty CreateUMLProperty(string name, string type)
        {
            UMLProperty property = new UMLProperty();
            property.Name = name;
            property.Type = type;
            return property;
        }
        public UMLMethods CreateUMLMethod(string name, string type)
        {
            UMLMethods method = new UMLMethods();
            method.Name = name;
            method.Type = type;
            return method;
        }
    }
     public class UmlClassifierShapeModel
    {
        [DefaultValue(null)]
        [HtmlAttributeName("type")]
        [JsonProperty("type")]
        public string Type
        {
            get;
            set;
        }

        [DefaultValue(null)]
        [HtmlAttributeName("class")]
        [JsonProperty("class")]
        public Class Class
        {
            get;
            set;
        }
    }
     public class Class
    {
        [DefaultValue(null)]
        [HtmlAttributeName("name")]
        [JsonProperty("name")]
        public string Name
        {
            get;
            set;
        }

        [DefaultValue(null)]
        [HtmlAttributeName("attributes")]
        [JsonProperty("attributes")]
        public List<UMLProperty> Attributes
        {
            get;
            set;
        }

        [DefaultValue(null)]
        [HtmlAttributeName("methods")]
        [JsonProperty("methods")]
        public List<UMLMethods> Methods
        {
            get;
            set;
        }
    }

    public class UMLProperty
    {
        [DefaultValue(null)]
        [HtmlAttributeName("name")]
        [JsonProperty("name")]
        public string Name
        {
            get;
            set;
        }
        [DefaultValue(null)]
        [HtmlAttributeName("type")]
        [JsonProperty("type")]
        public string Type
        {
            get;
            set;
        }
    }
    public class UMLMethods
    {
        [DefaultValue(null)]
        [HtmlAttributeName("name")]
        [JsonProperty("name")]
        public string Name
        {
            get;
            set;
        }
        [DefaultValue(null)]
        [HtmlAttributeName("type")]
        [JsonProperty("type")]
        public string Type
        {
            get;
            set;
        }
    }
}

Interface

An Interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations. To create an interface, define the classifier property as interface.
Also, define the name, attributes, and methods of the interface using the interface property of the node.
The attribute’s name, type, and scope properties allow you to define the name, data type, and visibility of the attribute.
The method’s name, parameter, type, and scope properties allow you to define the name, parameter, return type, and visibility of the methods.
The method parameter object properties of name and type allows you to define the name and type of the parameter.
The following code example illustrates how to create an interface.

tagHelper

interface.cs

<ejs-diagram id="container" width="100%" height="700px" nodes="@ViewBag.nodes">
</ejs-diagram>

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.Mvc;
using Syncfusion.EJ2.Diagrams;
namespace sample1.Controllers
{
    public class NodeController : Controller
    {
        // GET: Node
        public ActionResult Node()
        {
            List<DiagramNode> nodes = new List<DiagramNode>();
            List<UMLProperty> patientProperty = new List<UMLProperty>();
            patientProperty.Add(CreateUMLProperty("accepted", "Date"));

            List<UMLMethods> patientMethods = new List<UMLMethods>();
            patientMethods.Add(CreateUMLMethod("getHistory", "History"));

             nodes.Add(
                new DiagramNode()
                {
                    Id = "Patient",
                    OffsetX = 200,
                    OffsetY = 250,
                    Shape = new UmlClassifierShapeModel()
                    {
                        Type = "UMLClassifier",
                        Interface = new Interface()
                        {
                            Name = "Patient",
                            Attributes = patientProperty,
                            Methods = patientMethods
                        },
                    },
                }
            );
            ViewBag.Nodes =  Nodes
            return View();
        }
         public UMLProperty CreateUMLProperty(string name, string type)
        {
            UMLProperty property = new UMLProperty();
            property.Name = name;
            property.Type = type;
            return property;
        }
        public UMLMethods CreateUMLMethod(string name, string type)
        {
            UMLMethods method = new UMLMethods();
            method.Name = name;
            method.Type = type;
            return method;
        }
    }
     public class UmlClassifierShapeModel
    {
        [DefaultValue(null)]
        [HtmlAttributeName("type")]
        [JsonProperty("type")]
        public string Type
        {
            get;
            set;
        }

        [DefaultValue(null)]
        [HtmlAttributeName("class")]
        [JsonProperty("class")]
        public Class Class
        {
            get;
            set;
        }
    }
     public class Interface
    {
        [DefaultValue(null)]
        [HtmlAttributeName("name")]
        [JsonProperty("name")]
        public string Name
        {
            get;
            set;
        }

        [DefaultValue(null)]
        [HtmlAttributeName("attributes")]
        [JsonProperty("attributes")]
        public List<UMLProperty> Attributes
        {
            get;
            set;
        }

        [DefaultValue(null)]
        [HtmlAttributeName("methods")]
        [JsonProperty("methods")]
        public List<UMLMethods> Methods
        {
            get;
            set;
        }
    }

    public class UMLProperty
    {
        [DefaultValue(null)]
        [HtmlAttributeName("name")]
        [JsonProperty("name")]
        public string Name
        {
            get;
            set;
        }
        [DefaultValue(null)]
        [HtmlAttributeName("type")]
        [JsonProperty("type")]
        public string Type
        {
            get;
            set;
        }
    }
    public class UMLMethods
    {
        [DefaultValue(null)]
        [HtmlAttributeName("name")]
        [JsonProperty("name")]
        public string Name
        {
            get;
            set;
        }
        [DefaultValue(null)]
        [HtmlAttributeName("type")]
        [JsonProperty("type")]
        public string Type
        {
            get;
            set;
        }
    }
}

Enumeration

To define an enumeration, define the classifier property of node as enumeration. Also, define the name and members of the enumeration using the enumeration property of the node.
You can set a name for the enumeration members collection using the name property of members collection.
The following code example illustrates how to create an enumeration.

tagHelper

enumeration.cs

<ejs-diagram id="container" width="100%" height="700px" nodes="@ViewBag.nodes">
</ejs-diagram>

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.Mvc;
using Syncfusion.EJ2.Diagrams;
namespace sample1.Controllers
{
    public class NodeController : Controller
    {
        // GET: Node
        public ActionResult Node()
        {
            List<DiagramNode> nodes = new List<DiagramNode>();

            List<UMLMembers> patientMembers = new List<UMLMembers>();
            patientMembers.Add(CreateUMLMembers("Checking Account"));
            patientMembers.Add(CreateUMLMembers("Savings Account"));
            patientMembers.Add(CreateUMLMembers("Credit Account"));

             nodes.Add(
                new DiagramNode()
                {
                    Id = "Patient",
                    OffsetX = 200,
                    OffsetY = 250,
                    Shape = new UmlClassifierShapeModel()
                    {
                        Type = "UMLClassifier",
                        Enumeration = new Enumeration()
                        {
                            Name = "AccountType",
                            Members = patientMembers
                        },
                    },
                }
            );
            ViewBag.Nodes =  Nodes
            return View();
        }

        public UMLMembers CreateUMLMembers(string name)
        {
            UMLMembers members = new UMLMembers();
            members.Name = name;
            return members;
        }
    }
     public class UmlClassifierShapeModel
    {
        [DefaultValue(null)]
        [HtmlAttributeName("type")]
        [JsonProperty("type")]
        public string Type
        {
            get;
            set;
        }

        [DefaultValue(null)]
        [HtmlAttributeName("class")]
        [JsonProperty("class")]
        public Class Class
        {
            get;
            set;
        }
    }
     public class Enumeration
    {
        [DefaultValue(null)]
        [HtmlAttributeName("name")]
        [JsonProperty("name")]
        public string Name
        {
            get;
            set;
        }

        [DefaultValue(null)]
        [HtmlAttributeName("members")]
        [JsonProperty("members")]
        public List<UMLMembers> Members
        {
            get;
            set;
        }
    }

    public class UMLMembers
    {
        [DefaultValue(null)]
        [HtmlAttributeName("name")]
        [JsonProperty("name")]
        public string Name
        {
            get;
            set;
        }
    }
}

Connector shapes

The connector shape property defines the role or meaning of the connector.
The different types of connector shapes are BPMN, UmlClassifier, and UmlActivity and can render these shapes by setting the connector shape type property.
The type of flow shapes in a BPMN process are sequence, association, and message.

Relationships

A relationship is a general term covering the specific types of logical connections found on class diagrams.
The list of relationships are demonstrated as follows.

Shape	Image
Association
Aggregation
Composition
Inheritance
Dependency

Association

Association is basically a set of links that connects elements of an UML model. The type of association are as follows.

1. Directional
2. BiDirectional

The association property allows you to define the type of association. The default value of association is “Directional”. The following code example illustrates how to create an association.

tagHelper

association.cs

<ejs-diagram id="container" width="100%" height="700px" connectors="@ViewBag.connectors">
</ejs-diagram>

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.Mvc;
using Syncfusion.EJ2.Diagrams;
namespace sample1.Controllers
{
    public class NodeController : Controller
    {
        // GET: Node
        public ActionResult Node()
        {
            // Sets the Annotation for the Node
            List<DiagramConnector> Connectors = new List<DiagramConnector>();
            Connectors.Add(new DiagramConnector() { 
                Id = "connector",
                SourcePoint = new DiagramPoint() { X = 100, Y = 100 },
                TargetPoint = new DiagramPoint() { X = 200, Y = 200 },
                Shape = new {type = "UmlClassifier", relationship="Association", association="BiDirectional"}
            });
            ViewBag.connectors = Connectors;
            return View();
        }
    }
}

Aggregation

Aggregation is a binary association between a property and one or more composite objects which group together a set of instances. Aggregation is decorated with a hollow diamond. To create an aggregation shape, define the relationship as “aggregation”.

The following code example illustrates how to create an aggregation.

tagHelper

aggregation.cs

<ejs-diagram id="container" width="100%" height="700px" nodes="@ViewBag.connectors">
</ejs-diagram>

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.Mvc;
using Syncfusion.EJ2.Diagrams;
namespace sample1.Controllers
{
    public class NodeController : Controller
    {
        // GET: Node
        public ActionResult Node()
        {
            // Sets the Annotation for the Node
            List<DiagramConnector> Connectors = new List<DiagramConnector>();
            Connectors.Add(new DiagramConnector() { 
                Id = "connector",
                SourcePoint = new DiagramPoint() { X = 100, Y = 100 },
                TargetPoint = new DiagramPoint() { X = 200, Y = 200 },
                Shape = new {type = "UmlClassifier", relationship="Aggregation" }
            });
            ViewBag.connectors = Connectors;
            return View();
        }
    }
}

Composition

Composition is a “strong” form of “aggregation”. Composition is decorated with a black diamond. To create a composition shape, define the relationship property of connector as “composition”.

The following code example illustrates how to create a composition.

{% tab template= “diagram/umldiagramshapes”, es5Template=“es5composition” %}

tagHelper

composition.cs

<ejs-diagram id="container" width="100%" height="700px" connectors="@ViewBag.connectors">
</ejs-diagram>

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.Mvc;
using Syncfusion.EJ2.Diagrams;
namespace sample1.Controllers
{
    public class NodeController : Controller
    {
        // GET: Node
        public ActionResult Node()
        {
            // Sets the Annotation for the Node
            List<DiagramConnector> Connectors = new List<DiagramConnector>();
            Connectors.Add(new DiagramConnector() { 
                Id = "connector",
                SourcePoint = new DiagramPoint() { X = 100, Y = 100 },
                TargetPoint = new DiagramPoint() { X = 200, Y = 200 },
                Shape = new {type = "UmlClassifier", relationship="Composition"}
            });
            ViewBag.connectors = Connectors;
            return View();
        }
    }
}

Dependency

Dependency is a directed relationship, which is used to show that some UML elements needs or depends on other model elements for specifications. Dependency is shown as dashed line with opened arrow. To create a dependency, define the relationship property of connector as “dependency”.

The following code example illustrates how to create an dependency.

tagHelper

dependency.cs

<ejs-diagram id="container" width="100%" height="700px" connectors="@ViewBag.connectors">
</ejs-diagram>

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.Mvc;
using Syncfusion.EJ2.Diagrams;
namespace sample1.Controllers
{
    public class NodeController : Controller
    {
        // GET: Node
        public ActionResult Node()
        {
            // Sets the Annotation for the Node
            List<DiagramConnector> Connectors = new List<DiagramConnector>();
            Connectors.Add(new DiagramConnector() { 
                Id = "connector",
                SourcePoint = new DiagramPoint() { X = 100, Y = 100 },
                TargetPoint = new DiagramPoint() { X = 200, Y = 200 },
                Shape = new {type = "UmlClassifier", relationship="Dependency"}
            });
            ViewBag.connectors = Connectors;
            return View();
        }
    }
}

Inheritance

Inheritance is also called as “generalization”. Inheritance is a binary taxonomic directed relationship between a more general classifier (super class) and a more specific classifier (subclass). Inheritance is shown as a line with hollow triangle.

To create an inheritance, define the relationship as “inheritance”.

The following code example illustrates how to create an inheritance.

tagHelper

inheritance.cs

<ejs-diagram id="container" width="100%" height="700px" connectors="@ViewBag.connectors">
</ejs-diagram>

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.Mvc;
using Syncfusion.EJ2.Diagrams;
namespace sample1.Controllers
{
    public class NodeController : Controller
    {
        // GET: Node
        public ActionResult Node()
        {
            // Sets the Annotation for the Node
            List<DiagramConnector> Connectors = new List<DiagramConnector>();
            Connectors.Add(new DiagramConnector() { 
                Id = "connector",
                SourcePoint = new DiagramPoint() { X = 100, Y = 100 },
                TargetPoint = new DiagramPoint() { X = 200, Y = 200 },
                Shape = new {type = "UmlClassifier", relationship="Inheritance"}
            });
            ViewBag.connectors = Connectors;
            return View();
        }
    }
}

Multiplicity

Multiplicity is a definition of an inclusive interval of non-negative integers to specify the allowable number of instances of described element. The type of multiplicity are as follows.

1. OneToOne
2. ManyToOne
3. OneToMany
4. ManyToMany

By default the multiplicity will be considered as “OneToOne”.
The multiplicity property in UML allows you to specify large number of elements or some collection of elements.
The shape multiplicity’s source property is used to set the source label to connector and the target property is used to set the target label to connector.
To set an optionality or cardinality for the connector source label, use optional property.
The lowerBounds and upperBounds could be natural constants or constant expressions evaluated to natural (non negative) number. Upper bound could be also specified as asterisk ‘*’ which denotes unlimited number of elements. Upper bound should be greater than or equal to the lower bound.
The following code example illustrates how to customize the multiplicity.

tagHelper

multiplicity.cs

<ejs-diagram id="container" width="100%" height="700px" connectors="@ViewBag.connectors">
</ejs-diagram>

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.Mvc;
using Syncfusion.EJ2.Diagrams;
namespace sample1.Controllers
{
    public class NodeController : Controller
    {
        // GET: Node
        public ActionResult Node()
        {
            // Sets the Annotation for the Node
            List<DiagramConnector> Connectors = new List<DiagramConnector>();
            Connectors.Add(new DiagramConnector() { 
                Id = "connector",
                SourcePoint = new DiagramPoint() { X = 100, Y = 100 },
                TargetPoint = new DiagramPoint() { X = 200, Y = 200 },
                Shape = new {type = "UmlClassifier", relationship="Dependency", multiplicity= new {type="OneToMany"}}
            });
            ViewBag.connectors = Connectors;
            return View();
        }
    }
}

UmlActivity diagram

Activity diagram is basically a flowchart to represent the flow from one activity to another. The activity can be described as an operation of the system.

The purpose of an activity diagram can be described as follows.

1. Draw the activity flow of a system.

2. Describe the sequence from one activity to another.

3. Describe the parallel, branched, and concurrent flow of the system.

To create a UmlActivity, define type as “UmlActivity” and the list of built-in shapes as demonstrated as follows and it should be set in the “shape” property.

Shape	Image
Action
Decision
MergeNode
InitialNode
FinalNode
ForkNode
JoinNode
TimeEvent
AcceptingEvent
SendSignal
ReceiveSignal
StructuredNode
Note

The following code illustrates how to create a UmlActivity shapes.

tagHelper

UmlActivity.cs

<ejs-diagram id="container" width="100%" height="700px" nodes="@ViewBag.nodes">
</ejs-diagram>

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.Mvc;
using Syncfusion.EJ2.Diagrams;
namespace sample1.Controllers
{
    public class NodeController : Controller
    {
        // GET: Node
        public ActionResult Node()
        {
            // Sets the Annotation for the Node
            List<DiagramNode> Nodes = new List<DiagramNode>();

            Nodes.Add(new DefaultNode()
            {
                Id = "Node1",
                OffsetY = 100,
                OffsetX = 100,
                Height = 100,
                Width = 100,
                Shape = new {type="UmlActivity", shape="Action"}
            });
            ViewBag.nodes = Nodes;
            return View();
        }
    }
}

UmlActivity connector

To create an UmlActivity connector, define the type as “UmlActivity” and flow as either “Exception” or “Control” or “Object”.

The following code illustrates how to create a UmlActivity connector.

tagHelper

UmlActivityConnector.cs

<ejs-diagram id="container" width="100%" height="700px" connectors="@ViewBag.connectors">
</ejs-diagram>

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.Mvc;
using Syncfusion.EJ2.Diagrams;
namespace sample1.Controllers
{
    public class NodeController : Controller
    {
        // GET: Node
        public ActionResult Node()
        {
            // Sets the Annotation for the Node
            List<DiagramConnector> Connectors = new List<DiagramConnector>();
            Connectors.Add(new DiagramConnector() {
                Id = "connector",
                SourcePoint = new DiagramPoint() { X = 100, Y = 100 },
                TargetPoint = new DiagramPoint() { X = 200, Y = 200 },
                Shape = new {type = "UmlActivity", flow="Exception"}
            });
            ViewBag.connectors = Connectors;
            return View();
        }
    }
}

Editing

You can edit the name, attributes, and methods of the class diagram shapes just double clicking, similar to editing a node annotation.

The following image illustrates how the text editor looks in an edit mode.

Editing Class Diagram

Contents

Uml Class Diagram Shapes
Class
Interface
Enumeration
Connector shapes
Relationships
Association
Aggregation
Composition
Dependency
Inheritance
Multiplicity
UmlActivity diagram
UmlActivity connector
Editing

Contents

Uml Class Diagram Shapes
Class
Interface
Enumeration
Connector shapes
Relationships
Association
Aggregation
Composition
Dependency
Inheritance
Multiplicity
UmlActivity diagram
UmlActivity connector
Editing

Please provide additional information

Thank you for your feedback and comments.We will rectify this as soon as possible!