Constraints are only available in the NIAM view, and they are used for modeling limitations on the relations between entities. There are three types of constraints:
On this page:
Like keys in a Crows Foot logical view, uniqueness constraints can be used for uniquely identifying an entity by linking it to one or more attributes in the entity. A single entity can have multiple uniqueness constraints.
To model the key, add a Uniqueness constraint object to the view. After that connect the key to the attributes in the entity you want to make a part of this key by using a Link relation.
If multiple uniqueness constraints are used, it is possible to assign them a sequence number. To assign a sequel number, follow these steps:
The sequence number is now displayed in the constraint:
When a constraint is linked to an attribute in an entity or to a fact, only the constraint is shown with a relation to the other element. To explicitly show which element the constraint is linked to, you can display the name of the relation. To display the name, do as follows:
The name is now displayed below the constraint:
You can hide the name again by clicking it.
Check out the free Enterprise Studio introductory eLearning course to learn about ERD modeling in Enterprise Studio.