








Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Instructions on creating User-Defined Properties (UDPs) in erwin Data Modeler for Models, Entities, and Attributes. UDPs add metadata to objects and make data models more mature and robust by providing auxiliary information related to business requirements, security, sources, and other important details. CMS recommended UDPs for the logical level of data models, including Model-Level, Entity-Level, and Attribute-Level UDPs.
Typology: Lecture notes
1 / 14
This page cannot be seen from the preview
Don't miss anything!









OIT|EADG|DEA|DAES
03/30/
User-Defined Properties (UDPs) add metadata to objects in a data model. In erwin, UDPs can be created for main object classes including Attributes, Entities, Models, Relationships, Diagrams, and Subject Areas, UDPs are flexible, modifiable and may have preset values.
A Data Model utilizing UDPs is more mature and robust as it can provide not just a structural representation of the system, but it is also able to show any auxiliary information that may be related to the business requirements, security, sources or any other important details associated with the system. The information described by a UDP can be anything deemed relevant in context of the project or system.
UDP Defined Properties are established within erwin IDE via tool configuration. They may exist on multiple levels of the data model, both logical and physical. CMS is interested in the Model, Entity, Attribute and Relationship UDPs at the Logical level of the Data Model. CMS strongly recommends having UDP in the Project’s data model for the model, entity, and attribute levels.
UDP Description Business Reason Entity Requirement ID Requirement ID for the entity Explains the creation of this entity Entity Data Source (optional)
Data source to load the entity Explains location of where entity is loaded (if different attributes loaded from different sources, this UDP should be provided on the attribute level Entity Security Category (optional)
Security, PHI, or PII category for the entity
Explains access level to the entity (if different attributes has different security or PHI/PII categories, this UDP should be provided on the attribute level
UDP Description Business Reason Attribute Data Source Source of records to load this attribute
Those two UDPs defines where this attribute loaded from – source of records and its element. Works as a composite primary key for data Attribute Data SourceElement Source of records elements toload this attribute source element
Attribute Security Category (optional)
Security or PHI/PII category for the attribute
If the same for all attributes in an entity, then may be provided on the entity level Attribute Valid Values (optional)
Valid values for the attribute List of valid values for he attribute in a free text form (if acceptable)