Is It Possible to Analyse Verification of Design Against Functional AND Non-functional Requirements in One Place / Step?
This is a potential problem caused by the architecture of DOORS Next and Quality Manager and probably the OSLC.
The first part of the problem is that DOORS Next uses the incorrectly defined 'validates' link [it should be 'verifies' according to the use and definition] between the RM and Quality Manager tool. The built-in link constraints require that this link is only used between the tools.
The second part of the problem is that Quality Manager provides only a means to 'verify' functional requirements. This may be a reflection of an OSLC weakness or error.
What about non-functional requirements? Clearly these don't require testing -- but they do require verification. The forms of evidence are typically studies, simulation output i.e. links to documents with the results and analysis. This could be set up with the RM component.
This then leaves us with a situation where the verification is handled differently between functional and non-functional requirements. The 'validation' link error prevents us from using the relationship properly and being able to distinguish between validation (e.g. of a model or requirement collection) and verification of the design against that set of requirement.
The problem if verification is split across two tools using different relationships [the QM tool requires 'validates' and the intra-RM links would use 'verifies'] is that I'm not sure that it is possible to analyse/view the collection in a single report.
How / has anyone else tackled this? From some of the responses to the OSLC error wrt 'validates' it doesn't seem that there is any appetite to correct it so we're stuck with a link constrain that is semantically incorrect.
|
One answer
Hi Nic,
RQM (now called ETM) can be used to test non-functional requirements. For example, testers can use pre-conditions, post-conditions, information steps in manual test scripts, custom rich text sections, etc. In addition, RQM/ETM integrates with non-functional test tools, such as RPT.
That said, you do raise an interesting limitation in cross-product linking/traceability. Unfortunately, you will have to use the same link type as testing functional requirements. Note, RQM/ETM 7.0 supports a link custom attribute type and DNG supports custom link types, but either supports a cross-product picker or backlinks. |
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.