The auxiliary window and Java Developer

The "Java" tab of the auxiliary window on a package

Figure 5 - The "Java" tab of the auxiliary window on a package

Key:

1. This field is used to add the {JavaNoPackage} tagged value, indicating that packages will not be generated.

2. This field is used to add the {JavaRoot} tagged value, indicating that the package is the Java root.

The icons at the top of the window are used as follows:

· : This icon is used to launch Java generation.

· : This icon is used to launch Javadoc generation.

The "Java" tab of the auxiliary window on a class

Figure 6 - The "Java" tab of the auxiliary window on a class

Key:

1. The "Visibility" tickbox indicates the visibility of the class.

2. The "Abstract" tickbox indicates that the class is abstract.

3. The "Static" tickbox annotates the class using the {JavaStatic} tagged value, and indicates that the class is static.

4. The "Main class" tickbox indicates that the class should contain a main method. When you check this tickbox, a "public static void main (String[] argv)" is added to the class. The user must define the contents of this method.

5. The "Annotation" field is used to specify a Java 5 annotation.

6. The "Import" field is used to enter imports for the class in question. If you wish to specify several elements, separate them using a comma.

7. The "Javadoc" field is used to enter "Javadoc" type notes for the class in question.

8. The "Invariant" field is used to enter invariants for the class in question.

Note 1: When the selected class is an inner class in the modeling, a tickbox "InnerBox", figures in the auxiliary window. If this tickbox is not checked, the class is generated as a non-public class for its container class.

Note 2: When the "Main class" tickbox is checked, an additional button, "Run application" appears. This button is used to run the application. When you click on this button, a dialog box appears, inviting you to enter your application parameters. Enter and confirm to run the application.

The icons at the top of the window are used as follows:

· : This icon is used to launch Java generation.

· : This icon is used to visualize generated Java code.

· : This icon is used to edit generated Java code.

· : This icon is used to update generated Java code.

The "Java" tab of the auxiliary window on an operation

Figure 7 - The "Java" tab of the auxiliary window on an operation

Key:

1. The "Visibility" tickbox is indicates the visibility of the operation.

2. The "Operation type" button indicates the operation type (none, create, destroy).

3. The "Static" tickbox indicates that the operation is "class", in other words, shared by all its instances.

4. The "Final" tickbox adds the {JavaFinal} tagged value to the operation, and indicates that the operation is final.

5. The "Abstract" tickbox indicates that the operation is abstract.

6. The "Synchronize" tickbox adds the {JavaSynchronize} tagged value to the operation, and indicates that the operation is synchronized.

7. The "Native" tickbox adds the {JavaNative} tagged value to the operation, and indicates that the operation is native.

8. The "Throw exception" field is used to add the {JavaThrownException} tagged value to an operation.

9. The "Java code" field is used to enter or modify Java code for the operation.

10. The "Java return" field is used to write code at the end of the operation for the return statement.

11. The "Pre-condition" field is used to enter a constraint stereotyped <<JavaPreCondition>>.

12. The "Post-condition" field is used to enter a constraint stereotyped <<JavaPostCondition>>.

13. The "Javadoc" field is used to enter "Javadoc" type notes for the operation in question.

14. The "Template parameters" field is used to declare template parameters for the operation.

The icon at the top of the window is used as follows:

· : This icon is used to launch Java generation.

The "Java" tab of the auxiliary window on an attribute

Figure 8 - The "Java" tab of the auxiliary window on an attribute

Key:

1. This field indicates the visibility of the attribute.

2. This field is used to indicate the attribute's access mode.

3. The "Collection to use" field is used to add {type(x)}, where x can be one of a group of strings in a list. This field specifies, in a package context of type Java 5, the collection to be used and the type of interface published for this attribute, within a framework of multiple cardinality.

4. The "Static" tickbox indicates that the attribute is static.

5. The "Final" tickbox adds the {JavaFinal} tagged value to the attribute, and indicates that it is final.

6. The "Transient" tickbox adds the {JavaTransient} tagged value to the attribute, and indicates that it is final.

7. The "Wrapper" field is used to specify if a basic type must be generated as a wrapper class.

8. The "Multiplicity" field is used to enter the attibute's multiplicity

9. The "Initial value" field is used to give the attribute's initial value.

10. The "Javadoc" field is used to enter "Javadoc" type notes for the attribute in question. Please note that when the attribute is of base type, such as real, int, etc, additional, explicit tickboxes appear.

11. The "Binding parameters for generics" field is used to specify parameters if the attribute's datatype is a generic type.

For real-type attributes, the "double" and "float" fields also appear. These fields are used to specify that the attribute has double or float type respectively.

For integer-type attributes, the "long" and "short" fields also appear. These fields are used to specify that the attribute has long or short type respectively.

For char-type attributes, the "Byte" field also appears. This field is used to specify that the attribute has byte type.

Note: The parameters linked to the collection are included in the "Collection to use" field.

The icon at the top of the window is used as follows:

· : This icon is used to launch Java generation.

The "Java" tab of the auxiliary window on an association

Figure 9. The "Java" tab of the auxiliary window on an association

Key:

1. This field is used to select the access mode of the association.

2. The "Static" tickbox adds the {IsClass} tagged value to the association, and indicates that it is static.

3. The "Final" tickbox adds the {JavaFinal} tagged value to the association, and indicates that it is final.

4. The "Transient" tickbox adds the {JavaTransient} tagged value to the association, and indicates that it is transient.

5. The "Collection to use" field is used to add {type(x)}, where x can be one of a group of strings in a list. This field specifies, in a package context of type Java 5, the collection to be used and the type of interface published for this attribute, within a framework of multiple cardinality.

6. The "Multiplicity" field is used to enter the association's multiplicity.

7. The "Initial value" field is used to enter a "JavaInitValue" note for the selected association.

8. The "Javadoc" field is used to enter "Javadoc" type notes for the association in question.

9. The "Binding parameters for generics" field is used to specify parameters if the association's datatype is a generic type.

Note: The parameters linked to the collection are included in the "Collection to use" field.

The icon at the top of the window is used as follows:

· : This icon is used to launch Java generation.

The "Java" tab of the auxiliary window on a parameter

Figure 10. The "Java" tab of the auxiliary window on a parameter

Key:

1. The "Collection" field is used to add the {type(x)}.

2. The "Wrapper" field is used to if a basic type must be generated as a wrapper class.

3. The "double" field is used to specify that the parameter has double type.

4. The "float" field is used to specify that the parameter has float type.

5. The "Multiplicity" field is used to define the multiplicity of the parameter.

6. The "Javadoc" field is used to enter "Javadoc" type notes for the parameter in question.

7. The "Binding parameters for generics" field is used to specify parameters if the attribute's datatype is a generic type.