BEST PRACTICES FOR ENGINEERING DESIGN

by Donald F. Elger

Goal

As related to student projects such as this one, summarize the best ideas for success.

Method

During the past ten years, we have observed many different teams engaged in engineering design projects.  Each team has reported what has worked and what has not.  Most teams report the same basic ideas--these best ideas are summarized below.

Results 

best practice 1:  apply the concept of iteration

To invent an airplane, the Wright brothers followed a systematic approach.  In 1899, they designed a biplane kite, built it, tested it and learned from this experience.  In 1900, they designed a glider, and repeated the design, construction, testing and learning cycle.  In 1901, they built another glider.  After a number of design, build and test iterations, their efforts culminated with he first successful manned flight on December 17, 1903.  We label the systematic process of the Wright brothers as "the concept of iteration"

To complete this project, use the concept of iteration.  

Iteration cycle #1: Develop a design using basic math modeling for sizing the chute.  Build a chute.  Test the chute and compare predicted performance with actual performance.  Learn!  During the 1st iteration cycle, keep everything simple!  

Iteration cycle #2:  Using knowledge gained from the first iteration, repeat the design, build and test cycle.  To keep required time requirements down, take time to plan prior to building.

Iteration cycle N:  On each iteration cycle, strive for performance improvement and knowledge gain.   For most projects, use a minimum of 2 to 3 iteration cycles.  

best practice 2:  prototype early

Build a prototype early.  This will reveal the real problems that need to solved. 

best practice 3: use engineering science to inform decision making

Use simple mathematical estimates to find key specifications.  Avoid calculations that are too complex.  Use the concept of iteration to develop math models.  That is, first develop simple models and make sure they are correct.  Then if necessary, develop more sophisticated models.

best practice 4: agree to work as a team

Each person commits to the idea of collaboration. Set rules--for example, agree to come to meetings on time, to be on-task at meetings, to be responsible for tasks and to participate.  At meeting, use an agenda and stay on task.  Agree to get input from each team member.  Share work on tasks (e.g. math modeling) together.  In general, seek to blend each persons best ideas and skills--this is called synergy.

best practice 5: set clear and challenging goals

As a team, set goals that are well understood and are challenging.  For example: (a) win contest, (b) learn engineering process, (c) best looking design, (d) excellent team performance, etc.

best practice 6: good documentation

Documenting work as it is done fosters communication and good engineering.  Furthermore, this practice facilitates final reporting.  

best practice 7: open up the design space

When formulating design ideas, try to think of many different possible solutions.  If one can think of only a few ideas, it is unlikely that one of these ideas will be a good idea.  Alternatively, if one can think of thirty ideas, it is much more likely that one of the ideas is a good idea.

A young engineer has a tendency to fixate on one idea that usually comes into his head early in the design process.  This idea will seem so good that this engineer will lose all ability to think about other ideas or to hear other's ideas.  We call this phenomenon "lock-on,"  because it resembles the tracking of a heat-seeking missile.  Avoid lock-on like you would avoid the black plague.