Custom UDPs in erwin Data Modeler: Recommended for Models, Entities, and Attributes, Lecture notes of Business

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

2021/2022

Uploaded on 09/27/2022

kimball
kimball 🇬🇧

5

(3)

220 documents

1 / 14

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
OIT|EADG|DEA|DAES
Instructions for Creating Custom UDPs in erwin Data Modeler
03/30/2021
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe

Partial preview of the text

Download Custom UDPs in erwin Data Modeler: Recommended for Models, Entities, and Attributes and more Lecture notes Business in PDF only on Docsity!

OIT|EADG|DEA|DAES

Instructions for Creating Custom UDPs in erwin Data Modeler

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.

Overview

CMS Recommended Entity-Level UDPs

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

CMS Recommended Attribute-Level UDPs

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)

Creating Model-Level UDPs (1 of 2)

  • Select the Model class.
  • Select the New icon.
  • Provide Name , Type , and (optional)

Default values.

  • Select the Close button.

Creating Model-Level UDPs (2 of 2)

  • Select Model on the Erwin main menu, then select Model Properties in the drop menu.
  • Select the UDP tab in the Model Editor dialogue window.
  • Select the UDP created in the previous steps and add the appropriate value.
  • Select the Close button.

Creating Entity-Level UDPs (2 of 2)

  • Navigating from erwin’s Model Explorer , expand the Entities tree, right-click the appropriate Entity , and select Properties.
  • Select the UDP tab in the Entity Editor dialogue window.
  • Select the UDP created in the previous steps and add the appropriate value.
  • Select the Close button.

Creating Attribute-Level UDPs (1 of 2)

After following the steps in the

Starting Point slide:

  • Select the Attribute class.
  • Click the New button.
  • Provide Name , Type , and (optional)

Default values.

  • Click the Close button.

Creating Relationship-Level UDPs (1 of 2)

After following the steps in the

Starting Point slide:

  • Select the Relationship class.
  • Select the New button.
  • Provide Name , Type , and (optional)

Default values.

  • Select the Close button.

Creating Relationship-Level UDPs (2 of 2)

  • Navigating from erwin’s Model Explorer , expand the Relationships tree, right-click the appropriate Relationship , and select Properties.
  • Open the UDP tab in the Relationship Editor dialogue window.
  • Select the UDP created in the previous steps and add the appropriate value.
  • Select the Close button.