ME401 Fall 2011
From Clemson Engineering Design Applications and Research
|
[edit] Official Syllabus Media:ME401-2011-08-Syllabus.pdf
[edit] Course Contact
- Professor: Joshua D. Summers
- Office: 250 Fluor Daniel Building
- Phone: 864.656.3295
- E-mail: [jsummer (at) clemson (dot) edu]
- Class: TR 9:30 - 10:45 in Lee 111
- Office Hours: TR 2:00 – 3:00 and by appointment
[edit] Prerequisites
C or better in ME 303, 304, 305, 306 (concurrent enrollment in one of these courses is permitted with departmental approval); C or better in English 314 (or Technical Writing); concurrent enrollment in ME 312. If you are missing more than one of these courses, please see the instructor immediately.
[edit] Special Accommodations
If special accommodations are required for the student, please see the professor so that proper arrangements may be made. If no requests are made of the instructor both in person and via e-mail within the first week of the class (by Friday, Aug. 26, 2011), then it will be assumed that no accommodations are needed for the rest of the semester.
[edit] Expectations
This course, like any other engineering course, will consume a significant amount of time every week. You should anticipate spending approximately six-seven hours a week working on the design project (individually), one hour a week in team meetings, and approximately one-two hours a week on individual writing assignments. This is approximately eight-ten hours a week outside of class. You will be expected to conduct yourself in a professional manner at all times. This course is evaluated across many different dimensions, but “time spent” is not one of them. My objective is to prepare you for success in both the capstone design course (ME 402) and in your professional career as an engineer.
[edit] Textbooks
Dieter, G., Schmidt, L., (2009), Engineering Design, McGraw-Hill Higher Education, Boston, MA, ISBN: 978-0-07-283703-2.
[edit] References
See the Library Reserves.
[edit] Course Description
Project-oriented course in mechanical engineering. Emphasis is on the role of analysis, synthesis, and evaluation in design and on written reporting of design solutions. Influence of economics and optimization, concurrent development, integration of design and manufacturing, and systems creation are utilized for engineering design decisions. Prerequisites: ME 303, 304, 305, 306, (concurrent enrollment in one of these courses is permitted with departmental approval), ENGL 314; Co-Requisite: ME 312.
[edit] Reports
All executive summaries and reports are to be submitted following the report templates that are posted on the course website (http://www.clemson.edu/ces/cedar).
- Papers are due at the beginning of class. Late submissions will be accepted with 10% deduction for each day.
- Papers are to be submitted in hard copy.
- All documents should be organized to support professional communication. They will be evaluated with respect to:
- Presentation (organization, clarity of writing)
- Content (frame of reference, breadth of discussion, depth of discussion)
- Analysis (critique, conclusions)
- Ethical behavior and professional standards are expected in this class. All work submitted is to be that of the individual student unless cooperative effort is authorized in specific instances. The College of Engineering and Science Honor Code will be observed. Refer to your student handbook regarding University policies on academic dishonesty. Any copying, plagiarism, or other unethical behavior will be referred to the appropriate authorities and a failing grade will be earned by the offending student.
[edit] Computer Usage
Word processing, spreadsheet, Internet, and mathematical computation utilities will be used by the students throughout the course.
[edit] Weighting for Grade
| CH | Description | Weighting |
|---|---|---|
| C | Case Analysis and Learning Essays | 30% |
| R | Project Presentation (Written and Oral) | 20% |
| T | Project People (Teamwork) | 10% |
| A | Project Product (Artifact) | 15% |
| D | Project Process (Intermediate Deliverables) | 20% |
| P | Class Participation and Assignments | 5% |
| Total | 100% |
[edit] Case Analysis and Assignments
Students will be expected to provide individual written critique of past senior design reports and projects with respect to different aspects of the process, presentation, and product throughout the semester. These case reviews and analyses are useful in providing students an opportunity to explore many different types of design projects in a limited amount of time. Moreover, this provides students with examples of both good and poor reports, allowing them to develop their own deeper appreciation for how to present their findings. Additionally, a challenge in learning about new design tools is the process of internalizing many different tools. To support this, we will explore numerous tools for different aspects of the design process and you will evaluate the tools applicability to the assigned design project and to the assigned senior design project (past ME 402) that you will evaluate in terms of reporting. In addition to case analysis reports, assignments will be made throughout the semester on an individual basis. These assignments are intended to reinforce the lessons that are being taught, to focus the students’ attention on different topics, and to prepare the students to be successful professional engineers.
[edit] Project (Presentation, People, Product, Process)
A single project will be assigned for development throughout the semester. This project has been solicited from outside of Clemson University and will provide students with a challenge that is of social interest. Furthermore, the course instructor will not serve as the primary customer of the end product, but an outside interested party will act as the customer. The project will be evaluated against four basic aspects: presentation, people, product, and process with different relative weights.
- Presentation: The reporting on the project should be professional (clear, concise, and correct) and should be structured appropriately. Elements of reporting will include: weekly executive summaries, mini-reports, bi-weekly design reviews, final design report, and final poster presentation. It should be noted that an engineer is only as good as (s)he is a communicator.
- People: Peer evaluations will be critical in evaluating the team and individual performance. Teamwork will be monitored throughout the project with expectations that each member be able to identify a specific deliverable for which they are primarily responsible.
- Product: The final solution will be evaluated from a technical and economic viewpoint. Without a strong final product, the team will be considered a failure. The solution should be well justified through supporting documentation and analysis.
- Process: The design process will be evaluated based on the appropriate application of design tools and whether or not the design team would be able to successfully apply the process to a different design problem. An important learning outcome from this course is the realization that engineering design is not accidental, but can be controlled to yield higher quality solutions than random happenstance.
[edit] Class Participation and Assignments
Class participation will be used to evaluate students’ contributions to the discussion aspects of the class. The course’s success is highly dependent on fully engaged learners, and as such participation will be incorporated into the students’ grades.
[edit] The Engineer's Creed
As a Profession Engineer, I dedicate my professional knowledge and skill to the advancement and betterment of human welfare. I pledge:
- to give the utmost of performance
- to participate in none but honest enterprise
- to live and work according to the laws of man and the highest standards of professional conduct
- to place service before profit, the honor and standing of the profession before personal advantage, and the public welfare above all other considerations
In humility and with need for Divine Guidance, I make this pledge.
[edit] Engineering Ethics (The Canons)
- Engineers shall hold paramount the safety, health, and welfare of the public in the performance of their professional duties.
- Engineers shall perform services only in areas of their competence.
- Engineers shall continue their professional development throughout their careers, and should provide opportunities for the professional and ethical development of engineers under their supervision.
- Engineers shall act in professional matters for each employer or client as faithful agents or trustees, and shall avoid conflicts of interest or the appearance of conflicts of interest.
- Engineers shall build their professional reputation on the merit of their services and shall not compete unfairly with others.
- Engineers shall associate only with reputable persons or organizations.
- Engineers shall issue public statements only in an objective and truthful manner.
- Engineers shall consider environmental impact in the performance of their professional duties.
[edit] Academic Integrity
As members of the Clemson University community, we have inherited Thomas Green Clemson’s vision of this institution as a ‘high seminary of learning.’ Fundamental to this vision is a mutual commitment to truthfulness, honor, and responsibility, without which we cannot earn the trust and respect of others. Furthermore, we recognize that academic dishonesty detracts from the value of a Clemson degree. Therefore, we shall not tolerate lying, cheating, or stealing in any form. In instances where academic standards may have been compromised, Clemson University has a responsibility to respond appropriately and expeditiously to charges of violations of academic integrity.
[edit] Tentative Schedule
This schedule is subject to change. Students are responsible for being aware of such changes.
| Week | Day | Topic | Reading | Assign | Due |
|---|---|---|---|---|---|
| 1 | 2010.08.19 (Thurs) | Introduction, Product Realization Process (large) | Chapter 1 | A1 | |
| 2 | 2010.0.24 | Design Process and Explanation of Case Analysis (large) | Chapter 2 | C1 | A1 |
| 2 | 2010.08.26 | Problem Definition (large) | Chapter 3 | P1 | |
| 3 | 2010.08.31 | Problem Definition (large) | Chapter 3 | C1 | |
| 3 | 2010.09.02 | Problem Definition (large) | Chapter 3 | P2 | |
| 4 | 2010.09.07 | QFD and Project Management (large) | Chapter | ||
| 4 | 2010.09.09 | Project Management (large) | Chapter | P3 | |
| 5 | 2010.09.14 | Function Modeling (large) | Chapter | ||
| 5 | 2010.09.16 | Idea Generation (large) | Chapter | P4 | |
| 6 | 2010.09.21 | Idea Evaluation (large) | Chapter | C3 |
[edit] Design Tools
- Process Overview
- Project Definition
- Requirements Checklist
- Product Definition and Specification
- Objective Tree
- Quality Function Deployment
- Function Structures
- Function Means Trees
- GANTT Chart
- Brainstorming
- Method 6-3-5
- Gallery Method
- C-Sketch
- Morphological Charts
- Pairwise Comparisons
- Decision Matrix
- Design Review Checklists
- Failure Modes Effects Analysis
[edit] Semester Project Information
- Sponsor Presentation of the Problem
- presentation presented to class
- predefined folder structure and collection of templates
- Contact information for [David Goodman]
[edit] Background Slides
| Last Name | First Name | Background | |
|---|---|---|---|
| Adams | Patrick | padams@clemson.edu | Adams |
| Black | Andrew | abblack@clemson.edu | Black |
| Broom | Cameron | cbroom@clemson.edu | Broom |
| Bruneau | Lauren | lbrunea@clemson.edu | Bruneau |
| Chapman | Zachary | zchapma@clemson.edu | Chapman |
| Collins | Bradley | collin7@clemson.edu | Collins |
| Davis | Nicholas | nadavis@clemson.edu | Davis |
| Douglas | Nicholas | ndougla@clemson.edu | Douglas |
| Dubbs | Blake | bdubbs@clemson.edu | Dubbs |
| Duffield | John | jduffie@clemson.edu | Duffield |
| Dulcie | Michael | mdulae@clemson.edu | Dulcie |
| Fenton | Teal | tfenton@clemson.edu | Fenton |
| Grieshop | Nicholas | ngriesh@clemson.edu | Grieshop |
| Hudson | Charles | chhudso@clemson.edu | Hudson |
| Huskey | Charles | chuskey@clemson.edu | Huskey |
| Johnson | Timothy | timothj@clemson.edu | Johnson |
| Lannan | William | wlannan@clemson.edu | Lannan |
| Linnerud | Blake | bjlinne@clemson.edu | Linnerud |
| Mack | Richard | rmack@clemson.edu | Mack |
| McCurry | Tierce | jmccurr@clemson.edu | McCurry |
| Mitchell | Christoper | cmitche@clemson.edu | Mitchell |
| Montgomery | Travis | tmontgo@clemson.edu | Montgomery |
| Parrott | Robert | rparrot@clemson.edu | Parrott |
| Pega | Mac | mpega@clemson.edu | Pega |
| Pritchett | Geoffrey | gpritch@clemson.edu | Pritchett |
| Rees | William | wrees@clemson.edu | Rees |
| Romness | David | dromnes@clemson.edu | Romness |
| Rubel | James | jrubel@clemson.edu | Rubel |
| Sanders | McIntyre | msander@clemson.edu | Sanders |
| Satterfield | Heather | hsatter@clemson.edu | Satterfield |
| Scanlan | James | jscanla@clemson.edu | Scanlan |
| Schmelzer | George | gschmel@clemson.edu | Schmelzer |
| Showers | Daniel | dshower@clemson.edu | Showers |
| Smith | Kyle | kyle2@clemson.edu | Smith |
| Stephens | Charles | cstephe@clemson.edu | Stephens |
| Stone | Kyle | kwstone@clemson.edu | Stone |
| Sweet | Tucker | tuckers@clemson.edu | Sweet |
| Wideman | Cameron | cwidema@clemson.edu | Wideman |
| Wray | David | dgwray@clemson.edu | Wray |
| Youngblood | William | wyoungb@clemson.edu | Youngblood |
[edit] Teams
| Team | Last Name | First Name | |
|---|---|---|---|
| A | Griffin | David | |
| A | Bowman | Mark | |
| A | Snider | Erica | |
| A | Vitou | Alex | |
| A | Williard | Forrest | |
| B | Rose | Ashley | |
| B | Pearson | Matthew | |
| B | Webb | Cody | |
| B | Lessem | Whitney | |
| B | Callaghan | Christopher | |
| B | Hazel | Jared | |
| C | Sutch | Matt | |
| C | Goldstein | Marc | |
| C | Corwin | Garrett | |
| C | Leland | Nicolas | |
| C | Stoker | William | |
| C | Kapousidis | Vasilios | |
| D | Harris | Ryan | |
| D | Songer | Joseph | |
| D | Brundrett | AJ | |
| D | Frye | Joshua | |
| D | Knight | Walter | |
| D | Akridge | Doug |
