JeeWiz Modeler's Help File for RSA/RSM


	The Model-Driven System Builder

JeeWiz Modeler's Help File for RSA/RSM

Contents > 2. General Information

2.5 How to Set Properties

Most of the properties used by the JeeWiz transform are special properties that are unavailable within a standard UML diagram. JeeWiz properties for an item appear when you stereotype the item under the stereotype (and advanced) tab of the properties view of the item. To access these select the item (in the diagram or the model explorer), and then select the stereotype tab in the properties window. You may have to scroll down a little, but the stereotype properties will be found under the Add Stereotypes button.

Some properties, however, are UML standard properties and can be found under the general tab. These include the name (which in the case of an association is called label). Attributes may have a type added. This would normally be the case if they are stereotyped as attributes, but may not be necessary if they are stereotyped as dataviewFields. In either case, the type you set should be selected from the JeewizScreenMMLibrary. If this library is unavailable, it is possible you have set up your project incorrectly.

A property that is not set will almost always have a default value and it is rarely necessary to set any property value. The exception is usually name, but in the case of associations even names are not obligatory - role names are, but these and multiplicities will have values set by RSA. You can alter role names and multiplicities under the association's general tab or on the diagram. To get a default value back after you have set a value, you can choose the default option on a dropdown, but you can't just delete text. Instead right click on the property and choose reset default.

Dropdown lists on property values will usually have a "default" value. that does not mean that a value of "default" will be used by the transform. The transform will use whatever default the architect has decided to apply (or the standard default value out of the box). This is also the way standard boolean true/false values can remain unset in the model and allowed to default to the system standard. Perhaps a little confusingly, an event with no label (and no userNameBase) will set the button name to "default". Your architect may have overridden this.