Sign In
  • Question

    Where can I find a template for an average Preliminary Design Review?


    The information noted below comes from the Defense Acquisition Guidebook PDR procedures and is a good reference for planning a PDR.  Within the document are embedded links specific to different preparatory functions you may need to execute as well as checklists to help guide your preparations.  Click on them for more information.  This document, and other PDR related information, can be found by accessing the Defense Acquisition Guidebook (first hyperlink below), and typing Preliminary Design Review in the search window in the upper right corner of the DAG window.  The document itself can be accessing by clicking on the second hyperlink below.


    Preliminary Design Review Procedure


    TBD in future release.

    Functional Discipline: 



    The Government Project Management Office conducts the Preliminary Design Review (PDR) when the Project Manager indicates the preliminary design has addressed and resolved critical, system-wide issues.  The PDR analyzes the adequacy and completeness of the design by reviewing the design representations (e.g., prototypes, models, scenarios) and obtaining feedback about them from relevant stakeholders and subject matter experts.  The design representation should outline the product components and their interfaces, and there should be traceability between requirements and design. The review ensures that a system can proceed into detailed design and can meet the stated performance requirements within cost, schedule, risk, and other system constraints.  Tailor the review to the technical scope and risk of the system, and address the PDR in the Systems Engineering Plan.


    For programs following the Sustainment framework, the Program Manager may (if the system is complex) conduct a PDR for each subsystem or configuration item, leading to an overall system PDR.


    For programs following the 5000.02 framework, the PDR shall be conducted at system level, either before or after Milestone B.  Refer to the BPD Tailoring Guide for the conditions regarding when the PDR occurs in relation to Milestone B, and how the BPD is tailored to reflect the decision made.

    Entry Criteria:

    Complete the following before beginning this procedure:

    • Software Development Plan (SDP)
    • Draft General Requirements Specification (GRS) or all of the following three documents:  Concept of Operations (ConOps); System Subsystem Specification (SSS); Software Requirements Specification (SRS)
    • Updated Requirements Traceability Matrix (RTM)
    • Draft Interface Requirements Agreement (IRA)
    • Draft Database Specifications (DS)
    • Draft Design Document (DD)
    • Draft Test Scripts for Component Validation and Integration
    • Schedule and Cost
    • “To-Be” Department of Defense Architecture Framework (DoDAF) products (e.g., AV-1, OV-1, OV-2, OV-3, OV-4, OV-5a, OV-5b, OV-6a, OV-6c, DIV-2, SV-1, SvcV-1, SV-2, SvcV-2, SV-4, SV-5a, SV-6, SvcV-6, SV-7, SvcV-7, StdV-1)

    Procedure Steps:  (These steps are not necessarily sequential.)

    1. PMO:  Prepare for the Technical Review.

    Prepare for the technical review using Plan the Technical Review Procedure.


    1. Program Manager:  Initialize Preliminary Design Review.

    The program manager assigns a team to participate in the preliminary design review and makes all of the project artifacts under configuration management available to the participants. Team members should include but are not limited to the following roles: Customers, Program Manager, Enterprise Architect, Software Engineer, Lead and/or Chief Engineer, Lead Functional Analyst, Requirement Analyst, Lead Designer, System Security Manager/Information Assurance Manager, Test Manager, Developer, and others.  The program manger assigns relevant stakeholders and subject matter experts to review elements of the preliminary design.


    1. Chief or Lead Engineer:  Perform Preliminary Design Review.

    Determine whether the hardware, human, and software preliminary designs are complete and whether the team is prepared to start detailed design and test procedure development.  Determine whether the design trace to the requirements is satisfactory.  Determine whether or not the subsystem requirements, preliminary design, plans for detailed design and test procedure development form a satisfactory basis for proceeding into detailed design and test procedure development.  Use the Preliminary Design Review Checklist.


    For review guidance, refer to the Review Meeting Guide.


    1. Project Configuration Manager:  Prepare and distribute minutes.

    Prepare the PDR minutes and distribute them after approval.  Track action items until closure.


    1. Program Manager:  Prepare and Peer Review PDR report (5000.02 framework only).

    If the program is following the 5000.02 framework, prepare the PDR report.  If the PDR occurred before Milestone B, the PDR report shall consist of recommended requirements trades based upon an assessment of cost, schedule, and performance risk.  Otherwise, the PDR report shall consist of requirements trades made based upon an assessment of cost, schedule, and performance risk.  Distribute the PDR report to the PDR participants for Peer Review.  Refer to the Peer Review Procedure.

    Exit Criteria:

    The following is a result of completing this procedure:

    • Determination whether to proceed into detailed design and test procedure development
    • PDR report (5000.02 framework only)
    • Updated “To-Be” DoDAF products (e.g., AV-1, OV-1, OV-2, OV-3, OV-4, OV-5a, OV-5b, OV-6a, OV-6c, DIV-2, SV-1, SvcV-1, SV-2, SvcV-2, SV-4, SV-5a, SV-6, SvcV-6, SV-7, SvcV-7, , SV-10a, SV-10b, SV-10c, SvcV-10a, SvcV-10b, SvcV-10c, DIV-3, StdV-1)

    Open full Question Details
Chat with DAU Assistant
Bot Image