EE499
Fall Term 2005
Course Title EE Design
Time Tuesday and Thursday 11:00AM – 12:15pm
Room 255 FPAT
Instructor Arthur V Radun
Office Anderson Hall 689
Phone 257-4289
Email radun@engr.uky.edu
Office hours Tuesday 3:00PM – 4:00PM and Thursday 12:30PM – 1:30PM. You may stop by my office anytime (there is no guarantee I will be there) or make an appointment.
Text: Students will be required to identify texts, papers, applications notes, and other resources that they require. There is no formal text for this course. Course information including this syllabus is on the web at http://www.engr.uky.edu/~radun/EE499.
GOALS: This is the capstone design course for electrical engineering students. Multiple sections are offered each semester so that a student can elect to gain design experience in one of several areas. The student can elect to gain design experience in the area of their choice subject to the constraint they must work on a team. The common foundation for these courses foundation of this course is that they provide it provides practical hands-on design experience based on the core of the electrical engineering curriculum.
OUTCOMES:
Upon completion of this course students should demonstrate the ability to:
1. Effectively work in a group to develop and propose engineering solutions.
2. Apply previously acquired engineering principles as well as learn new principles in solving a large engineering design problem.
3. Communicate and thoroughly document the results of an engineering design project to the engineering community using a variety of media (report, web page).
4. An ability to apply knowledge of mathematics, science, and engineering.
5. Ability to design and conduct experiments, as well as to analyze and interpret data.
6. An ability to design a system, component, or process to meet desired needs.
7. An ability to function on multi-disciplinary teams.
8. An ability to communicate effectively.
9. A recognition of the need for, and an ability to engage in life-long learning.
10. An ability to use the techniques, skills, and modern engineering tools necessary for engineering practice.
Other information:
Projects must be substantial enough that it takes a team of more than one student to complete it in the available time. Your project can be either an approved project of your own choosing or it can be a project from the list below. You may assemble your own team for your project with the approval of the instructor. You will not be allowed to overstaff your project. It is best to start thinking and planning your project before immediately in order to maximize its success. The separate schedule (Excel file) lists tasks that you will have to complete and it should help you in your initial thinking and planning.
Electrical engineering design emphasizes the above outcomes in its philosophy. This fundamentally means that you will not be taught how to solve a specific problem but rather you will pick a problem and you and your team will solve it on your own. This will require that you and your team members work effectively together to develop and propose an engineering solution as opposed to having the instructor propose a solution for which you fill in the details. You will apply the knowledge of mathematics, science, and engineering that you already have instead of learning new mathematics, science, and engineering. If your knowledge is insufficient to solve your problem you will be required to put into practice your ability to engage in life-long learning, and learn what is required. This means reviewing your textbooks, going to the library, consulting the technical literature, and identifying knowledgeable individuals. Of course you are not to become a burden on such knowledgeable individuals and try to get them to develop and propose an engineering solution to your problem for you. Your goal is to be creative and thoughtful. The above philosophy will carry over into the experimental part of your project as well. You will have to design and conduct experiments and analyze and interpret data instead of being given a specified list of experiments to do with instructions telling you how to carry out the experiments.
What you will learn in class are the program management skills that are necessary to keep a large engineering design project on schedule and to meet its goals in the available time. This means establishing intermediate goals and a realistic schedule for completing the required work. You will learn to communicate your plans, progress, and problems to your program manager (the instructor) and to thoroughly document your results so that your progress relative to your schedule and established goals can be assessed. Many of the classes will be program progress review meetings of various types requiring you to give oral presentations. Some meetings will require formal presentations while others will only need informal discussions.
Industrial Advisors emphasizing different aspects of electrical and computer engineering; their names and affiliations are as follows:
Mr. Aubrey Page, Senior Principal Engineer, Raytheon Electronics Systems, Dallas, TX.75226
Dr. Paul Dolloff, Research and Development-Engineering Technology Consultant, East Kentucky Power Cooperative, Winchester, KY
Dr. Michael Lhamon, Senior Researcher, Lexmark International Inc., Lexington, KY.
Dr. Joseph Elias, Modeling Principal, Cypress Semiconductor, Lexington, KY.
Grading: Your grade will be determined by an assessment of the following deliverables (delivered to the instructor).
A big part of EE499 is the writing of reports and the giving of presentations.
|
Preliminary Proposal |
3% |
|
Proposal |
5% |
|
Proposal presentation |
2% |
|
Progress reports |
2% |
|
Design review package |
15% |
|
Design review presentation |
3% |
|
Capstone Design Report |
60% |
|
Final presentation |
5% |
|
Project Demonstration |
5% |
|
|
|
|
Total |
100% |
All deliverables are due as indicated on the separate schedule. Deliverables will not be accepted late, hand in what you have completed. You will collaborate with your team members, but each member must turn in their own copy of each written deliverable. The written deliverables from each team member may or may not be the same as that turned in by the other team members depending on how the work was divided up and the relative contribution to the results by each team member. The text of written deliverables cannot be hand written (use a word processor) though figures or equations may be hand written. Use a technical textbook as an example of how to use equations and figures in your writing. In addition, each team must email me an electronic copy of each deliverable that I can email to our industrial advisors to review. If the deliverable from a team are the same for each member I only need one electronic copy from that team. If one team member turns in a deliverable that is different from the rest of the team they must email me an electronic copy of what they turn in. Make arrangements to have hand written parts scanned. I have a scanner that can be used.
Each member of a team must present part of each oral deliverable and they must use power point unless they have extenuating circumstances and have made prior arrangements with the instructor.
Your preliminary proposal and proposal must include the following sections with section headings. You may use subheadings.
|
Introduction |
5% |
|
Description of the problem |
15% |
|
Proposed method of solution Detailed specification Block diagram |
20% |
|
Detailed list of intermediate goals |
20% |
|
Ghant/Pert chart (realistic schedule) |
20% |
|
Budget |
|
|
References |
5% |
|
Executive summary Include a list of show stoppers |
15% |
|
|
|
|
Total |
100% |
The proposal's executive summary must include a list and discussion of potential show stoppers, challenging problems that if not solved will mean the project will not be completed in the available time.
Your design review package must include the following sections with section headings. You may use subheadings.
|
Introduction |
5% |
|
Updated description of the problem |
2% |
|
Updated proposed method of solution Detailed specification Block diagram |
3% |
|
Updated Ghant chart (schedule) |
5% |
|
Design calculations |
20% |
|
Simulation results |
20% |
|
Schematic |
5% |
|
Component stresses |
20% |
|
Parts list Budget |
5% |
|
Executive summary Include a list of show stoppers |
10% |
|
References |
5% |
|
|
|
|
Total |
100% |
The design review package executive summary must include a discussion of the schedule and an assessment of whether you are behind, on, or ahead of schedule.
Your final report must include the following sections with section headings. You may use subheadings.
The following report format and development is designed to help student clarify and communicate their thinking in the design process, and allow for efficient and consistent grading of both individual and group efforts. An engineering notebook must be kept by all students as record of their individual contributions and progress in the design development.
1. Introduction (Problem identification and impact on society)
Suggested content:
(Motivation) In this section identify the problem to be addressed and explain why it is important.
(Impact) Explain the potential impact of the solution to other technologies and society.
(History of Similar Solutions) Present examples of similar/existing designs and solutions. Discuss differences between the proposed design and its approach to that which already exists.
2. Problem Statement (Solution formulation and design criteria):
Suggested content:
(Top-Level Solution) In this section describe the main function of the design and break it down into sub-functions/parts. A top-level diagram should be used to help explain the relation between the sub-functions and the complete design with a team effort.
(Criteria) Present/derive specific criteria for the overall design and each block in the top level. The specifications must be tied to the original problem. Experiments or other research may be needed before determining the specifications. An explanation of how these specification were determined must be included. The design criteria must incorporate realistic design constraints that include most of the following considerations: economic; environmental; sustainability; manufacturability; ethical; health and safety; social; and political.
(Testing) Procedures for how the final design/solution will be tested to verify it meets the design specifications.
3. Team and Work Organization (Teamwork and Timeline)
(Milestones) Describe main tasks that must be performed in order to complete the design. Present a timeline of completing the milestones.
(Team Issues) Describe the main responsibilities of each team member in completing the task.
(Peer Evaluations) Describe how the team members will evaluate each other (what are the criteria by which they will judge each other).
Sections 1, 2, and 3 should be complete by mid-semester, reviewed by faculty coordinator and industrial advisor and returned to student teams with comments. Comments must be responded to and the edited versions of these sections must appear in the final report. A tentative grade can be assigned at this point and either averaged with or replaced by the grade of these sections in the final report.
4. Solution (Design Process)
Suggested Content:
Describe the design process for each element in top-level proposal.
(optimization/design alternative resolution) Describe how parameters were optimized relative to the specifications/performance, and/or how decisions between design alternatives were made. If equations exist between performance specification and parameters, they should be presented in this section. If simulations were used, the simulation procedure must be described and critical results presented. If changes were made iteratively between design testing and design modification, this must also be explained.
It is important to demonstrate your thinking or processes used to decide between design alternatives relative to your proposed criteria.
Final schematics, drawings, program flowcharts, and photographs of final device are presented in this section.
5. Design Verification
Results of the testing procedure are presented in this section to show to what degree the design meets the original specifications. Use tables, charts, graphs, and statistics to effectively demonstrate performance. All must be explained clearly so reader can understand to what degree your design function and meets specifications.
6. Conclusions
Suggested content:
Summarize the performance of your design, the effectiveness of the design process, and indicate what you would have done differently at the start of this design process knowing what you know now. If you did not meet the criteria this is a good section to describe how future work you could do the criteria given more time.
Appendix
Must include engineering notebooks! Optional: programs, detailed schematics, preliminary/alternative designs …
Final Report (60%), graded by faculty coordinator in consultation with faculty advisor (Team/Group Grade).
Breakdown of 60% is as follows,
5% Problem identification and society impact
15% Problem Formulation (Criteria)
5% Teamwork and Organization
20% Solution
15% Verification
10% Independent evaluator on the report (Group Grade)
10% Coordinator Graded Engineering Notebook (individual)
5% Peer Review (internal) by team members (Individual Grade)
10% Oral presentation of design (individual grades for each member in the group)
5% Demonstration of design (Group Grade).
Exams No written exams. Final Presentations and Project Demonstrations will be made during the final exam time period. You can think of them as an oral final exam worth 18% of your grade. Your individual presentation should be 15 minutes long and be a logical and balanced part of your team’s presentation. You should have about 8 overheads and not more than 15 overheads. You will be strictly held to your allotted time, no more, no less.
Requests to have a grading error on any deliverable changed must be made in writing within 14 calendar days of the deliverable being returned to the class.
Project
In general projects must be substantial enough to require a team of more than one student to complete it in the available time. Your project can be either an approved project of your own choosing or it can be a project from the following list. You may assemble your own team for your project with the approval of the instructor. You will not be allowed to overstaff your project.
|
Project |
Expected team size |
|
|
|
|
IEEE robotic competition |
3 - 5 |
|
Big Blue |
3 - 5 |
|
Solar Car Power -Do the gap adjust motor again -Build a battery charger -Build a charger for the cars aux pack -Build a bps for the aux batt -Build a bps |
3 - 4 |
|
Solar car instrumentation |
3 - 4 |
|
Robot lawn mower |
3 - 5 |
|
Superhetrodyne AM radio |
2 - 4 |
|
Analog audio power amplifier |
2 - 3 |
|
Switching audio power amplifier |
3 - 9 |
|
DC/DC converter |
3 - 9 |
|
Toy motor controller |
3 - 9 |
|
Power transformer |
2 - 3 |
|
Photovoltaic system |
3 - 9 |
|
Basic electric organ |
2 - 5 |
|
Alarm clock |
2 - 4 |
|
Laboratory power supply |
2 - 3 |
|
Signal generator |
2 - 3 |
|
Clapper |
2 - 3 |
|
Discrete transmitter / mod. and receiver / demod. |
3 - 5 |
|
Infrared remote control transmitter and receiver. |
2 - 3 |
|
Discrete operational amplifier |
2 - 3 |
|
|
|
Some Available Resources
Computer Program Availability:
SPICE: B2 Spice which is on the Civil engineering computer lab computers the W. T. Young Library computers, and EE499 lab CRMS 215E.
MATLAB / SIMULINK: Civil Engineering computer lab.
MATHCAD: Civil Engineering computer lab.
AUTOCAD: Civil Engineering computer lab.
ANSOFT Electromagnetics: 556FPAT lab (see the instructor).
Laboratory: FPAT 681, Equipment Function Generators, Oscilloscopes, Power Supplies…. etc….
Consultations: