R513 - modelint/shlaer-mellor-metamodel GitHub Wiki

R513 / 1:Mc

Deletion State deletes instances in exactly one Lifecycle

Lifecycle instances are deleted after entering zero, one or many Deletion State

---

A Deletion State may exist only in a Lifecycle State Model. An Assigner is associated with an Association which, being part of the model structure itself, cannot be deleted.

A Lifecycle, on the other hand, may have any number of Deletion States if its corresponding Class instances can be deleted during runtime. Multiple Delete States may be desired when different transition paths precede deletion.

A Lifecycle without any Deletion States represents a Class whose instances are never deleted. This is the case with persistent instances, created during system initialization by the MX domain prior to runtime. It can also be the case with instances created at run-time that enter a final, non-deletion state under certain circumstances.