-
Key: SFPM_-13
-
Status: closed
-
Source: KDM Analytics ( Dr. Nikolai Mansourov)
-
Summary:
From AB review by Pete Rivett, March 17, 2020:
9.1.2.3 says that “Variations in the variation tree are considered ordered” but this is not represented in the metamodel using an ordered property. -
Reported: SFPM 1.0b1 — Tue, 15 Feb 2022 04:55 GMT
-
Disposition: Resolved — SFPM 1.0b2
-
Disposition Summary:
Update model, make Variation ordered and change owned end to 0..1
update model: make association from VariationSection to Variation
{ordered}, and 0..1 at the VariationSection end to accommodate the fact that a Variation can be also owned by another Variation.
Make association between Variation and Variatiion {ordered}and 0..1 at the owner end to accommodate the fact that a Variation can be also owned by another Variation.
-
Updated: Tue, 9 Jan 2024 22:27 GMT
SFPM_ — Make elements of variation tree ordered
- Key: SFPM_-13
- OMG Task Force: Software Fault Pattern Metamodel (SFPM) 1.0 FTF 2