How to model all-of vs. one-of? #630
-
I have read through the ReqIF document from the OMG and also have become pretty familiar with strictdoc but I'm not sure how to model these two different situations in strictdoc:
for example, is the parent-child relationship supposed to mean 1) whereas composite means 2)? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 17 replies
-
something we tried out in vcr-experiment was to model all-of as parent-child and one-of as composite But we don't know if that is the right approach to take. We'd like to get the approach right before the set of requirements explodes. |
Beta Was this translation helpful? Give feedback.
-
The idea behind the composite requirement seems to be a little different - the composite requirement states a requirement that is specified by its sub-requirements that are not "either or" options but are all smaller aspects that constitute this composite requirement altogether. Using composite requirement for options would probably work but is not the intended use case. |
Beta Was this translation helpful? Give feedback.
-
The answer is: model all-of using COMPOSITE_REQUIREMENT and model any options (one-of or one-or-more) as a note in the text of the requirement. |
Beta Was this translation helpful? Give feedback.
The answer is: model all-of using COMPOSITE_REQUIREMENT and model any options (one-of or one-or-more) as a note in the text of the requirement.