A T T A C H M E N T 8

К оглавлению
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 

REQUIREMENTS FLOWDOWN

MATRIX

You can look at a Requirements Traceability Matrix (RTM) as a horizontal

function and a Requirements Flow-Down Matrix (RFM) as a vertical function.

The RTM traces where a requirement appears in the overall process while the

RFM shows where a requirement has been allocated. Both apply to both prime

and subcontractors. The subcontractor versions are usually preceded with an

‘‘S’’ for differentiating between the two.

If you do not have a Requirements Flow-Down Matrix (or Plan), you can

use Table A8-1 as a start. Modify the table for your own needs. Just be sure to

not change the concepts of content and flow.

In the case of the RFM, there are two levels or sets of requirements to be

flowed down. The first is the requirement from the customer as contained in

T a b l e A 8 - 1 — R e q u i r e m e n t s F l o w - D o w n M a t r i x ( R F M )

Company Design S/C Plan S/C A S/C B

Spec Para Reqt WBS Plan Para Para Para Para

1.3.2 02-03-01 5.3.2 5.3.2 1.3.2 1.3.2

1.3.3 02-03-02 5.3.3 5.3.3 1.3.3 N/A

1.3.4 02-03-03 5.3.4 5.3.4 1.3.4 1.3.4

QA Plan 04-01-01 8.2.6 8.2.6 4.3.6 4.3.6

CM Plan 05-01-01 9.3.1 9.3.1 5.6.2 5.6.2

the SOW or specification. The second is a requirement demanded by enterprise

policy.

In some cases, a requirement may be flowed down to one subcontractor and

not another. Observe Spec Para Requirement 1.3.3 in the table cross-referenced

to Subcontractor B. Such requirements could be those that are product-specific;

perhaps Subcontractor A provides that kind of product but Subcontractor B

does not.