Incorrect representation of execute() in sequence diagram

[SongZijin]

In the sequence diagram of runBagPacker() Mechanism, when BagPacker call the Command to execute, another self-call of the execute() function is shown. However, this function should have already been called at the start of the activation bar and thus should be incorrect to call it again in the execute function.

If the intention is to show that there may be cases where the execute function calls other functions in the same Command class, denoting the self-call arrow with execute() can be confusing to the reader.

[soc-se-bot]

Your response not required for this bug as the team has accepted the bug as it is.