Conversion of Methods or Processes

ASCET offers the possibility to convert one signature type into another, e.g., a method into a process, or vice versa.

During conversion, the behavior specified for the signature type is kept. All external references (e.g., in other components) to the signature type are removed. This includes the following:

process assignments to a task of a project (will become <undefined> in the Tasks field of the project editor)
assigned sequence calls if the original method/process was used in the graphical specification of another component (will be reset)
references in the EHOOKS configuration

Restrictions

The following restrictions apply:

Only one method or process can be converted at a time.
Simultaneous conversion of several methods/processes is not supported.
Conversion is not possible if the component provides only one signature type.
Conversion is not possible if any information would be lost.
In such a case, conversion starts, but aborts with an error message shown in the ASCET monitor window. Click here for an example.
EXAMPLE
A method with two arguments and some local variables shall be converted into a process.
The arguments have no corresponding signature elements in a process; they cannot be kept, and the conversion fails. The reason is displayed in the ASCET monitor window.
In block diagram components, you can convert only methods/processes that belong to the currently loaded diagram.
The conversion algorithm does not check semantical equivalence.
The following signature types cannot be converted:
- AUTOSAR runnables
- operations in AUTOSAR ClientServer interfaces
- triggers, actions and conditions in state machines
- methods in CT blocks, Boolean tables, or conditional tables
Methods cannot be converted to AUTOSAR runnables.
It is not possible to undo a conversion.