Klever

After optimization of EMG it became the only VTG component that may miss attribute "Requirements specification" for its Unknown reports. Indeed, you can imagine that there is the such number of Unknown reports that differ just by a value of the missed attribute as the number of all possible values of this attribute within a given job. It is not great to produce all these Unknown reports in the implementation, so, it would be better to extend the comparison algorithm in Bridge so that it will support incomplete tuples of attributes for comparing verification reports. This is a more generic approach that can help to deal with other cases as well.

Shortly speaking, the new algorithm should match tuples of attributes like (ATTR1_VAL1, ATTR3_VAL1) with (ATTR1_VAL1, ATTR2_VAL1, ATTR3_VAL1, ATTR4_VAL1), (ATTR1_VAL1, ATTR2_VAL2, ATTR3_VAL1, ATTR4_VAL2), (ATTR1_VAL1, ATTR2_VAL3, ATTR3_VAL1, ATTR4_VAL3) and so on. In other words, you can treat all tuples as (ATTR1_VAL, ATTR2_VAL, ..., ATTRN_VAL, ) where "" matches all attributes non-specified explicitly within a given tuple.