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 

Create a version system and a Version Description Document where:

The general convention for document versions is:

X.YZ

Where: X _ Major issue or re-issue containing fundamental changes.

Y _ Minor change containing use changes or additional modules.

Z _ Minor use changes or documentation clarifications.

If you do not have a procedure for Version Description Documents, you can

use DID DI-IPSC-81442 as a guideline. Its contents are as complete as any one

document can get. The outline follows (the headings without content should be

self-evident. If you need further direction, refer to the DID):

1. Scope

1.1 Identification

1.2 System overview

1.3 Document overview

2. Referenced documents

3. Version description

3.1 Inventory of materials released

3.2 Inventory of software contents

3.3 Changes installed

3.4 Adaptation data

3.5 Related documents

3.6 Installation instructions

3.7 Possible problems and known errors

4. Notes

A. Appendices

Additional Resources:

MIL-STD-973

DID DI-IPSC-81442

62 SYSTEM EFFECTIVENESS FACTORS

62a (NO) All required System Effectiveness Factors3 have not been

appropriately considered.

All required System Effectiveness Factors have not been appropriately considered

unless all the necessary System Effectiveness Factors have been appropriately

considered in both the product and the processes.

RECOVERY

Certainly, not all the System Effectiveness Factors are required for every project

but they are often overlooked. Table 5-14 groups the System Effectiveness

Factors into their usual primary organizations.

The larger a parent organization, the more likely the second listed organization

will be a separate organizational element. This is important because, if

System Effectiveness Factor is a distinct organizational element, its function is

more likely to be addressed. When these functions are ‘‘buried’’ in engineering,

T a b l e 5 - 1 4 — S y s t e m E f f e c t i v e n e s s P a r e n t O r g a n i z a t i o n

System Effectiveness Factor Usual Parent Organization

Reliability Engineering or Reliability & Maintainability

Maintainability Engineering or Reliability & Maintainability

Vulnerability/Susceptability Engineering or Electro Magnetic Interference

Transportability Engineering(1) or Transportation(2)

Supportability Engineering or Logistics

Producibility Engineering or Manufacturing

Quality Quality

1 When transportability is a function of the product (i.e., a communications shelter).

2 When transportability is a function of delivery of the product to its destination.

the likelihood is greater that they will be glossed over or even ignored. These

functions must be addressed even in the smallest organizations. The most economical

way to accomplish this task is to designate a person to be responsible

for each of the applicable System Effectiveness Factors and to question or defend

that function during reviews. The project manager must ensure that all the

required System Effectiveness Factors are addressed in all processes. This is particularly

true in Design Reviews.

Notes

1. Defined as the smallest stand-alone component that produces a definable output

from a definable input. The unit may be hardware or software. In the case of hardware,

power can be external (i.e., a separate unit).

2. Loads are stresses placed upon a system. Loads are those stresses in units typical

for the product such as pounds, watts, ergs, number of subsystems, number of users,

number of executions per second, I/O rates, number of queries per second, etc.

3. The System Effectiveness factors refer to Reliability, Availability, Maintainability,

Supportability (including Logistics), Susceptibility, Producibility, Human Engineering,

Safety, and Security.

TEAMFLY