1. EE400D DOCUMENTATION INSTRUCTIONAL SERIES CRITICAL DESIGN REVIEW

2. The purpose of the PDR is to present the “requirements” and conceptual design of your project. The purpose of the CDR is to present the “design” of your project. The next phase of the project should be implementation of this design, not further design.

3. CRITICAL DESIGN REVIEW GUIDELINES Power Point Presentation / submit to Beachboard 40 minute maximum duration Each person in the group should present their own work. Be familiar with the material, do not reed it from the overhead or from a sheet of paper Speak clearly, with authority, and eloquently Practice the presentation to ensure all topics are covered in the time allotted.

4. CDR OUTLINE – PART 1 OF 3 Title Page Executive SummaryProject Manager Project Objectives and Mission Profile Design with Illustrations Major Project Features (Specifications) System DesignAll Divisions Detailed System Block Diagram(s), with Summary of Design Solutions Experimental Results What you did to arrive at Design Solution for System, Subsystem, and Components Do experimental results and observations meet Design Requirements?

5. CDR OUTLINE – PART 2 OF 3 Systems/Subsystem Design Electronics Interface Definitions Breadboard(s), Fritzing, Schematics, PCB Layout Software – Specifications, Pseudo-code, or flowchart, C++ Hardware – 3D Models and prototype prints Verification and Validation Test Plans System and Subsystem, Hardware and Software Test Plan A few short paragraphs on your plans for verifying that your design meets design requirements and how you will validate that you built the right product for the mission. Verification and Validation Matrices

6. CDR OUTLINE – PART 3 OF 3 Project Work Breakdown Structure (Who is doing what?) Resource Reports (Mass, Power) Updated Cost Schedule Status – Fabrication Project Percent completion and/or Burn Down Diagram Project Demonstrations

7. TITLE PAGE/EXECUTIVE SUMMARY Title Page What are you presenting (i.e., Critical Design Review) Name of Project Stylized Photo, Illustration, 3D Model Project Members (Who is doing what?) Executive Summary Project Objectives and Mission Profile Preferred Design Annotated Photo, Illustration, exploded 3D model – Summary Level Major Project Features (Specifications) Key Features of the Design Implemented Innovative Design Features

8. TITLE PAGE What is missing?

9. EXECUTIVE SUMMARY PROJECT OBJECTIVE AND MISSION PROFILE What is missing?

10. EXECUTIVE SUMMARY PREFERRED DESIGN WITH ILLUSTRATION An annotated Photo, Illustration, or exploded 3D model showing the major subsystems/components of your design

11. Executive Summary Major Project Features (Specifications) What is missing? Talk about the key and/or innovative design features of your product

12. SYSTEM DESIGN Detailed System Block Diagram Walk the audience through each subsystem/component block and how they are interconnected (i.e., subsystem and interface descriptions)

13. EXPERIMENTAL RESULTS Trade-off Studies, Models, and Rapid Prototyping What you did to arrive at Design Solutions for System, Subsystem, and Components Computer Simulations including Solidworks, Simulink, Multisim, Matlab, LabVEIW, LTspice, etc Do experimental results and observations meet Design Requirements?

14. EXPERIMENTAL RESULTS

15. EXPERIMENTS What is missing?

16. EXPERIMENTS What is missing?

17. SUBSYSTEM DESIGN Electronics Interface Definitions Systems Engineer Breadboards, Fritzing Diagram, SchematicsElectronics and Control Engineers PCB LayoutManufacturing Engineer Hardware System and Component 3D Models Prototype Prints

18. UPDATED INTERFACE DEFINITION

19. ELECTRONICS DESIGN Breadboards, Fritzing Diagram, Schematics…

20. SUBSYSTEM DESIGN PCB Layout Example

21. SUBSYSTEM DESIGN Hardware Examples

22. SOFTWARE DESIGN SpecificationsSystems Engineer Android App, Arduino Command and TelemetrySystems Engineer Present any pseudo-code and/or flowcharts which provide an overview of the software as well as sample C++ Code highlighting your code. Subsystem Electronics and Control Engineers Present any pseudo-code and/or flowcharts which provide an overview of the software as well as sample C++ Code highlighting your code.

23. SOFTWARE DESIGN Code Snip-it

24. VERIFICATION AND VALIDATION TEST PLANS Review NASA System Engineering Handbook and Verification and Validation lectureVerification and Validation System and Subsystem, Hardware and Software Test Plan A few bullet points on your strategy for verifying that your design meets design requirements and how you will validate that you built the right product for the mission. Verification and Validation Matrices

25. VERIFICATION AND VALIDATION TEST PLANS A few bullet points on your strategy for verifying that your design meets design requirements and how you will validate that you built the right product for the mission. What is missing?

26. PROJECT Work Breakdown Structure (WBS) Resource Reports Mass Power Updated Cost Schedule Status Update Schedule Project Percent Completion/Burn Down Diagram (if available)

27. PROJECT STATUS RESOURCE REPORTS What is missing?

28. PROJECT STATUS Schedule Status Example

29. PROJECT STATUS What is missing?