1. Marcos Esterman, Associate Professor Industrial and Systems Engineering Department Rochester Institute of Technology marcos.esterman@rit.edu Multidisciplinary Senior Design I Problem Definition: Module 1

2. Agenda Some Introductory Comments Expected Outcomes by the End of Week 3  Clearly defined and agreed upon problem statement & project deliverables  Prioritized list of needs  Use scenarios  Engineering Requirements  Draft of project plan Tools & processes to develop expected outcomes

3. WHAT IS THE DESIGN PROCESS?

4. What you should walk away with… Detailed Design is about solving the correct problem  Elegant solutions to problems people don’t care about are meaningless  1 st 3-weeks are about asking the right questions Solution exploration is both divergent & convergent  Think ‘inside’ and ‘outside’ the box  Iterate, iterate, iterate  Float between needs, specification & solutions Most importantly, trust & work the process

5. Design Process: Take 1 Possible Solutions Less than Satisfied “Undesired” Performance “Desired” Performance Needs Problems Qualitative System Response Variables Quantitative Specifications System Functions Concept Selection Detail Design Target Specs Final Specs Achieved & Validated Specs Original Hardware Artifact Improved Hardware Artifact

6. Design Process: Take 1 Possible Solutions Less than Satisfied “Undesired” Performance “Desired” Performance Needs Problems Qualitative System Response Variables Quantitative Specifications System Functions Concept Selection Detail Design Target Specs Final Specs Achieved & Validated Specs Original Hardware Artifact Improved Hardware Artifact Qualitative Problem Space Quantitative Problem Space Physical Solution Space

7. Qualitative Problem Space Quantitative Problem Space Physical Solution Space Design Process: Take 1 (cont.) Key Take-Away: MSD Needs to be Event Driven We are Establishing a 3-week cadence for events So that you can finish in 32 Weeks!

8. The Design Process: Take 2 Finished Prototype! Concept Design Subsystem Design Subsystem Design Needs & Problems Modeling & Analysis Modeling & Analysis Modeling & Analysis Troubleshooting = PDCA

9. Let’s Begin the Journey!