Search

TOPIC: Empty requirements in my specification

Empty requirements in my specification 4 months 5 days ago #49

  • javier-fernandez
  • javier-fernandez's Avatar
  • Offline
  • Administrador
  • Posts: 52
  • Thank you received: 1
  • Karma: 0
Dear all

I am working in RQA with a module of requirements that contains several empty requirements (they only have a header). I would like to not evaluate quality for those requirements because I think it is useful.

Is there any option?

Regards,
The administrator has disabled public write access.

Empty requirements in my specification 4 months 5 days ago #50

  • javier-fernandez
  • javier-fernandez's Avatar
  • Offline
  • Administrador
  • Posts: 52
  • Thank you received: 1
  • Karma: 0
Hi!

It is a good question.

You can create a filter to your module in order to avoid assessing quality to the requirements. In RQA, go to the Project Configuration tab and then click on the Modules button. Select the module and open its properties (right-click or double-click).

The properties window has a section to create this filter, using an attribute from the requirements in DOORS. In this case (see the first screenshot), I setup a filter saying that the Object Text of the requirement cannot be empty.

Then, the scoreboard of requirements will hide the requirements not matching the filters. The requirements will no be assessed anymore.

Hope you find this information useful.
Attachments:
The administrator has disabled public write access.