It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×11,924
×5,819
×1,314

question asked: Feb 16 '22, 11:18 p.m.
question was seen: 380 times
last updated: Feb 16 '22, 11:18 p.m.

Related questions

FAQ - How this Forum works

DNG/JRS v7.0.2 0 - Managing & Displaying Requirements that aggregate Requirements

0
Kelly Hoffman (58●1●6) | asked Feb 16 '22, 11:18 p.m.

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'
  1. In a Module View <o:p> </o:p>
  2. In a JRS report <o:p> </o:p>
  3. In the RTM (requirements traceability matrix) <o:p> </o:p>
A concurrency requirement specified as a Table of stand-alone requirements is visually pleasing, but hard to manage

<o:p> </o:p>

  1. Tables as format Text – import/export issues, hard to Compare Configurations... <o:p> </o:p>
  2. Tables as Graphic-Diagram type – painful to build.  Rendering results in cartoonish text. (perhaps this is a v6.0.6 issue)  We are upgrading to 7.0.2 in the next few weeks. <o:p> </o:p>
  3. RTM of a text formatted requirement will not display well
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!

Register or to post your answer.


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.