There are several formalisms that exist to depict behavior of blocks, chiefly State Machines, Activities and Interactions which would be allocated to the block with the use of the Allocation edge. Aside from these main formalisms it is possible for Blocks to directly own Opaque Behaviors and Function Behaviors. This section will look at the latter two in detail.

A Block can own a behavior that initiates when the block is instantiated. The behavior may terminate before the instance is terminates.

Typically this is a state machine which calls activities/interactions. A block can only have one Classifier Behavior?

Provide detail on how to process service requests

• Operation - Signature of a method. Must be owned by a block; have one or more inputs and output parameters and…
  • Synchronous Operation … have only one return parameter
  • Asynchronous Operation … have no return parameter
• Method - Some behavior that defines how an operation is executed
• Behavior - Body of method

• Reception - Some method associated with a signal (which is asynchronous). A reception designates a signal and specifies the expected behavioral response. The details of handling a signal are specified by the behavior associated with the reception or the classifier itself. The data carried by a (sent) signal is represented as attributes of the Signal. By declaring a reception associated to a given signal, a classifier specifies that its instances will be able to receive that signal, or a subtype thereof, and will respond to it with the designated behavior

• Provided Feature - A Feature that the block supports for other blocks to use
  • prov «signal» SignalA means owning block provides a reception for SignalA
• Required Feature - A Feature that the block requires other blocks to support for its own use
  • reqd «signal» SignalB means owning block requires a reception for SignalB