Skip to Content

Best Practice for assigning Data Asset personas/characterizations

Best Practice for assigning Data Asset personas/characterizations. I am looking to assign what I would term as a "business data type" where defined it would be something like "data formats and specific meaning for the value contained within an attribute", an example would be a "business data type" of "USPhoneNumber", where it would (always) be a phone number having the format of "nnn-nnn-nnnn", i.e. as opposed to an "EUPhoneNumber" as a "business data type". Would it be best to use the PowerDesigner Entity Attribute Stereotype, or create a new custom Data Type? Has anyone else implement a similar concept?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

0 Answers