Klever

At the moment the code coverage kind is specified within the specifications base for individual requirement specifications. This enables a granular configuration since not for all requirement specifications (more exactly not for all verifier profiles associated with particular requirement specifications) there is a reasonable code coverage. But indeed this setting does not affect verification results, it just changes their representation. In most cases it is enough to obtain code coverage just for original sources - so called lightweight code coverage. Sometimes it can be very useful to get code coverage for other sources, e.g. for models.

I suggest to specify the code coverage kind when launching verification job solutions and to get rid of corresponding settings from the specifications base. When there will be no reasonable code coverage it will be simply missed after all.