|
The objectives of PDR are to
demonstrate through presentation and support material that the program
understands its requirements and has developed a preliminary design that
fulfills the requirements.
The following items are
complete (to PDR level of development) and typically provided as read
material. Read package may also contain analysis material, trade studies,
etc. (i.e., Technical Memos)
System Specification
Segment Specification
Element Specification(s)
Interface Requirements Specifications IRS(s)
Software Requirements Specifications SRS(s)
System verification matrix and verification plan
System Integration & Test Plan
System Engineering Design Document (SEDD)
System/Sub-System Architecture
Block
Diagrams
Interface
Diagrams
Operations Concept Document (OCD)
System Behavior (Threads & Use Cases)
System Design/Cost Analysis
SFR Action Items
Completed
Mitigation Plan
Welcome
Program Overview
Program Processes
Security/P2
Program Staffing
Schedule
Entrance Criteria
System Introduction
System Architecture
Functions
OPSCON (Behavior) – L0 Thread
Thread Mapping
Critical
Use Cases
Segment
Behavior Allocation
Timeline Allocations
TPMs
Risk
Segment Design Description (segment responsibility)
|
Design Description Element
|
Expectations
|
|
System Architecture
|
The segment should present
the key design areas of their system; Functional, Hardware and Software. Each
area should be presented graphically as an architectural diagram. Each will
be expanded upon during the Functional, Hardware and Software segments of
the PDR presentation. Sub-Segment Architecture Diagram Hardware
Implementation & Deployment Diagram Software Implementation &
Deployment Diagram
|
|
Context Diagram
|
The segment should present a
context diagram illustrating where their segment functionally, physically
and logically (SW) fits within the larger system.
|
|
Interface Diagram
|
The segment should present
an interface diagram illustrating the physical and logical interfaces with
entities outside the segment.
|
|
Functional Architecture
|
The segment should
demonstrate they understand the functions required of their system. The
segment should present the allocations of functions to HW and SW elements
of the design.
|
|
Key Function(s) Design
|
The segment should
demonstrate they understand the driving requirements of their segment that
support the overall program.
|
|
Requirements
|
The segment should
demonstrate the flow down and understanding of system level requirements to
Segment and Element.
|
|
OPSCON
|
The segment should
demonstrate they understand the necessary behavior of their segment in
support of program requirements and in conjunction with other segments.
|
|
Risk
|
The segment should
demonstrate they understand and are managing identified areas of design and
development risk.
|
|
Systems Analysis and Studies
|
The segment should demonstrate
they have performed, with adequate rigor, the analysis of their preliminary
design. The segment should present design trades and supporting material
for design decisions.
|
|
Design Margins
|
The segment should present
design analysis demonstrating design closure and indicating design margin,
where applicable.
|
Development Assurance
Requirements Verification Plans & Status
Integration & Test
Software Engineering
Specialty Engineering
Reliability/Availability Allocations
Maintainability
Logistics
Safety
Program Wrap-Up
Actions from SRR
Items Closed
Mitigation Plans for Open Items
Plan to CDR
Exit Criteria
Government Caucus and Assessment
Government concurrence that
the Preliminary Design is complete and that the contractor has demonstrated
program has acceptable risk in proceeding into Critical Design phase.
|