Managing Software Changes (G06.24+)

Evaluating Software Changes
Managing Software Changes427169-003
3-14
Researching Conditional Requisites
Note also that Scout’s requisite analysis requires that the SPRs be installed on the
specified RVU as it is currently delivered. Two situations might require you to install
requisites that differ from those Scout selects, even though its analysis is correct:
If you have already installed an SPR for the same product as one of the selected
SPRs:
°
You might not need the selected SPR (or its requisites, if any) because the
SPR you installed supersedes it.
°
You might find that the SPR you are using and the selected SPR are mutually
exclusive, and that you must either give up function you currently have, or find
a more current SPR that includes the function in both the SPR you are using
and the selected SPR. In the latter case, you could then add the more current
SPR to your Scout worksheet and perform another Search/Get SPRs
procedure.
If an emergency overlay was performed on your RVU after the SUT you installed
was created and you have not installed the same or more current SPRs, you might
find that Scout did not send you an SPR because it is already included in the RVU,
but that you actually do need it because it is not included in your software
configuration. If so, you should manually analyze such an SPR’s requisites needed
for your software configuration, add these SPRs to your Scout worksheet, and
perform a No Search/Get SPRs procedure.
You can obtain a list of SPRs added to an RVU because of an emergency overlay
through Scout.