Impact Analysis

Describes the version management and the impact analysis when a requirement is modified.

Overview

When the input evolves, the coverage relationships evolves too and output must be updated in the following cases:

The impact analysis consists in analyzing the all the coverage errors after such modifications : identify all elements of output that shall be updated. REQCHECKER™ includes an impact analysis presented in the coverage matrix report.

Example

In this example :

If requirement in not fully covered, for example I3, its status is PARTIAL.

A coverage error occurs when :

See Status List Page.

Automatic version

The software automatically creates a version for each requirement when no version is defined by the statement. The automatic version is a 6 characters length hash number, for example 5CJYS3.

The hash is computed from text and picture read from documents. The automatic version is not dependent from the following changes:

The 6 characters length collision probabilities are: - If you update the requirement once, then update the coverage, the probability to skip the modification is 0.0000004%. - If you update the requirement 10 times, then update the coverage, the probability to get the same hash is 0.000016%.