1 / 12

ECE 18-649 Mini-Report #2 Starting Point

ECE 18-649 Mini-Report #2 Starting Point. Month Day, 2010 Group #N Member Name 1 Member Name 2 Member Name 3 Member Name 4. Overview. Presentation and slide information Grading criteria Outline for your talk: Process execution example Project statistics Lessons learned Open issues

caesar
Download Presentation

ECE 18-649 Mini-Report #2 Starting Point

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. ECE 18-649Mini-Report #2Starting Point Month Day, 2010 Group #N Member Name 1 Member Name 2 Member Name 3 Member Name 4

  2. Overview • Presentation and slide information • Grading criteria • Outline for your talk: • Process execution example • Project statistics • Lessons learned • Open issues • Suggestions Student Name

  3. 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” Student Name

  4. About Your Slides • Cover all of the content! • Title slide with group # & member names • Outline slide • Content slides (6-8 total) • Process execution example (3-5 slides) • Project statistics (1 slide) • Lessons learned (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 Student Name

  5. 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 Student Name

  6. Process Execution Example • Each group discusses a module • Select from the following: • Door Control • Drive Control • Dispatcher • You MUST have implementation and test completed for presented module • Its OK if you’re still debugging Student Name

  7. Overall goal • Demonstrate you followed process • Show how you did steps of the design process(Statechart  Code  Testing) • It’s OK to focus on one or two transitions • Starting with the statechart • Identify specific transitions • How do transitions show up in implementation? • Show unit tests exercise transitions • Discuss how integration and acceptance tests include transitions • What problems did you find? • How did revisions impact design? Student Name

  8. Process Execution Outline • Brief recap (if necessary) • Scenario/sequence diagram/requirement • State chart • Identify specific transition(s) and associated states • Implementation • Illustrate how transition was implemented in code • Unit testing • Show how a unit test exercised the transition • Show injections and assertions • Integration and acceptance tests • Discuss which of these tests exercise this transition • Design revision • Discuss an example of a revision in your design during process execution and impact of that revision Student Name

  9. Project Statistics • Statistics are for all modules for current week hand-in • Not just the single module you present • Probably this is a slide with a big table • Leave entries with “n/a” for ones that don’t apply to you yet • 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 Student Name

  10. Lessons Learned & Open Issues • Problems that you have already solved • How they came up • What did you do to solve them • Process failures? Which part of process? • Which strategies (team, technical, etc.) have worked well, and which have not? • Open issues • Biggest unsolved issue? • How do you plan to solve it? • Open issues are not incomplete parts Student Name

  11. 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 Student Name

  12. Logistics • Presentations due at 9 AM day of recitation when your group presents • Simply include it in submission directory • ../ece649/Public/handin/presentations/ • We understand the elevator is not complete • Demonstrate you are following process • If you are an early presenter, put in what you have • See course web page for time slots • Slots will run in order stated on web page Student Name

More Related