
Metamodel user guide
Signals are processed by StateMachines, which represent how SignalEvents are taken into account.
Modelio provides the DataFlow extension to UML. Using this extension, a Signal can be declared as representing a ModelElement (GeneralClass, Operation, or Parameter).
A DataFlow associated to the Signal will then be able to express this data, represented by the Signal, and may circulate between different NameSpaces.
In Modelio, a Signal belongs to a NameSpace, notably its Package.


Attribute | Description |
---|---|
boolean IsEvent [0..1] | Establishes if it is an event in the sense of event based systems : CORBA, Java, XWindow's, SGBDR. |
boolean IsException [0..1] | Defines if it is an exception, as they exist in Java, C++, and so on. |
Association | Description |
---|---|
Base : GeneralClass [0..1] | |
OBase : Operation [0..1] | |
PBase : Parameter [0..1] | |
Receiver : AcceptSignalAction [0..*] | The type of signal accepted. |
Sends : Transition [0..*] | When the Transition is accomplished, occurrences of this Signal will be sent. |
Usage : Message [0..*] | Signal that is sent by the message. |
Sender : SendSignalAction [0..*] | The type of signal transmitted. |
EOccurence : Event [0..*] | Signal of which the Event is an occurrence. |
CommunicationUsage : CommunicationMessage [0..*] | Signal that is sent by the message. |
DOccurence : DataFlow [0..*] | Defines the DataFlow as being an instance of the associated Signal. |