UML Notation - Integration - Update 44 - Help - Hexagon

Integration Help

Language
English
Product
Integration
Search by Category
Help
Smart 3D Version
12.1 (2019)
Smart Construction Version
2019(7.0)
SmartPlant Foundation / SDx Version
10
Smart Electrical Version
2019 (9.0)
Smart Materials/Smart Reference Data Version
2020 (10.0)
Smart P&ID Version
9 (2019)
Smart Review Version
2020 (15.0)
Smart Engineering Manager Version
10 (2019)
Smart Interop Publisher Version
13.1 (2019 R1)
Smart Isometrics Version
7.0(2019)
Spoolgen Version
9.0(2019)

In order to understand the UML diagrams used in the Schema Browser view, you must understand the basics of UML notation.

In UML all class objects are shown as rectangles with the name of the object and its stereotype at the top. Stereotypes define the types for classes and relationships. Stereotypes are always depicted in UML using the string <<stereotype>>, where stereotype is replaced by the appropriate value, such as ClassDef.

For example, Pump is stereotyped as a ClassDef, which means that Pump is a class definition in the schema.

Relationships in UML are shown as lines that connect objects. In the SmartPlant schema, the UML for each relationship has a stereotype that identifies the relationship type. Therefore, the following UML indicates that a relationship of type ScopedBy exists between the UID object, which is of type PropertyDef, and the String object, which is of type StringType.

One special type of relationship, a Realizes relationship, has a special symbology within UML and may or may not have a stereotype because the stereotype is redundant with the special symbology. For example, this graphic shows the PFDNozzlePort and the interfaces it realizes.

Certain relationships, called relationship definitions, not only have a stereotype but are also named and have roles and cardinalities defined at both ends of the relationship. A relationship definition not only defines a relationship but also establishes the type for a set of other relationships. For example, the Realizes relationship is typed by the Realizes relationship definition in the following graphic.

In this example, the Realizes relationship definition has a RealizedByClassDefs role and a cardinality of one-to-many at end 1. At end 2, it has a RealizedInterfaceDefs role and one to many cardinality. Because relationship definitions can be identified by the relationship name, roles, and cardinalities, the stereotype for relationship definitions (RelDef) is frequently left out of the UML.