1. 1 ECE 18-649 Final Mini-Report Starting Point Month Day, 2010 Group #N Member Name 1 Member Name 2 Member Name 3 Member Name 4

2. Group #NStudent Name2 Overview  Presentation and slide information  Grading criteria  Outline for your talk: Elevator design Process in retrospect Project statistics Open issues Suggestions

3. Group #NStudent Name3 About Your Presentation  Stay on time! Whole presentation: 10-12 minutes  You will be cut off at 13 minutes for Q&A  On time is more important than exact number of slides  Most groups take too long if they don’t practice At least two team members shall present each time Each team member presents at least twice Slides submitted in advance and run on TA laptop  Be professional Speak loudly enough to hear in back row Do not wear hat, coat, or gloves Do not chew gum or have objects in mouth Practice your talk before you give it Try to minimize “Ah” “Uhm” “You Know”

4. Group #NStudent Name4 About Your Slides  Cover all of the content! Title slide with group # & member names Outline slide Content slides (6-8 total)  Design discussion (2-3 slides)  Process in retrospect (2-3 slides)  Project statistics (1 slide)  Open issues (half slide)  Suggestions (half slide) Slide template is flexible, but must be legible  16-28 point type for bullets; 16 point min font size  Name of student presenting must be on each slide  Slide number must be visible on each slide  Don’t bring printed handouts to class

5. Group #NStudent Name5 Grading Criteria  (20pts) GROUP PERFORMANCE (5 pts)Slides submitted by deadline (5 pts)Slides have acceptable format  e.g., font sizes, name on each slide (5 pts) All required topics covered by slides (5 pts)At least two group members present on time You get this team grade even if you are not presenting  (10pts) Individual Performance Best two out of three used for each student  If you only present twice, those two grades are used Present non-trivial material and time length to count (5 pts)Able to explain material on designated slides (5 pts)Appropriate attire; heard in back row

6. Group #NStudent Name6 Presentation goals 1. Showcase design aspects of your elevator You spent the whole semester working on it Tell us about the coolest parts! 2. Lessons learned about process Now that you’ve had a chance to do a relatively large design project using process, tell us about it  We want to emphasize that there is much more flexibility in this presentation that previous ones If you’re unsure whether what you want to present is appropriate in content or scope, ask us!

7. Group #NStudent Name7 System Design Discussion  Each group shall select one (or two closely related) aspects of their design to discuss  This must be some aspect of your elevator  A few examples: The coolest part of your design  A non-trivial design choice for easy testing, improved performance, etc. Most challenging design aspect  The biggest design problems you encountered and how you solved them using process Emergent behaviors  Behaviors that manifested when individual parts of your design were combined  Good? bad? unexpected? How did you deal with them? Any other interesting or favorite part of your design

8. Group #NStudent Name8 Process in Retrospect  Discuss the use of process during the semester Now that you’ve had to use it, what did you learn? What were the benefits? What were the difficulties?  Discuss the use of process to find errors in your design Scenario, sequence diagrams, requirements, state charts  What kinds of problems did you find during peer reviews? Unit, integration, and acceptance testing  What kinds of errors did you find from each? How would you have solved the same problems without using process?  Which strategies (team, technical, etc.) have worked well, and which have not with respect to process?

9. Group #NStudent Name9 Project Statistics  Statistics for each presentation Include three sets of statistics (as of this presentation, and the two from previous presentations)  Number of scenarios/sequence diagrams Also, number of sequence diagram arcs  Number of behavioral requirements Count up the numbers (7.1, 7.1.1, 7.1.2 count as two)  Number of statecharts Also, total number of states Also, total number of arcs  Number non-comment lines source code you have written Do not count blank lines or comments  Testing information: Number unit tests Number integration tests Number acceptance tests  Number of outstanding defects and issue log entries

10. Group #NStudent Name10 Open Issues and Suggestions  Open issues Biggest unsolved issue? How do you plan to solve it? Open issues are not incomplete parts It’s OK to say ‘none’ if you’re already finished  What suggestions do you have for next year’s students?  Suggestions for staff to improve 18-649 in future semesters?

11. Group #NStudent Name11 Common Presentation Errors  Many bullet items more than one line long  Fonts smaller than 16 point Beware powerpoint auto-resize Fonts in diagrams count too!  This font is pretty tiny and should only be used for details (16 pt)  This font is too small and shouldn’t be used (14 pt)  Poor personal presence Wearing outdoor coats, any hat, torn shirts, T-shirt Chewing gum Talking to front row instead of back row  Poor time management You must speak for 2.5+ minutes for individual grade and at least two non-trivial slides We’ll give you 5 & 2 minute warnings for talk

12. Group #NStudent Name12 Logistics  ALL final presentations are due Sunday April 25 th, 2010 by 7:00 PM Include it in your submission directory../ece649/Public/handin/presentations/ Any late submissions or corrections after the deadline will result in late penalties  See course web page for time slots Slots will run in order stated on web page