Evaluation of the SCA generally requires a subjective assessment by the
manager. It is not reasonable to score the effort on the basis of the number
of sneak circuits detected, since the number present in the design is not
known. Some systems might contain many, others few. The analysis might be
compared to a routine medical examination. If a problem exists, it is
advantageous to detect it as early as possible. If, on the other hand, a
rigorous examination uncovers no anomalies, the patient has additional
assurance that he is in good health. Failure to find a problem, therefore,
does not necessarily characterize the rigor of the evaluation.
In his assessment of the SCA, the manager should critically review the
effort in relation to the activities, procedures, and reports agreed upon at
the beginning of the task. The final report should provide a thorough overview
of the work accomplished, and, in addition, it should be examined to determine
the adequacy of its response to the requirements listed in Table
TABLE 8. CHECKLIST FOR EVALUATING
Is the final report complete, and does it
contain the following information essential to its use as a
- General discussion of analysis techniques
- An itemization of the data base used in the analysis (including
all drawing numbers and revision letters thereto).
- A summary of reports, showing status of actions taken, and a copy
of each report.
- A complete statement of the partitioning method used.
- Network trees with identification of each element and
cross-references to the applicable design drawings. Each tree should
show the partition represented.
- A complete timing analysis, including definitions of all time
intervals analyzed for each portion, and a matrix showing the relative
switch states considered for each time interval.
- A master element cross-reference list, sufficient to allow any SCA
element to be readily