UAF14 — Insufficient distinction made between MissionVignette and MissionScenario

The UAF DMM specification does not make any significant distinction between the MissionScenario and MissionVignette concepts, nor does it suggest any formal (modeled) relationship between them. The only difference seems to be that a MissionVignette “can represent small, ideally self-contained parts of a scenario,” but this could have been more parsimoniously represented in the metamodel as a MissionScenario being composed of other MissionScenarios. If the ME Guide considers MissionScenario and MissionVignette to be different concepts, their descriptions in the UAF DMM specification should reflect and clarify the distinction. If a single type could be used in a model to represent both domain concepts, then the description of that type should envelope both concepts. What is currently in the spec represents the worst of both worlds: two different model implementations for the same domain concept, which will result in inconsistent usage by modelers.