I am interested if there is way to extend the schema to support easily custom metadata on entities and/or attributes (columns), so they can be later exported into XML and processed and also will be included in published documentation.
Generic ontology tools give you much bigger range in form of what you can do, maybe you should try to adopt this for later times and new design of VP.
Example requirement:
I have in data source file information which can be split into 4 different areas from domain model perspective:
General Context - person, address, etc.
General Master Data Context - Country, Region mapping tables
Specific Domain Data - Account, Installation
Specific Master Data Context - Product, etc.
So I have something like 4 labels which I would like to bind on entities for later usage.
About “include in published documentation”
It depends which way you publish documentation,
but in most of cases, Tagged Value already included by default.
Shapes in ER diagrams also support tagged values, if you cannot find tagged values tab in the specification window of a shape (e.g. Entity), try to look it up from the hidden tabs:
@roykeung - is tagged value supported on attribute level as well. See during our analysis, I would like to mark some field as SENSITIVE or other classification, I know I can use documentation, but some Key/Value store is better for such purpose.
Most of the model elements in Visual Paradigm can be configured to use stereotypes together with tagged values, class members like attribute and operation support them too. The link Roy posted above shows you how to apply them to actor, but it is no different for attribute.
Here shows how I defined a custom stereotype for attribute called “MyStereotype” with one boolean tagged value “Sensitive” default to false. By selecting from the diagram’s popup menu item “Presentation Options” > “Show Tagged Values” > “Show All”, you see I could make the tagged values visible in the diagram as well.
Sorry, on my testing,
the class’s Stereotype & Tagged Value, and attribute’s Tagged Value can be shown,
but the attribute’s Stereotype is missing.
@peter.wong - ok, so this is behavior on Class, but ER Entity has even different behavior from Class, I think only Stereotype on Entity is visible, the rest is not.
It will be valuable to display these as well on Entity layer.