For the complete documentation index, see llms.txt. This page is also available as Markdown.

Validation and review

The level of quality assurance required depends on the map's practical use case.

There are a number of methods that can be used to validate the accuracy of the map's content.

Dual/multiple user independent mapping

Dual independent mapping is often considered the "gold standard" approach and should be used when a high-quality map is required.

In this approach, each source code is independently mapped by 2 (or more) authors, and the results are then compared. When the authors agree on a mapping, it is accepted. If there is a conflict, the authors have a conflict resolution process to reach an agreement on the correct mapping.

An agreement is achieved for a given source code when all selected targets (or no map) and their respective relationship types are the same among the mapping authors.

The conflict resolution process may involve a workshop between the authors or the use of an adjudicator or subject-matter expert to make a decision.

Full review process

Reviewing is the use of human knowledge and skill to review maps.

Each and every map row is reviewed singly and individually. It is preferred that users conducting the review are not involved in the map's authoring to ensure unbiased validation. Due to resourcing constraints, this is not always possible; in such cases, it is recommended that users conducting the reviews not review their own mapping work.

Sampling review process

In this approach, a sample set is selected from the whole map. The sample set is then reviewed. Like the full review process, it is preferred that users performing the review are not involved in authoring of the map to ensure an unbiased validation, due to resourcing constraints, this is not always possible, and in these cases, it is recommended that users performing the reviews do not review their own authoring work.

If taking a sampling review approach, care should be taken when selecting the sample set and acceptable error rate, depending on the map's risk rating. This approach may not be suitable for most maps, as it does not necessarily validate the entire map, but it may be more suitable for ongoing map maintenance.

Provide Feedback

Last updated