Electrical Engineering/Computer Engineering Senior Design Project


Published on

Published in: Technology, Business
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Electrical Engineering/Computer Engineering Senior Design Project

  1. 1. What makes a successful project <ul><li>Make your project ambitious enough </li></ul><ul><li>But make it do-able </li></ul><ul><li>Involve a range of activities to exercise a team </li></ul><ul><li>Specify something that you can prototype </li></ul><ul><li>Have more than one design approach </li></ul><ul><li>Involve some interesting non-technical issues </li></ul><ul><ul><li>Ethical </li></ul></ul><ul><ul><li>Economic </li></ul></ul><ul><ul><li>Environmental </li></ul></ul><ul><li>Try to use experiments and trials </li></ul><ul><ul><li>and set them up correctly </li></ul></ul>
  2. 2. Scoring Rubric for Senior Design Projects Outcome 4 Exemplary 3 Proficient 2 Apprentice 1 Deficient Rating 3c. Graduates will be able to design a system, component or process to meet specified project requirements by: i. identify specific project objectives based on general project and client requirements .         ii. gather and use relevant information           iii. generate and analyze alternative by synthesizing and applying approriate engineering knowledge           iv. consider all relevant constraints if applicable. Economic           Environmental/sustainability           Manufacturability           Ethical/health and safety           Social/political           v. choose the best solution based on technical and economic criteria and considering relevant constraints           3.g. Graduates will demonstrate an ability to communicate effectively – written, oral and presentation skills. ii. oral presentation           3.b. an ability to design and conduct experiments, as well as to analyze and interpret data i. experimentation if applicable           ii. data analysis          
  3. 3. Examples of Senior Design Projects ( Summer 2006) <ul><li>1.5T Four-Element Phased Array MR Coil (Hashim Baradah, Ali Alibeji) </li></ul><ul><li>Developed from summer job at Medrad </li></ul><ul><li>Creating a More Efficient (Manufacturing) Process (David Schaffner) </li></ul><ul><li>Applied to family-owned manufacturing company </li></ul><ul><li>Nitrogen Doping of n-Type 4H SiC (Corey Schaffer) </li></ul><ul><li>Developed from independent research projects in Physics Department </li></ul><ul><li>Control System for Small Autonomous Aerial Vehicles (Jeremy Romeiko, Kim-Wai Lam) </li></ul><ul><li>From Robotics Club activity </li></ul><ul><li>RFID Workstation Design (Kyle Pentz, Paul Powell, Eric Shields) </li></ul><ul><li>Associated with Prof. Mickle’s RFID research </li></ul><ul><li>Hardware Prototype to Demonstrate Products with RFID Tags (Michael Wolff, Feng Gao) </li></ul><ul><li>Associated with Prof. Mickle’s RFID research </li></ul><ul><li>Control of Waste Water Treatment Plant (Arthur Brower) </li></ul><ul><li>Related to regular job </li></ul>
  4. 4. What’s a Proposal For? It establishes your credentials for a project and determines whether you will get it. It usually establishes the scope of work for a project. It definitely determines how much money you get. It is a team planning document.
  5. 5. Written Proposal <ul><ul><ul><li>Executive Summary (1 page maximum) </li></ul></ul></ul><ul><ul><ul><li>A. Specific Aims (1 page maximum) </li></ul></ul></ul><ul><ul><ul><li>B. Background (~2 pages) </li></ul></ul></ul><ul><ul><ul><li>C. Preliminary Work / Design Possibilities (3-4 pages) </li></ul></ul></ul><ul><ul><ul><li>D. Design Approach to be used (~1 page) </li></ul></ul></ul><ul><ul><ul><li>E. Milestones and Schedule (~1/2 page) </li></ul></ul></ul><ul><ul><ul><li>F. Cost Estimate (~1/2 page) </li></ul></ul></ul><ul><ul><ul><li>G. Expected Problems and how dealt with (~1 page) </li></ul></ul></ul><ul><ul><ul><li>H. References </li></ul></ul></ul>Total length should be no greater than 10 single-spaced pages, including figures but excluding the Executive Summary and a title page
  6. 6. Questions that should be answered by Background Significance of project What is new or different? Why is it important? How does it fit in with things that have already been done? This section should review the state-of-the-art and/or relevant scientific/industrial literature. Potential design approaches Why should our group be doing it?
  7. 7. What has already been done? Products commercially available (State-of-the-Art) Research Literature “ Scientific” journals 1 Professional meetings (Proceedings) 1 Technical society magazines 2 Industry magazines 3 Web sources 3 1 Material has been independently reviewed 2 Material often has been “lightly” reviewed 3 Material often not reviewed – anything goes!
  8. 8. IEEE Sources Spectrum, Potentials and Proceedings of the IEEE IEEE Specialized Publications Total of 126 titles in technical areas ranging from computer engineering and biomedical technology to electric power and wireless technology: Magazines Technical papers Conference Proceedings Books Available through IEEE Xplore in the library or go to http://ieee.org/web/publications/home/index.html
  9. 9. IEEE Spectrum, August 2004
  10. 10. IEEE Spectrum, August 2004
  11. 11. IEEE Technical Society Magazines Aerospace & Electronics Systems Annals of the History of Computing Antennas & Propagation Magazine Circuits & Devices Magazine Circuits and Systems Magazine Communications Communications Surveys and Tutorials Computer Computer Graphics & Applications Control Systems Magazine Design & Test of Computers Distributed Systems Online Electrical Insulation Magazine Engineering in Medicine & Biology Engineering Management Review Industry Applications Magazine Instrumentation & Measurement Magazine Intelligent Systems Internet Computing IT Professional Micro Microwave Magazine MultiMedia Network Pervasive Computing Power and Energy Magazine Robotics & Automation Magazine Security and Privacy Magazine Signal Processing Magazine Software Technology & Society Magazine Wireless Communications
  12. 18. Comments on Literature Citations <ul><li>Take the approach that the reader is your adversary. </li></ul><ul><li>You are trying to convince your reader that you are right, and your reader is likely to be looking for evidence that you are wrong. By citing publications in the scientific and engineering literature, you are providing authoritative outside evidence that what you say is correct . . . </li></ul><ul><li>and you are protecting yourself from someone else’s error – as well as charges of plagerism. </li></ul><ul><li>Web citations are becoming increasingly acceptable but are still suspect (review issues). Be sure to include date you accessed a website. </li></ul><ul><li>Personal experience is important, but it is generally not acceptable as documentation. If you must use personal experience, give details on how your conclusions from the experience were formed. </li></ul><ul><li>Examples of statements that cause problems </li></ul><ul><li>“ Developing this type of algorithm for use on this processor is something that has not been done before.” </li></ul><ul><li>A statement like this cannot stand by itself. It must be supported. You can support it by reviewing what has been developed for the processor and noting that none of the applications involve the algorithm of interest. </li></ul><ul><li>“ This approach has . . . already . . . been published in several papers . . .” </li></ul><ul><li>To support a statement like this, you need to list (cite) at least two papers. </li></ul><ul><li>“ Based on our research, the best approach is to . . .” </li></ul><ul><li>Not enough. You need to describe the research with enough detail to allow the reader to draw the same conclusion you did. </li></ul>
  13. 19. Use of Literature Citations <ul><li>The output of a rotary LVAD, however, is sensitive to afterload, i.e, to the hydraulic load it must pump against [1]. In addition, due to the fact that, at least until now, there are no reliable pressure sensors available to detect preload conditions, adaptation to venous return changes is still a missing factor in many of the control approaches reported in the literature [2, 3]. </li></ul><ul><li>[1] Boston, J.R.; Antaki, J.F.; Simaan, M.A.,“Hierarchical control of heart-assist devices”, IEEE Robotics & Automation Magazine, vol. 10, 1, pp. 54 - 64, March 2003. </li></ul><ul><li>[2] Maslen, Eric H. et al.,“Feedback Control Applications in Artificial Heart”, IEEE Control Systems, vol. 10, 1, pp. 26 - 34, December 1998. </li></ul><ul><li>[3] Giridharan, G., Skliar, M.,“Physiological Control of Blood Pumps Without Implantable Sensors”, Proc. of American Control Conference, Denver, CO, June 2003, pp. 471 - 476. </li></ul><ul><li>From A. Ferreira, M. A. Simaan, J. R. Boston, and J. F. Antaki, “Frequency and time-frequency based indices for suction detection in rotary blood pumps,” Proc. Int’l Conference on Acoustics, Speech, and Signal Processing, pp. II-1064 - II-1067, Toulouse, France, May 16, 2006 . </li></ul><ul><li>See Engineering Citation Formatting Guidelines on web site. </li></ul>
  14. 20. Library Research Plan <ul><li>The Bevier Library staff has created a set of on-line teaching modules that run in BlackBoard to help engineering students develop a range of skills related to information literacy. </li></ul><ul><li>Each design student is required to complete the modules and the associated quizzes with scores of at least 80%. </li></ul><ul><li>Each design group is to complete a Library Research Plan by September 10 , listing at least five non-web sources with a sentence or two on each to explain how they relate to the proposed project. </li></ul>
  15. 21. <ul><li>Library Research Plan </li></ul><ul><li>Bevier Engineering Library </li></ul><ul><li>Preparation for Senior Design Proposals </li></ul><ul><li>Due September 10 (beginning of class) </li></ul><ul><li>1a. What is the area of your design project? Write 1 sentence broadly describing it. </li></ul><ul><li>1b. What specific aspects of this area or problem do you plan to explore/utilize in your design solution? </li></ul><ul><li>1c. Highlight the key terms in your responses above and add any additional terms you plan to use as initial search terms to begin your review of the state-of-the-art related to your project. </li></ul><ul><li>What types of engineering literature are relevant to your project (and to your audience and the purpose of your project)? </li></ul><ul><li>What research tools will you use to identify relevant information for your topic? </li></ul><ul><li>Attach citations to 5 sources that you think will significantly contribute to your project proposal, including a sentence or two on how each is relevant. </li></ul><ul><li>Names of team members: </li></ul><ul><li>_______________________________ _______________________________ </li></ul><ul><li>_______________________________ _______________________________ </li></ul>
  16. 22. Preliminary Work/Alternatives (3-4 pages) Describe alternative design approaches Hardware DSP chip/microcontroller Experience with development environment Computer Peripherals Language Arguments for selected approach Technical capabilities Cost and experience Development time
  17. 23. Milestones (~1 page) Identify key tasks of project Which tasks can be done independently and which depend on previous work How much overlap is possible How many people will work on each task Estimate time for each task Progress report should address milestones
  18. 24. Acoustic Source Tracker <ul><li>Objective </li></ul><ul><li>To locate an acoustic source and </li></ul><ul><li>indicate the position with a rotating </li></ul><ul><li>laser </li></ul><ul><li>Team Members: </li></ul><ul><li>David Corsello </li></ul><ul><li>Matthew Ferencz </li></ul><ul><li>Brian Venus </li></ul>Data Acquisition Results Left and Right channel signals Microphone array and mount Adviser: Dr. Bob Boston Applications Video conferencing, security, targeting <ul><li>Design Alternatives </li></ul><ul><li>Implement </li></ul><ul><ul><li>~ Microcontroller </li></ul></ul><ul><ul><li>~FPGA </li></ul></ul><ul><ul><li>~PC </li></ul></ul><ul><li>Algorithm </li></ul><ul><ul><li>~ Calculate the delay in time domain </li></ul></ul><ul><ul><li>~Multiple microphones </li></ul></ul>Solutions ~Implement with Nios processor on Altera Board ~Servo Motor to direct array and laser towards source ~16-Bit A-to-D Converters for high resolution Conclusion System integration complete Signal Processing algorithm ECE 1896 Senior Design Algorithm Simulation Servo Microphone Microphone 18&quot;
  19. 25. Acoustic Source tracker control computer acoustic
  20. 26. Example of Milestones Final Prototype Algorithm Acoustic Data Acquisition Software Design Algorithm Implementation Pointer Controller
  21. 27. Schedule (1/2 page) Tasks Can sequential tasks be completed in time? Who is doing what? Parts Sources How long will it take to get them? Time frame Proposals due September 26 Four weeks – October 24 – progress reports Six more weeks (including Thanksgiving) – Design Expo (December 5) Need time for debugging and testing
  22. 28. Cost Estimate (1/2 page) A. Development costs What will it cost you to design and build a prototype? Parts needed Availability and sources Alternatives B. Funding request C. Production costs What would it cost to produce the product in market-sized quantities for sale?
  23. 29. Expected Problems (~1 page) Identify bottlenecks in project Identify technical hurdles What don’t you know how to do Devise alternatives in case problems can’t be solved in time Parts sourcing problems Purpose of this section is to show you have thought through the project and have some expectations of how it will turn out
  24. 30. Oral Proposal Presentation 10 minutes About 1 slide per minute (less than 10) Be selective - you can’t explain everything Title slide should include team members, advisor, and acknowledgement of any outside groups you are working with. You are to give Angela a copy of the title slide after your presentation.
  25. 31. Comments on Proposals (and final reports) <ul><li>A proposal or report is a sales document – you are trying to sell a project to someone (boss, customer, investor). You have to be convincing. Remember that you are trying to convince your reader that you are right, and your reader is likely to be looking for evidence that you are wrong. </li></ul><ul><li>The Executive Summary is not an introduction. It needs to include technical detail about what is to be done and why it should be done. You will need some introduction for the summary to make sense, but use as little a possible. (This is part of the art of writing summaries.) </li></ul><ul><li>Background should include a general introduction to the problem. This is where you cite references to the state-of-the-art and current research. Justify that what you are proposing is important and worthy of a senior design effort. </li></ul><ul><li>Don’t just say that you have done such-and-such. Give sufficient detail for the reader to be able to evaluate the reliability of your results and the validity of your conlusions directly. Remember, the reader is your adversary, looking for holes in your arguments. </li></ul><ul><li>Reports should make the project look like it was planned and executed perfectly. Anything else is hard to understand. You can (should) discuss at the end what problems were encountered and whether they were solved. </li></ul><ul><li>Learn to be your own editor. Be tough. Unnecessary words are usually confusing. </li></ul><ul><li>Remember that behind every great novelist, there is a great editor who reduced the book length by two-thirds! (Okay, I made that up, but it is close.) </li></ul><ul><li>7) Use white space – bullets and lists can make a page much easier to read. </li></ul><ul><li>Be careful of how you use words. Avoid colloquial and picturesque language. It is likely to mean different things to different people. </li></ul><ul><li>Minimize repetition, even when you are forced to use an organization that is inherently repetitive. </li></ul><ul><li>See Hints on writing technical reports on the website. </li></ul>