RECOVERY

К оглавлению
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 
17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 
34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 
51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 
68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 
85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 
102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 
119 120 121 122 123 

Assumption: The Unit Tests were properly constructed, and each associated

group of units constituted an appropriate subsystem.

Pull together all the subsystem tests:

Check the traceability of each unit and unit test to the appropriate subsystem.

Check the inputs and outputs of each subsystem.

Check the interfaces and interface compatibility of each interfacing subsystem.

Check the loads of each subsystem.

Make changes as necessary.

Modify the system test as necessary and recheck the traceability to the

requirements.

61 CONFIGURATION MANAGEMENT

61a (NO) The Configuration Management Plan (CMP) is not

thorough, complete, or authorized.

The Configuration Management Plan (CMP) is not thorough, complete, or

authorized unless it follows the required format and maintains the required

content as specified in customer or company configuration management policy.

Further, the CMP is not authorized unless it is signed by an authority that is

authorized to sign such documents (usually the vice president or director of

engineering or an equivalent position).

The Configuration Management process could easily be looked upon as the

Janus process. Remember the Roman god Janus who looked both backward

and forward? That’s what the configuration management process does. It looks

backward to the baseline, as established, and forward to the test process that

will prove the viability of a change.