CSULB EE400D DOCUMENTATION INSTRUCTIONAL SERIESPRELIMINARY DESIGN REVIEW

PRELIMINARY DESIGN REVIEW

• The Preliminary Design proceeds from a clear definition of the

• Mission Objective(s) and Profile

• Program/Project Level 1 Requirements/Verification

• System/Subsystem Level 2 Requirements/Verification

• This material was codified in the Preliminary Design / Project Planning Blog Post.

• The Preliminary Design Review presents how your design has proceeded to date with the goal of meeting these objectives and requirements.

PRELIMINARY DESIGN REVIEW GUIDELINES• Power Point Presentation

• 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.

• Have simple and uncluttered visual materials.

• Do not put too much information on one visual.

• Plagiarism – Provide source for all visuals, text, block diagrams, etc.

PDR OUTLINE• Title Page with WBS Project Manager

• Mission Objectives/Profile Project Manager

• Requirements and Verification

• Program/Project Project Manager

• System/Subsystem System, Subsystem Engineers

• Design Innovation Project Manager

• Systems/Subsystem Design System Engineer

• Electronic System Design

• System Block Diagram(s)

• Interface Definitions

• Mechanical System Design

• System Resource Reports

• Mass Budget

• Power Budget

• Design and Unique Task Descriptions Subsystem Engineers

• The Design Process: sketches, back of the envelope, trade-off studies, models…

• Summary Schedule and Cost Project Manager

• Appendix: Sources

TITLE PAGE

• Team Member Names

• Division Assignments

SIMPLE ROBOT WORK BREAKDOWN STRUCTURE (WBS)

CLEARLY STATE MISSION OBJECTIVES AND MISSION PROFILE

LEVEL 1& 2 REQUIREMENTSREQUIREMENT EVALUATION RUBRIC

1. Is the requirement, Quantitative, Verifiable, and Realizable

2. Is the requirement located at the correct level (1 – Program/Project or 2 – System/Subsystem)

3. Is the requirement response to a higher level requirement or customer’s objective? Is the linkage clearly defined? Is requirement consistent with other requirements?

4. Does requirement provide links to source material?

5. Are equations used to calculate a requirement provided and are answers correct?

6. Is language in the form of a requirement?

7. Is a single requirement defined (i.e., breakup statements that contain multiple requirements)

LEVEL 1 REQUIREMENTS WITH VERIFICATION

LEVEL 2 REQUIREMENTS WITH VERIFICATION

SYSTEM AND SUBSYSTEM DESIGN BLOCK DIAGRAM

INTERFACE DEFINITION DESIGN EXAMPLES

• Your system interface includes your interface matrix and schematic(s).

RESOURCE REPORTS

• Resources that are important to your project need to be tracked over the life of the project.

• UFO Ab-ducted, BiPed, Spider, – Power and Mass

• Rover, ATechTop – Power

• Cost must be managed by all projects

• Over the life of the project; as simulations and experiments are run, trade-off studies completed, models and prototypes built and tested, you will be able to finalize your design. Until then, there will always be uncertainty. This level of uncertainty is managed by allocating margins to project resources. This may be done at the system, subsystem, and/or component level.

DESIGN UNIQUE TASK DESCRIPTIONSTHE DESIGN PROCESS

• Sketch of the Design Ideas

• Back of the Envelope Calculations

• Trade Off Studies

• Models

• Mathematical

• Computer Simulation

• Physical Models (Rapid Prototyping)

• Full-scale Prototypes

• Scale Models

TASK DESCRIPTIONS EXAMPLES

TASK DESCRIPTIONS EXAMPLES

TASK DESCRIPTIONS EXAMPLES

• Rapid Prototyping Example

COST AND SCHEDULE

• Bill of Materials

• Schedule with tasks

• By person

COST AND SCHEDULE EXAMPLES

COST AND SCHEDULE EXAMPLES

APPENDIX

• Sources for outside information.

APPENDIX EXAMPLES

SUMMARY• Focus On

• Original work – what you have learned

• Demonstration of the Engineering Method – From Objectives to Design

• Demonstrations with real hardware

• Do Not Show Product Pages

• Copied Promotional Text

• No linkage to Requirements

RESOURCES• Introduction to Engineering Design and Problem Solving

• http://www.csulb.edu/~hill/ee400d/UNCC%20Intro%20to%20Engr%20Design.pdf

• Design Synthesis

• http://www.olivenhain.com/files/docs/projects/Demo_Garden/Design_Synthesis.pdf

• Preliminary Designs

• http://www.csulb.edu/~hill/ee400d/Lectures/08_Preliminary%20Design.pdf

• PDR Outline Document

• http://www.csulb.edu/~hill/ee400d/Lectures/10_PDR%20Presentation%20New%20for%20F'14.pdf

• PDR Grading Criteria

• http://www.csulb.edu/~hill/ee400d/Lectures/10b_PDR%20Grading.pdf