| CEN4020: Software Engineering I | up↑ |
The HCI presentation is used to assess your oral communication competency. Therefore, each team member must give a well-defined 5-minute portion of the presentation. Your team organizes these presentations, deciding who presents what, and in what order. However, keep in mind that the rubric (see the rubric at end of this file) must be applied separately to each person's portion of the presentatiion. For example, this means each person must have an introduction and a conclusion, and some well defined content, in order achieve a full score.
The presentation is done in the classroom. You are expected to use the HCI prototype web pages you have developed as your primary visual aids. However, you may want to supplement this with an introductory PowerPoint or HTML page for each person, saying who is speaking, and the topic -- typically a use case.
Each team will have 5 minutes per person, plus about 5 minutes for the entire team for questions and answers. Each person must take care not to run into another person's time.
Each person should introduce her/himself -- not all at the beginning, but at the transition to each speaker. Each should begin with a brief statement of what she/he is going to present, close with a summary, and ask for questions if there have not already been questions during that segment of the presentation. We will need to keep the time for questions and answers short, but we want each presenter to have a chance to answer questions, and we don't want the user's to have to hold questions to the end of the entire team presentation.
The schedule is tight. Make certain all of your materials are on the web, linked from the team's Trac page, without special protections, ready to go without delays. There will be no time to log into personal accounts, hook up laptops, etc. (Failure to be ready to start on time will result in a reduced score for the presentation.)
Please follow a storyboard approach to organizing your presentation. You are telling an illustrated story of how a person would make use of the system. The illustrations are your HCI prototype web pages. For example, a new user visits the web page, browses the public area, decides to sign up, gets a login, logs in, fills out forms to provide data, gets reports, etc. In effect, you walk through an extended use case scenario, probably a combination of several that you have considered distinct uses, chained together in a natural way that flows logically from one to another. At each point, explain what the user has in mind. Step through the windows the user will see, and how the user and system will interact at each step.
You should have time to cover several use cases, but maybe not enough time to cover them all, so the team needs to prioritize. Give priority to the scenarios that you feel are most central to the customer's purpose. To preserve logical ordering you will need to begin with registration, and include log-in, but take care not to spend too much time on them. If you include quizzes (an add-on) don't mention them until you have covered the core function of showing people how they save money by actually reducing their energy consumption.
If you chain together the use cases, as suggested above, you can transition between speakers at the use case boundaries. If you don't have enough time for each person to do a separate use case, you may split a longer scenario into parts that are presented by different people.
Remember to target the style and content of the presentation to your intended audience. The audience here is the customer. These presentations are your chance to market your understanding of the system and present unique ideas about the system to the customer. The customer wants to see that you clearly understood and conveyed his or her wants and needs for the proposed system.
Success of a presentation is a direct result of the amount of preparation, including review of the presentation materials and practice, by your team.
| Name: | ||||||
| START TIME: | END TIME: | Grade | ||||
| ORGANIZATION (20 pts) | Strongly Disagree ... Strongly Agree | |||||
|---|---|---|---|---|---|---|
| Introduction included name of presenter(s) | 1 | 2 | 3 | 4 | 5 | |
| Introduction included purpose and brief overview | 1 | 2 | 3 | 4 | 5 | |
| Concluded with definite ending and summarized main points | 1 | 2 | 3 | 4 | 5 | |
| Presentation well prepared and well organized | 1 | 2 | 3 | 4 | 5 | |
| CONTENT (40 points) | ||||||
| Essence of presentation clearly conveyed and understood | 1 | 2 | 3 | 4 | 5 | |
| Enough, but not too much, material/detail given | 1 | 2 | 3 | 4 | 5 | |
| Explanations appropriate and understandable | 1 | 2 | 3 | 4 | 5 | |
| Knowledge and understanding of subject matter demonstrated | 1 | 2 | 3 | 4 | 5 | |
| Questions handled well | 1 | 2 | 3 | 4 | 5 | |
| DELIVERY (20 points) | ||||||
| Presentation appeared extemporaneous (spoken, not read or memorized) | 1 | 2 | 3 | 4 | 5 | |
| Grammatical language used | 1 | 2 | 3 | 4 | 5 | |
| Avoided vocal fillers ("You know", "Aahh", etc.) | 1 | 2 | 3 | 4 | 5 | |
| Made good use of visual aids (overheads, chalkboard, computer demo, etc.) to support and enhance presentation | 1 | 2 | 3 | 4 | 5 | |
| Visual aids easy to see, easy to understand | 1 | 2 | 3 | 4 | 5 | |
| Presentation starts and ends on time | 1 | 2 | 3 | 4 | 5 | |
| EFFECTIVENESS IN COVERING OBJECTIVES (20 points) | ||||||
| Presentation gave customer a clear understanding of what the product would do when using the user interface. | 1 | 2 | 3 | 4 | 5 | |
| Navigation is clear and simple | 1 | 2 | 3 | 4 | 5 | |
| All button, clicks appeared to work | 1 | 2 | 3 | 4 | 5 | |
| Interface covers core product functions | 1 | 2 | 3 | 4 | 5 | |
| Interface design is consistent with principles of good HCI | 1 | 2 | 3 | 4 | 5 | |
| Interface design is attractive | 1 | 2 | 3 | 4 | 5 | |
| Customer feedback was sought and responded to | 1 | 2 | 3 | 4 | 5 | |
| Area for notes:
| ||||||
| $Id$ |