Software quality report

[Steve McDonald]

Once you have linked your requirements through use cases to test cases, it would be very useful to be able to generate a report to quantify the quality of the developed software.

Similar to an impact analysis report, this would show the number of test cases related to each related element together with a breakdown by test case status. In this way, you could ensure that each element (eg requirement) was covered by at least one test case and then identify which requirements had (or had not) been successfully tested.

You could also potentially look at the relationships from the other direction and use the information to prioritise / schedule testing to cover the most important associated elements.

Thanks

Steve
 

[Stefan Bolleininger]

Dear Steve,

i like your idea about the reports, but it has a big point which makes it unable for the tool-manufacturer to create such a solution:

"Your process is defined by yourself and not by the tool-manufacturer".

In your case the completeness of trace-chains would be:

Usecase<--Requirement<--Testcase.

my  Rulecheck is performed against

Requirement<--PARequirement<--PAObject/PAComponent/anything<--Testcase

(While all items with "PA" could be Possibly Available).

Such rulecheck and completeness-routines must be written against your process and it is hardly possible to define the overall accaptable process

Regards

Stefan