-
Key: KERML-118
-
Status: closed
-
Source: Self ( Jim Ciarcia)
-
Summary:
Constraint
deriveFeatureFeaturingType
Feature.featuringType is shown as the union of all the typeFeaturings that feature it with the first type of a feature chain. But what is not included is the possible FeatureMembership.
This conflicts with the fact that Feature.owningType subsets featuringType and Feature.owningType is the owningType of an owningFeatureMembership. (Bonus: there is no derived property for codifying that statement of the derived /owningType attribute).Resolution of this issue may be worth utilizing typeWithFeature in more places instead of featuringType
-
Reported: KerML 1.0b1 — Mon, 10 Jul 2023 01:11 GMT
-
Disposition: Resolved — KerML 1.0b2
-
Disposition Summary:
Correct the OCL for deriveFeatureFeaturingType
The OCL for deriveFeatureFeaturingType should use featuring rather than typeFeaturing. The property typeFeaturing contains only the TypeFeaturings for which a Feature is the featureWithType, while featuring contains all Featurings relating to a Feature, including all FeatureMemberships (which are Featurings).
Note also that Feature::owningType is derived implicitly as the inverse of Type::feature, for which the derivation is given by deriveTypeFeature.
-
Updated: Tue, 1 Jul 2025 15:00 GMT
KERML — deriveFeatureFeaturingType conflicts with owningType
- Key: KERML-118
- OMG Task Force: Kernel Modeling Language (KerML) 1.0 FTF