timeslice/snapshot featuring types required to specialize or be same as types
Source: NIST ( Conrad Bock)
Clause 22.214.171.124 (OccurrenceUsage), Constraints, says
If the portionKind of an OccurrenceUsage is not empty, then, for each occurrenceDefinition of the OccurrenceUsage, there must be a featuringType of the OccurrenceUsage which either is the occurrenceDefinition or directly or indirectly specializes it.
For example, adapted from 7.13.5 (Successions as Usages):
checkOccurrenceUsageTypeFeaturing requires Flight to specialize each of Pre/In/Postflight, even though these would typically be disjoint with Flight, leading to:
- all features defined in Pre/In/Postflight "inheriting" to Flight, eg, PreFlight::refuel, would inherit to Flight, with a separate value potentially unconstrained in time from the one happening in preflight.
- valid traces where all the pre/in/postflight values are instances of Flight, which are all required to have pre/in/postflight timeslices.
which probably aren't intended in this exampe.
Reported: SysML 2.0a1 — Mon, 6 Nov 2023 14:05 GMT
Updated: Sat, 2 Dec 2023 14:17 GMT