SMD PDR Template



DOWNLOADED AND/OR HARD COPY UNCONTROLLED

Verify that this is the correct version before use.

|APPROVAL SIGNATURES |DATE |

|Greg Blaney (original signature on file) |IMS Representative |06/11/2009 |

| | | |

|REVISION HISTORY |

|Revision |Description of Change |Author |Effective Date |

|Basic |Initial Release |Ken Vorndran |06/11/2009 |

| | | | |

|REFERENCE DOCUMENTS |

|Document |Title |

|IVV QM |IV&V Quality Manual |

|IVV 09-4 |Project Management |

|IVV 09-9 |Risk Management |

|S3106 |Portfolio Based Risk Assessment (PBRA) |

|NPR 7120.5 |NASA Space Flight Program and Project Management Requirements |

| | |

Purpose of Preliminary Design Review (PDR)

The purpose of the PDR is to demonstrate that the preliminary design meets all system requirements with acceptable risk and within the cost and schedule constraints, and that it establishes the basis for proceeding with detailed design. The PDR will show that the correct design options have been selected, that interfaces have been identified, and that verification methods have been described.

Purpose of the IV&V PDR Template

The purpose of this template is to provide a standard outline and format for an IV&V PDR presentation. This template is designed to provide standard sections that are used in all or most IV&V PDRs, as well as directions for content tailoring and guidance. This template applies to the PDR for each IV&V Science Mission Directorate (SMD) Project.

Context for the PDR

Before reaching the PDR phase, the IV&V Project may have the following items/actions completed or in place:

• Portfolio Based Risk Assessment (PBRA)

• IV&V coverage

• IV&V Project Execution Plan (IPEP)

• System Goals

• System Model

• Communication diagrams

• Some elaboration of behaviors

• Validated requirements (system/segment/element)

• Architecture analysis

• Verify software design/interface design

• Potentially some verify implementation

• Test design validation (scope only)

Additionally, the IV&V Project may be in a position to present any of the following:

• PBRA results

• Coverage provided

• Listing of system capabilities (desired/undesired behaviors/adverse conditions)

• Listing of services (provided/consumed)

• Work performed to date

• Goodness of product-related data/statements for work performed to date in capabilities/limitations

• Validated requirements

• Architecture analysis

• Design analysis

• Implementation analysis

• Test design validation analysis

• High-level plan for remaining IV&V efforts

• Risks

PDR Entrance Criteria

The criteria for deeming a PDR successful are as follows:

• Successful completion of the System Definition Review (SDR) or System Requirements Review (SRR) and/or Mission Definition Review (MDR), and responses made to all SDR or SRR and/or MDR Requests for Action (RFAs) and Review Item Discrepancies (RIDs), or a timely closure plan for those remaining open

• A preliminary PDR agenda, success criteria, and charge to the board that have been agreed to by the technical team, project manager, and review chair prior to the PDR

• PDR technical products listed below for both hardware and software system elements, available to the cognizant participants prior to the review:

– Updated baselined documentation (as required)

– Preliminary subsystem design specifications for each configuration item (hardware and software), with supporting trade-off analyses and data (as required

• The preliminary software design specification should include a completed definition of the software architecture and a preliminary database design description (as applicable)

– Updated technology development maturity assessment plan

– Updated cost and schedule data

– Updated risk assessment and mitigation

– Updated logistics documentation (as required)

– Applicable technical plans – e.g., technical performance measurement plan, contamination control plan, parts management plan, environments control plan, Electromagnetic Interference (EMI)/Electromagnetic Capability (EMC) control plan, payload-to-carrier integration plan, produceability/manufacturability program plan, reliability program plan, quality assurance plan

– Applicable standards

– Engineering drawing tree

– Safety analyses and plans

– System-level safety analysis

– Interface Control Documents (ICDs)

– Verification/validation plan

– Disposal plan

– Plans to respond to regulatory requirements – e.g., Environmental Impact Statement (as required)

– Technical resource utilization estimates and margins

– Preliminary Limited Life Items List (LLIL)

PDR Success Criteria

The criteria for deeming a PDR successful are as follows:

• Top-level requirements including mission success criteria, Technical Performance Measures (TPMs), and any sponsor-imposed constraints are agreed upon, finalized, stated clearly, and consistent with the preliminary design.

• The flow-down of verifiable requirements is complete and proper, or, if not, an adequate plan exists for timely resolution of open items. Requirements are traceable to mission goals and objectives.

• The preliminary design is expected to meet the requirements at an acceptable level of risk.

• Definition of the technical interfaces is consistent with the overall technical maturity and provides an acceptable level of risk.

• Adequate technical interfaces are consistent with the overall technical maturity and provide an acceptable level of risk.

• Adequate technical margins exist with respect to TPMs.

• Any required new technology has been developed to an adequate state of readiness, or back-up options exist and are supported to make them viable alternatives.

• Project risks are understood and have been credibly assessed, and plans, a process, and resources exist to effectively manage them.

• Safety and mission assurance – e.g., safety, reliability, maintainability, quality, and Electrical, Electronic, and Electromechanical (EEE) parts – have been adequately addressed in preliminary designs and any applicable Safety and Mission Assurance products – e.g., Probabilistic Risk Assessment (PRA), system safety analysis, and failure modes and effects analysis – have been approved.

• The operational concept is technically sound, and includes (where appropriate) human factors, as well as the flow-down of requirements for its execution.

IV&V PDR Template Conventions

Three different “styles” of text are used in this template:

1. [Text included in square brackets]

This text represents specific information to be provided. Examples are [Project name] for the name of the project, and [date] for the date of the presentation. Where this text appears, insert the requested information between the brackets, and then delete the brackets.

2. {Italic text in braces}

This text is guiding or explanatory in nature. It will include tailoring guidance and descriptions of the kinds of information to be included in each section. Therefore, this text should not be included in the final presentation.

3. Normal Text

Text that appears normal is typically common among IV&V PDR presentations. This is standard text that may be copied verbatim into the presentation, although it is suggested that it be tailored to fit each individual presentation. It represents any text that does not fit into either of the above categories.

These conventions are implemented on the following template.

To open the template for modification, right-click the object, select “Presentation Object”, and then select “Open” from the submenu. Once the presentation has opened in PowerPoint, the file can be edited and saved locally.

{Page intentionally left blank.

Template begins on the following page.}

[pic]

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download