Introduce a CheckDecisionPoint mapping. The CheckDecisionPoint depends on all predicating partitions. The realizing partitions depend on the CheckDecisionPoint. This should therefore involve relatively little disruption to scheduling or code generation.
The new CheckDecisionPoint mapping has to perform the correlation of future outputs as indicated by the actual traces. If successful the correlated outputs should be assigned to the traces so that realizing partitions finish off. Perhaps it is necessary to switch modes for create/update functionality.
| --- | --- | | Bugzilla Link | 547198 | | Status | NEW | | Importance | P3 normal | | Reported | May 12, 2019 09:28 EDT | | Modified | May 12, 2019 10:13 EDT | | Depends on | 547199 | | Blocks | 515236 | | See also | 547200 | | Reporter | Ed Willink |
Description
Further to http://www.eclipse.org/mmt/qvt/docs/CheckBeforeEnforce/CheckBeforeEnforce.pdf add support for a sound check-before-enforce.
Suggested approach.
Introduce a CheckDecisionPoint mapping. The CheckDecisionPoint depends on all predicating partitions. The realizing partitions depend on the CheckDecisionPoint. This should therefore involve relatively little disruption to scheduling or code generation.
The new CheckDecisionPoint mapping has to perform the correlation of future outputs as indicated by the actual traces. If successful the correlated outputs should be assigned to the traces so that realizing partitions finish off. Perhaps it is necessary to switch modes for create/update functionality.