Operation or Signal Signatures
An operation or signal signature consists of the name of the operation (or signal), its return type, and its parameters with their types. Standard UML syntax is used for signatures, in the form: Ope0 (Param0: M-Bool): M-Bool.
The signature can be defined:
• Either in the properties dialog box of the operation or signal.
• Or in the Properties dialog box of the class to which the operation belongs, by directly entering the Signature in the Operations tab.
When the signature is entered directly, its validity is checked. If there is an error, a dialog box specifies the nature of the error and allows you to correct it.
When the signature contains a type preceded or followed by a complement (for example, Ope1(param1: const double), it is necessary to remove the ambiguity by selecting one of the words in the expression.
If the type does not exist, it is automatically created.
The saved signature includes a reference to the type. If the type is renamed, the signatures that use it will reflect this change.
Signature syntax
The standard syntax for signatures is:
operationname(parameter1:typeexpression1,parameter2:typeexpression2,...):returnexpressiontype
Names containing spaces or special characters must be enclosed in single quotes ('Client name'). When a name contains an apostrophe, the apostrophe must be typed twice: 'Buyer''s Name'
Examples of signatures:
Unstock (Product0: Integer(3), Quantity0: Integer): Boolean
'Create order' ('Client name' : Client): Byref Variable
In a signature specification, it is possible to specify the package to which a class belongs, followed by two colons.
Example: Enterprise::'Sales Management'::Client.
The listed class is linked to the parameter or return type. If it does not exist, it is created. Any packages listed in the path that do not exist are also created, and linked to the class.
If the package is not specified, a dialog box will enable you to select from similarly named classes.
See also: "Operation or Signal Signatures"