DNG/JRS v7.0.2 0 - Managing & Displaying Requirements that aggregate Requirements
I'm looking for best known methods for managing, displaying, reporting, and linking an aggregation of requirements.
In our system, we have a set of quality requirements that are stand-alone and are also aggregated to operate concurrently.
Managing the set of stand-alone requirements in DNG, displaying in a Module, reporting via JRS tables and comprehending the RTM (reqs traceability matrix) is straight-forward.
We then define 'concurrency' requirements that specify which stand-alone requirements need to function as a concurrent set. In addition, the concurrency requirements should reference or 'reuse' the stand-alone requirements to avoid consistency issues.
The concurrency requirement should be comprehended in the following 'views'
A concurrency requirement specified as a Table of stand-alone requirements is visually pleasing, but hard to manage
<o:p> </o:p>
I'm interested to understand how others manage a set of requirements as a single concurrency requirement.
|
Be the first one to answer this question!
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.