Project Name System Critical Design Review

1
Project NameSystem Critical Design Review
Insert project logo

• Class Number Title
• Date
• Location

2
Topics

• Project Overview
• System Overview
• System Element 1
• System Element 2
• System Element 3
• Management Overview
• Supplemental Slides

3
Project Overview

• Project Mission Statement
• One paragraph statement of the overall goal
  (general attributes) of the project. This is a
  high-level summary statement (few specific
  details).
• Project Technology Demonstration
• What are the key technologies to be demonstrated
  in the project
• Project Objectives
• List objectives (specific attributes) to define
  the mission statement. These are lower-level and
  more specific than the Mission Statement.

4
Project Overview

• Project Success Criteria
• What will be the minimum set of testable outcomes
  to declare the project a success
• Relevance to Sponsor
• What are the reasons that the sponsor should
  support the project (what will it do for the
  sponsor?)

5
Project Overview

• Project-level Requirements
• Project success and other programmatic criteria
  turned into a set of specific, testable
  statements. If programmatic criteria come from a
  specification document that must be met,
  reference the document. List these requirements
  in a table.

6
System Overview
System Block Diagram/Graphic

• Itemize the major system elements and a brief
  statement of their function

7
System Overview
Graphic to illustrate system operational phases
8
Project System Element Risk Assessment
9
System Element 1

• System Element Description
• For each major system element, give a detailed
  description of the main function it is to
  perform.
• System Element Success Criteria
• For each major system element, give a detailed
  listing of success criteria

10
System Element 1

• System Element Requirements
• Testable requirements tied to project-level
  requirements for the 1st system element

11
System Element 1

• Subsystem Listing
• For each major system element, list the
  subsystems to comprise that system element. Use
  WBS numbering to identify them.
• Include a block diagram showing the relative
  relationship between the subsystems and any
  signals that can be defined

Graphic capturing the Conceptual Design Diagram
for the system element
12
System Element 1
Subsystem block diagram/graphic

• Subsystem Definition
• Describe the function(s) to be performed by the
  ith subsystem of system element 1
• Describe any operational phases or timings
  relevant to the subsystem
• Subsystem I/O (power and/or signals)

13
System Element 1

• Subsystem Requirements
• Testable requirements tied to system element
  requirements for the ith subsystem of system
  element 1

14
System Element 1
Insert a graphic showing the Part Configuration
for this subsystem.
15
System Element 1
Insert the data from the Parametric Design.
16
System Element 1
Detailed schematics/drawings/flow charts, etc.
17
System Element 1

• Support Analysis/Data
• Power needs (nominal, worst case)
• Mass budget, form factor restrictions
• Thermal considerations/mitigation
• Safety factors (vibration, mass, wire gauge,
  fasteners, etc.)
• Regulatory issues (code specifications,
  regulatory specifications, etc.) that must be
  met status of any relevant applications,
  licenses, or reviews

18
System Element 1

• Hardware/software status
• If any hardware/software has been developed to
  test design concepts, show results here
• Indicate any potential design delays (long lead
  items, etc.) here.

19
System Element Subsystem Risk Assessment
20
Management Overview

• Organizational Chart
• WBS
• Schedule
• IT Summary
• Budget
• Detailed Risk Assessment and Mitigation

21
Organizational Chart
Show an organizational chart with lines of
reporting for team members. Also indicate
advisors/helpers
22
WBS

• WBS
• Project Work breakdown Structure

23
Schedule

• Schedule
• Show expected time line for the project (can be
  done as a Gantt chart)
• Use the WBS from the preceding slide

24
I T Summary

• IT Overview
• Describe the approach to how IT will be
  accomplished
• IT Flow
• Describe the flow of the IT from unit level to
  final acceptance testing

25
Budget

• Budget
• Personnel and resources budget for developing the
  project

26
Detailed Risk Assessment and Mitigation
27
Documentation

• The following documents are suggested to be ready
  at the time of the Critical Design Review
• Finalized Parts List and Materials List.
• Finalized Operations Concept Document
• Finalized Interface Control Document
• Finalized Integration and Test Plan
• Finalized budgets power, mass, size,
  communications links, etc.
• Finalized Requirements Matrix and Requirements
  Document