Measurement of traceability confirmation time after the implementation of CodeBeamer

[YI_14104864]

We are trying to evaluate the effectiveness of CodeBeamer by measuring the difference in requirement traceability confirmation time before and after its implementation.

Since it is very difficult to manually measure the time it takes to confirm traceability after CodeBeamer has been introduced, we would like to measure it using user operation logs.

Does CodeBeamer have such a feature?

If not, could you suggest an alternative method?

[GeoffreyClemm]

To understand your question, I'd need to know the following:

(1) What you mean by "requirement traceability confirmation time"?   

Is it, for example, how long it takes between when a link goes Suspect and the Suspect flag on that link is cleared?

(2) What use case needs this information (i.e., what benefit would be provided by having this information)?

(3) By "before and after its implementation", do you mean "the implementation of that requirement" or "the implementation of Codebeamer at your company"?