The question: How can one constrain the inputs for tagged values created as attributes in stereotypes in a profile?
Outside of a profile I can edit Tagged Value Types, giving them a Type, LowerBound, UpperBound (see the "Create Structured Tags" help page).
When I create tags from a profile, though, I create attributes in a stereotype and these become tags when I import the stereotype into my working project. How do I apply the same sort of LowerBound, UpperBound, etc., to these attributes? (Presumably this is possible using the Constraints tab?)
Let me explain what I am trying to do. I want to create a data dictionary, not for a database, but for interface definitions. Essentially I am will be creating a design class diagram but the data classes will have full details (minValue, maxValue, defaultValue, unit, etc.) defined in UML. (I could keep the data dictionary in a spreadsheet, of course, but UML seems ideal for this since this information is truly in a model, so that updates will apply universally and I can properly represent inheritance.) I think tagged values are useful to show the details. Since I want to reuse this information I created a profile. Attributes on stereotypes, however, become tags when applied, so there is a difference....
Am I heading in the right direction or is there a better way to do this?
Also, if I change a profile (e.g., add a new attribute to a stereotype), is there a way to apply the new version of the stereotype from the new version of the profile to classes already created on a UML diagram using a previous version of that profile?
Thanks!
Paul
