feature-chaining-feature-conformance

Available in: KerML, SysML

This checks that all feature chain segments are accessible from the previous segment.

This is effectively standardizing nesting checks because chain segments can be referenced by qualified names. Typically this will not be triggered.

Specification

Each chaining_feature (other than the first) must be featured within the previous chaining_feature.

Example

This is easiest to trigger from KerML by overriding default featuring types:

class D;
feature A {
    feature B featured by D;
}
feature a chains A.B; // error

Default featuring types do not trigger this:

feature A {
    feature B;
}
feature a chains A.B; // ok