Preliminary Design Review (PDR) The following material was extracted from Section 40 of Mil. Std.

1521 (now withdrawn) to provide additional definitions for the format and content of the reliminar! "esign #eview ( "#). 40. reliminar! "esign #eview ( "#)
.

40.1 $eneral The reliminar! "esign #eview shall %e a formal technical review of the %asic design approach for a config&ration item or for a f&nctionall! related gro&p of config&ration items. 't shall %e held after the hardware s!stem hardware specification(s)( the )igh*+evel Software "esign( the Software Test lan (ST )( the ),-' Test lan( and preliminar! versions of the Software .ser/s Man&al (S.M) and -omp&ter S!stem "iagnostics are availa%le( %&t prior to the start of detailed design. 0or each config&ration item the actions descri%ed %elow ma! %e accomplished as a single event( or the! ma! %e spread over several events( depending on the nat&re and the extent of the development of the config&ration item( and on provisions specified in the contract Statement of ,or1. 2 collective "# for a gro&p of config&ration items( treating each config&ration item individ&all!( ma! %e held when s&ch an approach is advantageo&s to the contracting agenc!3 s&ch a collective "# ma! also %e spread over several events( as for a single config&ration item. The overall technical program ris1s associated with each config&ration item shall also %e reviewed on a technical( cost( and sched&le %asis. 40.2 'tems to %e #eviewed. The contractor shall present the following for review %! the contracting agenc!4 40.2.1 ),-'s4 a. reliminar! design s!nthesis of the s!stem hardware Specification for the item %eing reviewed. %. Trade*st&dies and design st&dies res&lts c. 0&nctional flow( re5&irements allocation data( and schematic diagrams. d. 65&ipment la!o&t drawings and preliminar! drawings.

e. 6nvironment control and thermal design aspects f. 6lectromagnetic compati%ilit! of the preliminar! design g. ower distri%&tion and gro&nding design aspects h. reliminar! mechanical and pac1aging design of consoles( rac1s( ca%les( connectors( etc. i. Safet! engineering considerations 7. Sec&rit! engineering considerations l. reliminar! 8ill of materials m. ertinent relia%ilit!9maintaina%ilit!9availa%ilit! data p. 'nterface re5&irements 5. -onfig&ration item development sched&le v. )&man 6ngineering considerations w. Standardi:ation considerations x. "escription and characteristics of -;TS )ardware rod&cts !. 6xisting doc&mentation : +ife -!cle -ost 2nal!sis

40.2.2 -S-'s4 a. 0&nctional flow. The comp&ter software f&nctional flow em%od!ing all of the re5&irements allocated from the Software #e5&irements Specification and 'nterface #e5&irements Specification(s) to the individ&al software mod&les of the -S-'. %. Storage allocation data. This information shall %e presented for each -S-' as a whole( descri%ing the manner in which availa%le storage is allocated to individ&al software mod&les. c. -ontrol f&nction description. 2 description of the exec&tive control and start9recover! feat&res for the -S-' shall %e availa%le( incl&ding method of initiating s!stem operation and feat&res ena%ling recover! from s!stem malf&nction. d. -S-' str&ct&re. The contractor shall descri%e the top*level str&ct&re of the -S-' and design rationale( the development methodolog! which will %e &sed within the constraints of the availa%le comp&ter reso&rces( and an! s&pport programs which will %e re5&ired in order to develop9maintain the -S-' str&ct&re and allocation of data storage. e. Sec&rit!. 2n identification of &ni5&e sec&rit! re5&irements and a description of the techni5&es to %e &sed for implementing and maintaining sec&rit! within the -S-' shall %e provided. f. #e*entranc!. 2n identification of an! re*entranc! re5&irements and a description of the techni5&es for implementing re*entr! ro&tines shall %e availa%le.

g. -omp&ter software development facilities. The availa%ilit!( ade5&ac!( and planned &tili:ation of the comp&ter software development facilities shall %e addressed. h. -omp&ter software development facilit! vers&s the operational s!stem. The contractor shall also provide details of the Software "evelopment +i%rar! controls. i. "evelopment tools. The contractor shall descri%e an! special sim&lation( data red&ction( or &tilit! tools that are not delivered &nder the terms of the contract( %&t which are planned for &se d&ring software development. 7. Test tools. The contractor shall descri%e an! special test s!stems( test data( data red&ction tools( test comp&ter software( or cali%ration and diagnostic software that are not delivera%le &nder terms of the contract( %&t which are planned for &se d&ring prod&ct development. 1. "escription and characteristics of -;TS prod&cts l. 6xisting doc&mentation m. S&pport reso&rces. The contractor shall descri%e those reso&rces necessar! to s&pport the software and firmware d&ring operational deplo!ment of the s!stem( s&ch as operational and s&pport hardware and software( personnel( special s1ills( h&man factors( config&ration management( test( and facilities9space. n. ;peration and s&pport doc&ments. The preliminar! versions of the S.M and programmers man&al shall %e reviewed for technical content and compati%ilit! with the top*level design doc&mentation. o. .pdated since the last review to all previo&sl! delivered software related -"#+ items.

40.2.< S&pport 65&ipment (S6)4 a. #eview considerations %. =erif! testa%ilit! anal!sis res&lts

e. #eview progress toward determining total S6 re5&irements for installation( chec1o&t( and test s&pport re5&irements. f. #eview the relia%ilit!9maintaina%ilit!9availa%ilit! of s&pport e5&ipment items. g. 'dentif! logistic s&pport re5&irements for s&pport e5&ipment items and rationale for their selection. 1. 'f a +ogistic S&pport 2nal!sis (+S2) is not done( then review the res&lts of S6 trade*off st&dies for each alternative s&pport concept..

40.< 6val&ation of "etail "esigns.

40.<.1 ),-'s

a. "etermine that the preliminar! detail design provides the capa%ilit! of satisf!ing the performance characteristics paragraph of the ),-' "evelopment specifications. %. 6sta%lish compati%ilit! of the ),-' operating characteristics in each mode with overall s!stem design re5&irements if the ),-' is involved in m&lti*mode f&nctions. c. 6sta%lish the existence and nat&re of ph!sical and f&nctional interfaces %etween the ),-' and other items of e5&ipment( comp&ter software( and facilities.

40.<.2 -S-'s.

a. "etermine whether all interfaces %etween the -S-' and all other config&ration items %oth internal and external to the s!stem meet the re5&irements of the Software #e5&irements Specification and 'nterface #e5&irements Specification(s). %. "etermine whether the top*level design em%odies all the re5&irements of the Software #e5&irements Specification and 'nterface #e5&irements Specification(s). c. "etermine whether the approved design methodolog! has %een &sed for the top*level design. d. "etermine whether the appropriate )&man 0actors 6ngineering principals have %een incorporated in the design. e. "etermine whether timing and si:ing constraints have %een met thro&gho&t the top*level design.

40.5 "esign #elia%ilit!. 40.5.1 'dentif! the 5&antitative relia%ilit! re5&irements specified in the hardware "evelopment and Software #e5&irements Specification(s)( incl&ding design allocations( and the complexit! of the -S-'s. 40.5.2 #eview fail&re rate so&rces( derating policies( and prediction methods. #eview the relia%ilit! mathematical models and %loc1 diagrams as appropriate. 40.5.< "escri%e planned actions when predictions are less than specified re5&irements. 40.5.10 #eview elements of relia%ilit! program plan to determine that each tas1 has %een initiated toward achieving specified re5&irements. 40.> "esign Maintaina%ilit!.

40.>.1 'dentif! the 5&antitative maintaina%ilit! re5&irements specified in the hardware "evelopment and Software #e5&irements Specifications3 if applica%le( compare preliminar! predictions with specified re5&irements. 40.>.2 #eview ),-' preventive maintenance sched&les in terms of fre5&encies( d&ration( and compati%ilit! with s!stem sched&les. 40.>.5 #eview planned designs for accessi%ilit!( testa%ilit!( and ease of maintenance characteristics (incl&ding provisions for a&tomatic or operator* controlled recover! from fail&re9 malf&nctions) to determine consistenc! with specified re5&irements. 40.>.? #eview provisions for diagnosing ca&se(s) of fail&re3 means for locali:ing so&rce to lowest replacea%le element3 ade5&ac! and locations of planned test points3 and planned s!stem diagnostics that provide a means for isolating fa&lts to and within the config&ration item. 40.>.@ #eview for ),-'s the "esign for Maintaina%ilit! -hec1list to ins&re that listed design principles shall lead to a mat&re maintaina%ilit! design. "etermine that contractor design engineers are &sing the chec1list. 40.>.A 6val&ate for ),-'s the preliminar! maintaina%ilit! demonstration plan( incl&ding n&m%er of maintenance tas1s that shall %e accomplished3 accept*re7ect criteria3 general plans for introd&cing fa&lts into the ),-' and personnel involved in the demonstration. 40.>.10 #eview elements of maintaina%ilit! program plan to determine that each tas1 has %een initiated towards achieving specified re5&irements. 40.>.11 'ns&re that consideration has %een given to optimi:ing the s!stem9item from a maintaina%ilit! and maintenance viewpoint and that it is s&pporta%le within the maintenance concept as developed. 2lso( for ),-'s ins&re that a #epair +evel 2nal!sis (#+2) has %een considered. 40.? )&man 0actors. 40.?.1 The contractor shall present evidence that s&%stantiates the f&nctional allocation decisions. The #eview shall cover all operational and maintenance f&nctions of the config&ration item. 40.?.2 #eview design data( design descriptions and drawings on s!stem operations( e5&ipment( and facilities to ins&re that h&man performance re5&irements of the hardware "evelopment and Software #e5&irements

Specifications are met. 6xamples of the t!pes of design information to %e reviewed are4 a. ;perating modes for each displa! station( and for each mode( the f&nctions performed( the displa!s and control &sed( etc. %. The exact format and content of each displa!( incl&ding data locations( spaces( a%%reviations( the n&m%er of digits( all special s!m%ols ( ictographic)( alert mechanisms (e.g.( flashing rates)( etc. c. The control and data entr! devices and formats incl&ding 1e!%oards( special f&nction 1e!s( c&rsor control( etc. d. The format of all operator inp&ts( together with provisions for error detection and correction. e. 2ll stat&s( error( and data printo&ts * incl&ding formats( headings( data &nits( a%%reviations( spacing( col&mns( etc. 40.@ S!stem Safet!. 40.@.1 #eview res&lts of config&ration item safet! anal!ses( and 5&antitative ha:ard anal!ses (if applica%le). 40.@.2 #eview res&lts of s!stem and intra*s!stem safet! interfaces and trade* off st&dies affecting the config&ration item. 40.@.> $enerall! review ade5&ac! and completeness of config&ration item from design safet! viewpoint. 40.@.? #eview compliance of commerciall! availa%le config&ration items or config&ration item components with s!stem safet! re5&irements and identif! modifications to s&ch e5&ipment( if re5&ired. 40.1< Test. 40.1<.1 #eview all changes to the S!stem9S&%s!stem( ),-' "evelopment( Software #e5&irements( and 'nterface #e5&irements Specifications s&%se5&ent to the esta%lished 2llocated 8aseline to determine whether Section 4.0 of all these specifications ade5&atel! reflects these changes. 40.1<.2 #eview information to %e provided %! the contractor regarding test concepts for 'ntegration and Test ('BT) testing (%oth informal and formal). 'nformation shall incl&de4 a. The organi:ation and responsi%ilities of the gro&p that will %e responsi%le for test. %. The management of his in*ho&se development test effort provides for4 (1) Test Methods (plans9proced&res) (2) Test #eports (<) #esol&tion of pro%lems and errors (4) #etest proced&re (5) -hange control and config&ration management

(>) 'dentification of an! special test tools that are not delivera%le &nder the contract. c. The methodolog! to %e &sed to meet 5&alit! ass&rance re5&irements95&alification re5&irements( incl&ding the test repeata%ilit! characteristics and approach to regression testing. d. The progress9stat&s of the test effort since the previo&s reporting milestone. 40.1<.4 #eview interface test re5&irements specified in the s!stem hardware( Software #e5&irements( and 'nterface #e5&irements Specifications for compati%ilit!( c&rrenc!( technical ade5&ac!( elimination of red&ndant test. 'ns&re that all associated test doc&ments reflect these interface re5&irements. 40.1<.@ #eview plans for software .nit testing to ens&re that the!4 a. 2ddress .nit level si:ing( timing( and acc&rac! re5&irements. %. resent general and specific re5&irements that will %e demonstrated %! .nit testing. c. "escri%e the re5&ired test*&ni5&e s&pport software( hardware( and facilities and the interrelationship of these items. d. "escri%e how( when( and from where the test*&ni5&e s&pport items will %e o%tained. e. rovide test sched&les consistent with higher level plans. 40.1<.A #eview plans for -S- integration testing to ens&re that the!4 a. "efine the t!pe of testing re5&ired for each level of the software str&ct&re a%ove the &nit level. %. resent general and specific re5&irements that will %e demonstrated %! -S- integration testing. c. "escri%e the re5&ired test*&ni5&e s&pport software( hardware( and facilities and the interrelationship of these items. d. "escri%e how( when( and from where the test*&ni5&e s&pport items will %e o%tained. e. "escri%e -S- integration test management( to incl&de4 (1) ;rgani:ation and responsi%ilities of the test team (2) -ontrol proced&res to %e applied d&ring test (<) Test reporting (4) #eview of -S- integration test res&lts (5) $eneration of data to %e &sed in -S- integration testing. f. rovide test sched&les consistent with higher level plans. 40.1<.10 #eview plans for formal -S-' testing to ens&re that the!4 a. "efine the o%7ective of each -S-' test( and relate the test to the software re5&irements %eing tested. %. #elate formal -S-' tests to other test phases.

c. "escri%e s&pport software( hardware( and facilities re5&ired for -S-' testing3 and how( when( and from where the! will %e o%tained. d. "escri%e -S-' test roles and responsi%ilities. e. "escri%e re5&irements for $overnment*provided software( hardware( facilities( data( and doc&mentation. f. rovide -S-' test sched&les consistent with higher* level plans. g. 'dentif! software re5&irements that will %e verified %! each formal -S-' test. 40.20 ost #eview 2ction. 40.20.1 2fter completing the "#( the contractor shall p&%lish and distri%&te copies of #eview min&tes. The contracting agenc! officiall! ac1nowledges completion of a "#.