Two modes of Activities may use the Activity’s Mini-Spec as implementation:
● Reactive Activities
When the functionality is best defined as pairs of triggers and actions, that language is the most suitable to define that behavior. The syntax is exactly trigger and action: E/A thus directly expresses the required behavior.
This textual language allows most clear, straight forward and compact implementation when the required functionality might be defined as a set of triggers and resulting actions.
For example: On/Off Behavior like the following:Button1Press/turn_on(); tr!(Lamp1);;
Button2Press/fs!(Lamp1); shutdown();;
● Procedural Activities
When the functionality is a pure calculation, defined as a sequence of “if then else,” iterations and numerical calculations that language might be used. It is similar in its expressiveness to the Flowchart graphical language, however it does not requires any graphics, thus might be faster to complete when the algorithm is already proved to be correct.
This textual language is the Rational Statemate Action Language. .