Coursehero >> Texas >> UT Arlington >> CSE 3310

Course Hero has millions of student submitted documents similar to the one below including study guides, homework solutions, papers, exam answer keys and textbook solutions.

3310 CSE Fundamentals of Software Engineering; Fall 2008 Presentation Rules & guidelines Rules: Presentation dates: Mon. 10/6 (Teams 1 to 4), Wed. 10/8 (Teams 5 to 7). All material (i.e. SRA, UML, Use Cases) is due on 10/8. A copy of your presentation slides should be handed to me before starting your presentation. Presentations should cover SRA, Use cases and UML as well as a high level overview of the project, the approach and the next steps. 10% daily penalty, of the presentation portion, if you are not prepared when your turn comes. We will use a different order for the final presentations (i.e. go in reverse order) to be fair all teams. Power Point is the desired software for the presentation; however other applications could also be used assuming you provide the necessary software. You could e-mail me your Power Point presentation by noon on the day of your presentation in case you d like to use my laptop for presentation. Otherwise you must provide the means for your presentation via your own laptop. No presentation on the blackboard is accepted. You can use the board to elaborate points if you wish. Total presentation time per team is 20 minutes (16 minutes for presentations, i.e. about 8 minutes for each member, and 4 minutes for setup and Q&A). Please keep track of your time and plan accordingly via practice sessions. The contents of the presentation will affect all team members grade. Conducting the presentation will affect the presenters grades only. Two team members should take part in the presentation, one at time, a presenting different portions. The other two will present the final product at the end of the semester. If your team has only 3 members, you could decide to have either one or two people do the presentation. If your team has 5 members, you could decide to have either two or three people do the presentation. Make sure to mention the name of all your team members in your presentation as well as introducing yourself. Interleaved presentations are not accepted. I.e. One presenter must finish before the next one starts. However one can operate the laptop while other presents. All team members can participate in answering questions. As an audience, please be courteous and don t disturb the presenters. We will use the guidelines on the next page for evaluating the presentations. Keep in mind that grading your handouts (i.e. SRA/UML/Use Cases) is independent of the presentation evaluations. CSE 3310 Fundamentals of Software Engineering; Fall 2008 Presentation evaluation guideline Evaluator: Dr. Khalili Mr. White Term Project: Retail Auto Parts System (RAPS) Team Number: Presenter#1 s name: Presenter#2 s name: *Scale: 5 = Excellent, 4 = Good, 3 = Meets expectation, 2 = Below expectation, 1 = Poor Topic covered *Scale *Scale Comments Presenter 1 Presenter 2 Overview and project Introduction Project components and approach via UML, context diagrams High level review of Use Cases, Requirements, Assumptions & Constraints Next Steps, Conclusion Overall Content Overall presentation look & feel Overall Presenter s Performance Additional comments:

Find millions of documents here - Study Guides, Homework Solutions, Papers, Exam Answer Keys and more. Course Hero has millions of course related materials that will enable you to learn better, faster and get an A in all your courses.
Below is a small sample set of documents: