1 / 13

ELCT 402 Spring 2011

ELCT 402 Spring 2011. Dr Enrico Santi Professor L. Patrick Mitchell Ryan Lukens Teaching Assistants Dept of Electrical Engineering University of South Carolina Columbia, SC 29208. Presentation Overview. Course Objectives and Approach Grading Written Documents Organization

peggy
Download Presentation

ELCT 402 Spring 2011

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. ELCT 402Spring 2011 Dr EnricoSanti Professor L. Patrick Mitchell Ryan Lukens Teaching Assistants Dept of Electrical Engineering University of South Carolina Columbia, SC 29208

  2. Presentation Overview • Course Objectives and Approach • Grading • Written Documents • Organization • Project Descriptions • Strategies • Immediate Assignments

  3. Course Objectives • Plan and Organize an engineering project • Communicate technical matter in written and oral forms • Work as a team member • Successfully complete an engineering project from start to finish

  4. Approach • Goal: • To prepare you toapply Engineering to a Job through Communication • and • Customer Awareness (Teachers) • Research the problem • Develop solutions • Prototype • Test and Retest • Communicate to superiors • Document progress

  5. Grading • Grade is a composite of entire semesters’ work • 50% of your grade is determined by your group, 50% is determined by you • It is very straightforward to Receive an A

  6. Getting an A - Patrick • Course Website has descriptions and detailed grading policy for each assignment! • Ensure you have information pertaining to each sub-point in grading • Don’t misuse engineering terminology • Don’t write something that wouldn’t make sense to say • Take your time, and don’t expect to get a good grade by doing the assignment the night before

  7. Organization • Come to class. Its only 1 hour 1 time a week • Meet weekly, and report out brief meeting minutes to Patrick. • Major Assignments • Analysis and Design Requirements • Proposal • Design Review • Subsystem Demo • System Characterization • Final Oral Presentation/Final Demon

  8. BlackBoard • Assignments are submitted on blackboard • Each assignment should be named as YourName_AssignmentName.docx to avoid confusion • Assignments will be graded and returned to you by way of BlackBoard

  9. Notebook • Just write anything down • Leave some space at the front for contents • Date each entry • Cut out figures, staple documents, Glue-Stik • Neatness is not the source of your grade • Start now: Let your lab notebook be your constant companion

  10. Projects • 3 projects, 23 people: Groups of 3 and 4 students • Determine a team name, team leader, a desired project, and Email me this information by Thursday. • If you are not in a group by Thursday, email me your project preferences from 1 to 3 and I will assign your group: Final Group compositions will be established Friday • Descriptions on Course Website

  11. Common Problems to Avoid • Putting off documentation “until later”. • Not scheduling or not performing adequate research and analysis • Spending money instead of thinking • Communicating poorly • Failing to define and refine goals and deadlines. • Failing to consider integration of subsystems until the last minute. (Formalize your interface specifications.) • Emphasizing individual performance instead of team performance.

  12. Tech Analysis • Develop technical insight to the challenges that need to be overcome • Use Physics and Engineering to develop requirements • Do not solve the problem: Present possible solutions Solve an example of Tech Analysis: Personal Computer

  13. Grading Format: Tech Analysis

More Related