How do handle a requirement that needs n "covers" references

[InfiniteNothing]

Hello, I have a requirements gateway question. I have a high level word document and some of the requirements are  going to need muliple "covers" reference.  In my case the high requirement is:

There are going to be two sensors.

<REQ 2Sensors>

This gets covered in two places in the low level document each of which generate their own requirements

Sensor 1 will by Brand A 

<REQ BrandA> 

<covers 2Sensors>

Sensor 2 will be Brand B 

<REQ BrandB>

 <covers 2Sensors>

 
I'm looking for a way to require that there are 2 <covers 2Sensors>  references so that if 1 gets deleted the feature is no long covered.

The solution must maintain that <REQ BrandA> and <REQ Brand B> are both nonderived requirements (because they are generated from <REQ 2Sensors>.

[Manooch_H]

Hi InfiniteNothing,

All you will have to do is create two separate coverage links from the covering documents to the requirements document like so:

Hope this helps!

[InfiniteNothing]

There are only two documents in my example

[InfiniteNothing]

But, now that you mention it. I have a second situation that I need help with. In this case:

 

I have the following requirements in the "Requirement Document"

• There will be a an RTD sensor 
• The RTD sensor will be very accurate

This gets covered in two documents (like the picture above). The parts list (Covering Document 1) and the specifications document (Covering Document 2).

An accuracy isn't appropriate for a parts list so I'd like to tell RG that for that particular requirement, no coverage is requiredin the parts list. Is there a way to do this?

Message Edited by InfiniteNothing on 08-14-2009 02:36 PM

[Manooch_H]

Hi InfiniteNothing,

Unfortunately, both of your goals can not be achieved with the way you have currently set up your project. For your first question, you can either specify two requirements one for Sensor1 and one for Sensor2 or you can split the coverage document into two documents. Unfortunately we can't change the rules which designate how a requirement is covered.

For your second question, we run into the same problem again where we can't change the rules. You do however have a few options. You can either create a section in your Parts List for Non-Part Requirements and specify the coverages for requirements such as accuracy there or you can create a separate document called Non-Part Coverages which contains the coverages for all requirements that will not have an associated part and or this document with the Parts List (Covering Document 1).

Hope this helps!