ece496 lecture4 nov8 2012 · evaluated but unmarked dry run then marked final presentation – (by...
TRANSCRIPT
1
1
ECE496 Design ProjectTerm 2 Deliverables
Thursday, Nov 8, 2012
Agenda
o An aside: December review1. Progress report / progress review2. Oral Presentation 3. Final Report4. Design Fair5. Misc. Administrative Stuff6. Extra Materials:
o Poster Designo Ethics Reviews
ECE496 Milestones & Deliverables
Sept Nov JanDec MarFeb AprOct2011 2012
Design Review meeting
Individual Progress Report
Final ReportOral Presentations
(tutorials)
Planning, concept Design Review
ExecutionProgress Report, Oral Presentation
Design Fair
December Review
1st draft 2nd draft
Final version
Project Proposal
December Review
o Not markedo May have deliverables from Design Reviewo May want to deliver based on Design Reviewo Best if a show and tell of progress so far
2
Begin with a good plan … maps Equipment Study
terrain Avoid
pitfalls
…follow through in execution
Team work Testing Documenting Presenting Reporting progress
Notes from Ted Herman This is not what we are trained to do The task is huge Your schedule is probably already wrong Set hard limits on the time to decide on tools, platforms,
etc.
Agenda
o An aside: December review1. Progress report / progress review2. Oral Presentation 3. Final Report4. Design Fair5. Misc. Administrative Stuff6. Extra Materials:
o Poster Designo Ethics Reviews
3
Individual Progress Report / Evaluation –Why They’re There
–Project View:• To allow reevaluation of position and adjustments if required • To access overall project progress• To access individual contributions and progress
Individual Progress Report
A group progress summary plus individual reports
What you have accomplished since the Design Review)
GroupProgress summary
Individual reports(for each student)
Hints for the Progress Report
Credible (supported) statements about accomplishments (completed & underway)
Unfinished activities are less comforting(What does “Select processor 50% done” mean???)
Indicate problems you’ve encountered and overcome through your creativity and hard work.
This is why you have been told repeatedly to have an engineering notebook!!!!
Wishy-washy ≠ Credible
Background statement Reference [link to tasks & requirements]
Development Activity done Test
Example --“I finished the analog-to-digital conversion routine”• is it coded?• does it compile cleanly?• does it work with some input randomly selected?• does it work with a carefully-designed set of test cases
that cover all operational situations?• Sample evidence: photos, simulation plots, screen shots,
schematics, flow diagrams, etc.
4
Note: Writing vs. Communication
This is not about writing. This is about communication.
Figures & Charts
Boxes
Headings
Lists & Tables & Bullets
Categories & other
Organization
Tip from Ted Herman
Keep an “evidence trail” on the work you do. We took too much time on our progress reports because we had to recreate evidence and remember what we had done.
Individual Supervisor Evaluations
Your supervisor will also evaluate your individual progress in mid-January.
Agenda
o An aside: December review1. Progress report / progress review2. Oral Presentation 3. Final Report4. Design Fair5. Misc. Administrative Stuff6. Extra Materials:
o Poster Designo Ethics Reviews
5
Oral Presentation – Why It’s There
Project View:– Faster information flow, lower volume than written report;
questions possible– To be able to measure progress– To inform third parties of project
Oral Presentation Format
Evaluated but unmarked dry run THEN Marked final presentation
– (by administrator)
Will have opportunity to select dates (watch your email) Bring your own laptop Presentation length depends on team size Questions from audience
Grading session
Quick flow; low volume Try to include necessary pieces, but make the format
your own. Avoid a chronological account of your project
19
Presentation Format
Build your presentation around important points, using the grading evaluation form. To some degree all of the following are expected:– Motivation– Project goals and specifications– System overview– Progress update– Conclusions
20
Presentation Format
6
21
Individual
22
Team
Team
Make contact with your audience Use pictures, graphs, diagrams! With text, stick to key points Use informative headings Use a manageable number of slides
23
Presentation Tips
Make contact with your audience Use pictures, graphs, diagrams! With text, stick to key points Use informative headings Use a manageable number of slides Make your presentation memorable
24
Presentation Tips
7
Oral Presentation (Typical structure)
A title slide An outline of the presentation's contents. Introduction (explain to those not familiar with your
work the background and motivation for your project) Objectives (what you set out to do) Describe design, accomplishments, & milestones Summarize progress and future work Conclusions (what you covered in your presentation)
Question: How do you (or can you) rework this and use this to make your presentation interesting and
reflective of your enthusiasm in your project, without sacrificing important content???
Agenda
o An aside: December review1. Progress report / progress review2. Oral Presentation 3. Final Report4. Design Fair5. Misc. Administrative Stuff6. Extra Materials:
o Poster Designo Ethics Reviews
Final deliverables worth more than one course …
Proj
ect P
ropo
sal
Des
ign
Rev
iew
Indi
vidu
al P
rogr
ess
Rep
ort &
eva
luat
ion
Ora
l Rep
ort
Des
ign
Fair
Fina
l dem
onst
ratio
n
15% 8%17%
35% 22%5%
Fina
l Rep
ort
15%
Administrator50%
Supervisor50%
Final Group Report
Due before the Design Fair
Show you have followed the plan and reached the goal, satisfied the objectives and delivered the deliverables
---- or ----
Tell us what the problems were! Be honest, don't pad
– administrator and supervisor familiar with work, just need to know what you finally accomplished
8
29
Leveraging your past work
Preparing your final report, poster, and demo from the start
Final Group Report
Key additions– Documentation and assessment of final design– System testing and results– In some cases, a better articulated goal and requirements
Accomplishments need to be concrete tied to goals and requirements
The report is a shared, team responsibility– everyone contributes and makes clear which portion they write
Generous use of Diagrams!!!! Tables!! Lists!!! Follow final report guidelines
30
The Last Word from Ted Herman
The work I did in ECE496 got me a jobWe started badly, realized our problem.
The fix was:• Weekly “must attend” team meetings with subtask
assignment and peer pressure to finish them• Business first; friends later
Highlight your accomplishments
Save time by clarifying expectations Discuss with supervisor
– Supervisor’s grade is more heavily weighted now
You’ve already received expectations from administrator from past reports– Marked progress reports are with supervisor– Contact your administrator if you have trouble getting back your
marked reports
32
9
Highlight Accomplishments
Focus on quality and completeness of validation & evidence Top-down
• Demonstrate a working system • Acceptance tests
Bottom up • Demonstrate working system modules
Discuss results in terms of the project goal and requirements
Back up document with concrete evidence in the form of images, schematics, screen shots, simulations, etc. of both the design and the testing.
Agenda
o An aside: December review1. Progress report / progress review2. Oral Presentation 3. Final Report4. Design Fair5. Misc. Administrative Stuff6. Extra Materials:
o Poster Designo Ethics Reviews
35
2011 Design Fair HighlightsSearch ”2011 ECE Design Fair” on YouTube
Preparing for the ECE496 Design Fair
10
Design Fair – parts
1. Poster2. Presentation / Demo / Questions
Your message to visitors:"Here is the problem and why it's important. Here is what we accomplished, and proof that it works."
Preparing a Design Fair Demonstration
ALL groups must demo: Show the work is done or demonstrate some key concept of the work
Preparing a Design Fair Demonstration
Think through its impact on a visitor Provide a fluid connection to the poster Highlight accomplishments Leveraging past work
– Review the acceptance test from your Project Proposal• Example: cataract diagnosis
Consider both live and static or constructed demonstrations
What will you need in terms of resources to do this?
Resources for the Design Fair
Some stations are simply a table (i.e. without a power outlet, network connections, computer, etc.)
If your demonstration requires special equipment or facilities, you must notify Mike Mehramiz
• Deadline: Mon. March 11th
11
Time Conflicts with Design Fair
Design Fair takes place Tues-Thurs, April 2, 3, 4 6:30-9pm
Teams will be assigned a night by Mike Mehramiz If entire team has a schedule conflict on any of the
evenings, must contact Mike • Deadline: March 11, 2012
•Project title change•Equipment requests•Schedule conflict notification
Design Fair – grading
Supervisors often grade outside the Design Fair to have more time to better assess what you finally accomplished
Your grade from the administrator will be based on the following criteria:
• the quality of the presentation material • the ability to explain your work • the ability to provide correct responses to questions posed by the administrator
• project progress and complexity• a successful demonstration
• :
Agenda
o An aside: December review1. Progress report / progress review2. Oral Presentation 3. Final Report4. Design Fair5. Misc. Administrative Stuff6. Extra Materials:
o Poster Designo Ethics Reviews
44
Awards
ALOHA Award ($10,000) CNIB Hochhausen Prize Gordon E. Slemon Design Award Centennial Thesis Awards (2) Certificates of Recognition/Invitation to Final ShowcaseShort application required. Apply by email to at time of
submission of Final Report. See Awards page for details.
Many students get jobs based on their project!
12
Summary and To Do List
Important Dates: Monday March 11 Design Fair Requests
– Equipment requests– Schedule conflict notification
Thursday March 21 Final report Tues. to Thurs. April 2, 3, 4th Design Fair Fri. April 5th Design Showcase
Remind supervisors to submit Progress evaluations online
Watch for future announcements
Final Design Showcase
Bahen Atrium, Thursday April 5th, 11am-2pm
46
Claiming Project Expenses
All expenses must be based on the budgets that were submitted, reviewed and approved by teams.
Original receipts required Some Items purchased with support from us to be
returned as indicated in initial approval of request Additional instructions on “How to Claim” Funds to be
posted. See ‘Budgets & Funding Requests’ page
Time Conflicts for Oral Presentation or Design Fair
Dates are choosen via DoodleIf your presentation conflicts with evening midterms:
• If not completely overlapping, group usually presents after the test
• Ask instructor of other course to move the test date or allow you to write your test earlier
• Inform your administrator as soon as possible!
13
49
Questions……