The TASK_LIFECYCLE enumeration type includes a state 'resumed' that does not exist. This should be removed, including from the BMM.
Additionally, various mentions of ‘aborted’ state appear in the text; these should be changed to ‘abandoned’.
Also put the TASK_LIFECYCLE enumeration table next to the state machine diagram in the spec.
Ok, I think the numerical value aspect of the enum is fixed.
I still need to know if you agree that I modify the def. of ‘suspended’ to mean ‘'performable Tasks that have been put on hold, and dispatchable Tasks that are blocked waiting on another performer’.
Or it may be that we even think the latter is not correct; thinking about it, it might be better to show a waiting Dispatchable Task as ‘underway’. I ‘suspended’ is only used for Tasks that really are known to be ‘on hold’.
I agree with the latter notion, yes, so I’m in favour of modifying that definition to just “Tasks that have been put on hold”, without any elaboration as to how that applies to dispatchable tasks, and for performable tasks it is obvious anyway.
But can you set those values in BMM? Because I’m pretty confident that Archetype Designer will encode wrong integers for constraints and default values because it relies on BMM.