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 and use an In-process Review Approval sheet containing information

similar to Figure 5-3.

F i g u r e 5 - 3 — I n - P r o c e s s R e v i e w A p p r o v a l F o r m

IN-PROCESS REVIEW APPROVAL FORM

The ___(1)____ In-Process Review Minutes containing

the __(1)_____In-Process Review Package

labeled ___(2)_______ and

dated ____(3)_______

and

The __(1)___In-Process Review

conducted on ___(3)_______ together with the In-Process Review Action Items are

hereby approved

therefore

____(4)____ is hereby directed to proceed to the next stage of the program.

Signed ___(5)_____ of ______(6)________ Date _______________

55 PROTOTYPES

55a (NO) The prototypes do not reflect the requirements.

The prototypes do not reflect the requirements when the customer or client

does not agree that the prototype satisfies or demonstrates the requirements.

This is perhaps subjective, but is the nature of prototyping. It is common in

the prototyping process that the customers have new or added requirements or

have changed their minds. This is fundamental to the prototyping process.

When this happens, the product and the requirement must be compared and if

they do not agree, the product must be reworked until they do agree or the

contractual agreement must be modified.

The best way to eliminate subjectivity is to conduct a physical or functional

audit. For a detailed description of functional configuration audits and physical

configuration audits, see MIL-STD-1521. These audits are essentially physical

and functional inventories against the requirements.

There is a dichotomy inherent in the prototyping process. While it is a quick

way to get a technical result and customer feedback, it is fraught with programmatic

problems. This is due to the fact that technical people are talking to

technical people, both wanting to solve the issue technically, usually without

regard to the programmatic issues. The differences lie in what you (your project)

have agreed to provide. It is not uncommon for a project to start with a

general set of technical requirements and agree to provide X number of manhours

to achieve that result. Even though the technical requirement may not

have been met, the contractual requirement may be met.