Source: Model Driven Solutions ( Mr. Ed Seidewitz)
The approved resolution to
KERML-20adds the validation constraint validateFeatureValueOverriding that "All Features directly or indirectly redefined by the featureWithValue of a FeatureValue must have only default FeatureValues." This constraint causes problems for two models in the Systems Model Library. These library models do not actually violate the constraint, but using the models as intended my violate the constraint.
- In the action definition Actions::AcceptAction, the inout paramater payload is redefined with a feature value binding it to aState.aTransition.aPayload. However, when an accept action is parsed with a change or time trigger, the payload is implicitly bound to the generated change or time signal, and this violates the validateFeatureValueOverriding constraint.
- In the analysis case definition AnalysisCases::AnalysisCase:
- The subject of the objective of AnalysisCase is bound to the result parameter of the AnalysisCase. However, when specifying an analysis case, it is sometimes convenient to compute a check of the case objective by evaluating it on a given subject value. However, the binding of such an subject argument then violates the validateFeatureValueOverring constraint.
- The result parameter is bound to the result of the AnalysisCase::resultEvaluation calculation feature. However, when defining an analysis case in a user model, it is natural to bind the computation of the result of the case to the result parameter as a feature value. But this then violates the validateFeatureValueOverriding constraint.
Reported: SysML 2.0b1 — Tue, 24 Oct 2023 14:00 GMT
Updated: Thu, 30 Nov 2023 19:47 GMT