What
Currently there are some feature level requirements existing, which do not have any derived component level requirement.
For details see corresponding appendix d here.
On the other hand, there are feature level requirements with many component requirements derived. See appendix e here
These requirements should be clarified in our regular meeting:
- Is it fine that these have no component level requirement?
- What happens if later on a component level requirement is introduced, but there is a test which already "fully verifies" the feature level requirement?
- Is there something like an "ideal number" of linked component requirements? So is it fine that two feature level requirements are used as a basis for ca. half of our component level requirements?
Acceptance Criteria (DoD)
TBD
How
No response
What
Currently there are some feature level requirements existing, which do not have any derived component level requirement.
For details see corresponding appendix d here.
On the other hand, there are feature level requirements with many component requirements derived. See appendix e here
These requirements should be clarified in our regular meeting:
Acceptance Criteria (DoD)
TBD
How
No response