Reading:

Section 6.1-6.2 in textbook by Mattson and Sorensen

Download

• Lecture slides
• Template for design outcomes and design activities Excel or PDF

What are we going to do in this course?

In ME 493 you will work in teams to complete a major engineering design project. Using the terminology of the textbook, teams should be fully engaged in the Subsystem Engineering and Product Refinement phases described in Chapter 6 and Chapter 7.

As the term "subsystem" suggests, the team works to evolve the engineering design of components that, when assembled into a whole system, perform functions to meet the client needs. Testing of subsystems should be used to confirm that the subsystems meet performance requirements. Assembly of subsystems into a full prototype allows testing and verification that the system meets the customer requirements.

Learning Objectives for this class

After completing the activities in this class, students should be able to

• List at least two key performance metrics to focus on during the coming week
• Identify a measurement (evaluation) plan to determine whether the subsystem design meets the performance metrics
• Estimate the time and resources required to measure (evaluate) subsystem performance
• Identify the design activities necessary to specify subsystem features in a way that meets subsystem performance goals
• Estimate the time and resources required to design the subsystem

The list of learning objectives is in reverse chronological order: from the outcomes back to the actions necessary for achieving those outcomes.

Current Tasks for Teams

1. Assess status of your project
   • Review the Gantt chart to
     • Make sure it is accurate (updating as necessary), and
     • Assign team members to projects related to subsystems
   • Anticipate delays in ordering parts
   • Work in parallel on tasks
   • Use weekly meetings to coordinate tasks and make decisions
2. Meet with your sponsor for a design review
   • Find date to meet
     • Set time for meeting
     • Develop agenda and send it to the sponsor at least 5 days in advance
     • Plan for your presentation – don't wing it at the meeting
   • Present conceptual design
   • Confirm plans (and scope) for prototype development, including the budget
3. Shift to subsystem engineering (if you haven't already)
   • Work in parallel – assign subsystems to different groups or individuals
   • Establish interfaces between subsystems
     • Exchange of energy (or power)
     • Exchange of material
     • Exchange of control
   • Develop testing plan to make sure each subsystem meets its performance requirements
   • Plan for system integration and testing
4. Review and execution of documentation plan
   • Review and either affirm or change current info/document management
   • Write mini-reports for each activity. Mini-reports become sections of the appendix
   • Document lessons learned as you go

The Spring Term will pass quickly. I'm sure groups already feel the need to work effectively and to anticipate future deadlines. Working in parallel is crucial to the success of Capstone projects. Working in parallel requires

1. Trust
2. Good communication – regular updates
3. Mutual understand of system architecture