search

nmfta-repo / vcr-experiment

MIT License
1 stars 4 forks source link

capture intent of parent-child relationship in requirements #16

Closed BenGardiner closed 2 years ago

BenGardiner commented 2 years ago

The requirements here use the parent ref to indicate that the child requirement 'replaces' the parent requirement in a more specific context.

That should be captured in the intro to subsections for these more specific contexts e.g. Security Requirements for CAN Gateways

BenGardiner commented 2 years ago

based on strictdoc dev's answers here https://github.com/strictdoc-project/strictdoc/discussions/630#discussioncomment-2439610 it sure sounds like COMPOSITE_REQUIREMENT is the way to model the 'all sub requirements must be satisfied' .

It's not clear yet how to model 'one of the sub requirements must be satisfied'...

BenGardiner commented 2 years ago

The discussion in https://github.com/strictdoc-project/strictdoc/discussions/630#discussioncomment-2439610 has been resolved:

  1. COMPOSITE_REQUIREMENT is for modelling 'all of the following must be satisfied' .
  2. REF: PARENT is for modelling 'this requirements will in turn satisfy the parents' (traceability only).

For modeling 'any of' or 'one or more' the only way to do this that can also be exported to requirement interchange formats is to include the options as a note to implementors in STATEMENT or FREETEXT fields.