Design elements - UML class diagrams

The vector stencils library "UML class diagrams" contains 38 symbols for the ConceptDraw PRO diagramming and vector drawing software.
"... classes are represented with boxes which contain three parts:
(1) The top part contains the name of the class. It is printed in Bold, centered and the first letter capitalized.
(2) The middle part contains the attributes of the class. They are left aligned and the first letter is lower case.
(3) The bottom part gives the methods or operations the class can take or undertake. They are also left aligned and the first letter is lower case. ...
To indicate a classifier scope for a member, its name must be underlined. ...
An association can be named, and the ends of an association can be adorned with role names, ownership indicators, multiplicity, visibility, and other properties. ...
Aggregation ... is graphically represented as a hollow diamond shape on the containing class end of the tree with a single line that connects the contained class to the containing class.
... graphical representation of a composition relationship is a filled diamond shape on the containing class end of the tree of lines that connect contained class(es) to the containing class.
... graphical representation of a Generalization is a hollow triangle shape on the superclass end of the line (or tree of lines) that connects it to one or more subtypes.
... graphical representation of a Realization is a hollow triangle shape on the interface end of the dashed line (or tree of lines) that connects it to one or more implementers. A plain arrow head is used on the interface end of the dashed line that connects it to its users.
Multiplicity ... representation of an association is a line with an optional arrowhead indicating the role of the object(s) in the relationship, and an optional notation at each end indicating the multiplicity of instances of that entity (the number of objects that participate in the association).
Entity classes ... are drawn as circles with a short line attached to the bottom of the circle. Alternatively, they can be drawn as normal classes with the «entity» stereotype notation above the class name." [Class diagram. Wikipedia]
The example "Design elements - UML class diagrams" is included in the Rapid UML solution from the Software Development area of ConceptDraw Solution Park.

The vector stencils library "UML object diagrams" contains 26 symbols for the ConceptDraw PRO diagramming and vector drawing software.
"Each object and link on an object diagram is represented by an InstanceSpecification. This can show an object's classifier (e.g. an abstract or concrete class) and instance name, as well as attributes and other structural features using slots. Each slot corresponds to a single attribute or feature, and may include a value for that entity.
The name on an instance specification optionally shows an instance name, a ':' separator, and optionally one or more classifier names separated by commas. The contents of slots, if any, are included below the names, in a separate attribute compartment. A link is shown as a solid line, and represents an instance of an association. ...
If you are using a UML modeling tool, you will typically draw object diagrams using some other diagram type, such as on a class diagram. An object instance may be called an instance specification or just an instance. A link between instances is generally referred to as a link. Other UML entities, such as an aggregation or composition symbol (a diamond) may also appear on an object diagram." [Object diagram. Wikipedia]
The example "Design elements - UML object diagrams" is included in the Rapid UML solution from the Software Development area of ConceptDraw Solution Park.

"Chen's notation for entity–relationship modeling uses rectangles to represent entity sets, and diamonds to represent relationships appropriate for first-class objects: they can have attributes and relationships of their own. If an entity set participates in a relationship set, they are connected with a line.
Attributes are drawn as ovals and are connected with a line to exactly one entity or relationship set.
Cardinality constraints are expressed as follows:
- a double line indicates a participation constraint, totality or surjectivity: all entities in the entity set must participate in at least one relationship in the relationship set;
- an arrow from entity set to relationship set indicates a key constraint, i.e. injectivity: each entity of the entity set can participate in at most one relationship in the relationship set;
- a thick line indicates both, i.e. bijectivity: each entity in the entity set is involved in exactly one relationship.
- an underlined name of an attribute indicates that it is a key: two different entities or relationships with this attribute always have different values for this attribute.
Attributes are often omitted as they can clutter up a diagram; other diagram techniques often list entity attributes within the rectangles drawn for entity sets." [Entity–relationship model. Wikipedia]
The vector stencils library ERD, Chen's notation contains 13 symbols for drawing entity-relatinship diagrams using the ConceptDraw PRO diagramming and vector drawing software.
The example "Design elements - ER diagram (Chen notation)" is included in the Entity-Relationship Diagram (ERD) solution from the Software Development area of ConceptDraw Solution Park.

The vector stencils library "UML package diagrams" contains 21 symbols for the ConceptDraw PRO diagramming and vector drawing software.
"A package diagram in the Unified Modeling Language depicts the dependencies between the packages that make up a model. ...
Elements.
(1) Package: It is a general purpose mechanism for organizing model elements & diagrams into groups. It provides an encapsulated namespace within which all the names must be unique. It is used to group semantically related elements. It is a namespace as well as an element that can be contained in other package's namespaces.
(2) Class: It is a representation of objects, that reflects their structure and behavior within the system. It is a template from which actually running instances are created. Classes usually describe logical structure of system.
(3) Interface: It is a specification of behavior. Implementing classes of an interface class are required to support the behavior.
(4) Object: It is an instance of class. It is often used in analysis to represent numerous artifacts and items that exist.
(5) Table: It is a stereotyped class." [Package diagram. Wikipedia]
The example "Design elements - UML package diagrams" is included in the Rapid UML solution from the Software Development area of ConceptDraw Solution Park.