Presentation is loading. Please wait.

Presentation is loading. Please wait.

CSULB EE400D Documentation Instructional Series

Similar presentations


Presentation on theme: "CSULB EE400D Documentation Instructional Series"— Presentation transcript:

1 CSULB EE400D Documentation Instructional Series
Preliminary Design Review

2 The Design Process Review
Design is an iterative process where the engineer must analyze the design (i.e., break apart, deconstruct), identify areas of greatest uncertainty, study (rapid prototype) possible solutions, and along the way eliminate poor or unsuitable solutions. Once the parts of a design are understood, the design can be synthesized (i.e., put back together, reconstructed) and the design studied as a whole (i.e., at the system level). Over the entire design process (analysis and synthesis) the criteria for making decisions are the mission objectives and requirements.

3 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 documentation was codified in the Project Plan The Preliminary Design Review presents how your design has proceeded to date with the goal of meeting these objectives and requirements.

4 Preliminary Design Review Guidelines
Power Point Presentation 20 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.

5 PDR Outline Title Page with Team Members and Division Assignment(s)
Mission Objectives/Profile Project Manager Requirements and Verification Program/Project Project Manager System/Subsystem System, Subsystem Engineers Systems/Subsystem Design System Engineer System Block Diagram(s) Interface Definitions Resource Reports Mass Budget Power Budget Bill of Materials Design and Unique Task Descriptions Subsystem Engineers The Design Process: sketches, back of the envelope, trade-off studies, models… Summary Cost and Schedules Project Manager Appendix: Sources

6 Title Page Team Member Names Division Assignments
Material Responsible for in the PDR

7 Clearly state Mission Objectives and Mission Profile

8 Level 1& 2 Requirements Requirement Evaluation Rubric
Is the requirement, Quantitative, Verifiable, and Realizable Is the requirement located at the correct level (1 – Program/Project or 2 – System/Subsystem) Is the requirement response to a higher level requirement or customer’s objective? Is the linkage clearly defined? Is requirement consistent with other requirements? Does requirement provide links to source material? Are equations used to calculate a requirement provided and are answers correct? Is language in the form of a requirement? Is a single requirement defined (i.e., breakup statements that contain multiple requirements)

9 Level 1& 2 Requirements Presentation Options
Level 1and Level 2 requirements with verification on separate slides. Level 1with drilled down Level 2 on same slide with verification on separate slides.

10 Level 1 and 2 Requirements with Verification on Separate Slides

11 Level 1 and 2 Requirements with Verification on Separate Slides – Continued

12 System and subsystem Design Block Diagram

13 Interface Definition Design examples
Your system interface definitions can take many forms including schematic(s) and tables.

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

15 Resource Quiz What is wrong with this table?

16 Design Unique Task Descriptions The 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

17 task descriptions examples

18 task descriptions examples

19 task descriptions examples
Rapid Prototyping Example

20 Cost and schedule Bill of Materials Schedule with tasks By person

21 Cost and schedule examples
What is wrong with this table?

22 Cost and schedule examples

23 Appendix Sources for outside information.

24 appendix examples

25 Summary Focus On Do Not Show Product Pages
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

26 Resources Introduction to Engineering Design and Problem Solving
Design Synthesis Preliminary Designs PDR Outline Document F'14.pdf PDR Grading Criteria


Download ppt "CSULB EE400D Documentation Instructional Series"

Similar presentations


Ads by Google