Transcript Document

Dr Enrico Santi
Professor
L. Patrick Mitchell
Ryan Lukens
Teaching Assistants
Dept of Electrical Engineering
University of South Carolina
Columbia, SC 29208
•
•
•
•
•
•
•
Course Objectives and Approach
Grading
Written Documents
Organization
Project Descriptions
Strategies
Immediate Assignments
•
•
•
•
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
•
•
•
•
•
•
Research the problem
Develop solutions
Prototype
Test and Retest
Goal:
To prepare you to
apply Engineering
to a Job through
Communication
and
Communicate to superiors Customer Awareness
Document progress
(Teachers)
Analysis & Requirements
Document
5%
Sys Characterization Report
5%
Oral Presentation (Composite)
10%
Status Reports
5%
Quality of Peer Evals of Others
10%
Rating from Peers
5%
Notebook Composite
10%
Proposal
15%
Tech Manual
10%
Midterm Requirements
10%
Final Demonstration
10%
End Analysis of Error in budget
and effort
5%
Average Individual Points
50%
Average Team Points
50%
Total Grade Points
100%
•
•
•
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
•
•
•
•
•
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
•
•
•
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



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
•
•
•
•
•
•
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
•
•
•
•
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
•
•
•
•
•
•
•
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.
•
•
•
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
Indications of
r
Excellence
r
r
Acceptable
r
r
r
r
r
r
Indications of
r
Baseness
r
Writing
r
Subscore
r
r
r
Multiple options are explored
Qualitative considerations are explained
Quantitative assesment defines interfacing of subsystem
Total
5
5
5
15
Presents quantitative requirements for a single subsystem
Sound theoretical basis for requirements
Approximations and estimates are reasonable
At least one possible solution is presented
Requirements leave availability for other options
Technology relevant to the requirements are discussed
Total
15
15
10
10
10
10
70
Gross Technical Misunderstanding
Blatant Plagirism
Total
-5
-75
-80
Total
5
5
5
5
20
Structure
Coherence
Grammar
Technical Terminology