Engineering 6806 Electrical & Computer Engineering Design Project
Instructors |
Dr. D. K. Peters |
Dr. S. O'Young |
Office hour | Mo, We 3:00-4:00,
or by appointment |
Tu 2:00-5:00 |
Lectures: | Tu 12:00-12:50, Th 12:00-1:50
EN2048 |
Lab slot: | Th 2:00-5:00 |
T.A. |
Razzaqul Ahshan | Peter King |
E-mail | razzaqul at engr.mun.ca | peter at engr.mun.ca |
Office | 3075 | 4029A |
Phone | 737-3472 | 737-3527 |
Teams |
Objectives |
Project |
Organization & Deliverables |
Kit |
FAQ |
Schedule |
Evaluation
Detailed Schedule
The following is the tentative schedule of
lectures, meetings and other deliverables.
Date |
Deliverable |
Lecture/meeting |
Examples/Handouts |
Th 09.06 |
|
Introduction |
management.ppt,
barriers.ppt
|
Tu 09.11 |
|
Team Draft, no lecture (only captains attend). |
|
Th 09.13 |
|
Mechatronics,
Lab 1Getting started with the
robots |
Photo of controller card with
labels., Sample code,
Drive system test code,
Servo sample code
|
Tu 09.18 |
|
Incremental
Design |
Intro to Subversion |
Th 09.20 |
|
Modularization |
Sample document |
|
Tu 09.25 |
|
Computer
Vision (N. Krouglicof) |
Th 09.27 |
|
Computer
vision (cont'd) (12:00-12:50), Lab 2 -- Computer vision |
Dr. Krouglicof's Engr 8805 page |
Mo 10.01 |
Preliminary draft design document |
Th 10.04 |
|
Review meetings (1:00 - 4:00) |
Judge software jar,
Test client jar,
.bat file to run the judge,
sample map file.
rallycourse.dtd.
|
Th 10.11 |
Demo 1 |
Mo 10.15 |
Peer review 1 |
Mo 10.22 |
Revised draft design document |
Th 10.25 |
|
Review meetings (12:00 - 5:00) |
|
Th 11.01 |
Demo 2 |
|
|
Mo 11.05 |
Peer review 2 |
Th 11.22 |
Final competition (results and grades) |
|
|
Fr 11.30 |
Final Documentation, Log books |
|
|
Mo 12.03 |
peer review 3. |
Textbook
There is no textbook for this course.
Evaluation
Logbook (individual) | 6% |
Project: |
| Demo 1 | 8% |
| Documentation rev. 1 | 6% |
| Demo 2 | 8% |
| Documentation rev. 2 | 12% |
| Competition | 24% |
| Final Documentation | 36% |
As you can see from above the documentation is worth up to 60% of your grade
for each increment. This grade is broken down as 40% for design and 20% for
the documentation itself.
Note that teammates will not necessarily receive the same grade
for the project component. The team score for the project will be
calculated as above, and each team member's score will be adjusted up or
down based on:
- Peer evaluation -- At two times during the project and at the end,
every member of
each team will be asked to indicate what they think the percentage
contribution of each of their team members (including themselves) was to
the project.
- Reported effort -- The reported hours worked (as discussed
elsewhere) will be taken into account in assessing team members relative
contribution. Note, however, that effort is not the same as
contribution.
The individual project mark will be calculated as
, where
m | is the individual student project mark (out of
94) |
P | is the team project mark (out of 94) |
pe1, pe2, pe3 | are the peer evaluation
grades as a decimal (i.e., pe1 = 1 means that the student is
evaluated to be contributing on par with expectations on the first peer
evaluation.) |
h | is the hours worked reported for this student |
H | is the total hours worked by all students on the team |
n | is the number of student on the team |
Related Links
- Sensors
-
- Motor Control
- LMD18200T
- Micro-controller
-
- Application Notes
-
- Java & Computer Vision
-
- Revision Control
-
- Related interests
-
back to Dennis Peters' homepage
Last modified
$Date: 2007-11-28 11:25:12 -0330 (Wed, 28 Nov 2007) $
($Revision: 256 $) by
$Author: dpeters $