Human-Computer Interaction (HCI)
1 (2000): Seminar Presentation
Presentation Due Date (allocation by auctioning): Presentation: L4-GroupA&B, L5-GroupC&D, L6-GroupE&F)
Formal Submission: Monday, Week 13 (25 September 2000)
Objective: The aim of this assessment piece is to accentuate communication skills either via class/multi-campus delivery (internals).
There are three parts of this assessment as follows:
1. To successfully organise and deliver a PowerPoint presentation on course content to an audience of other students in this course.
2. To critically analyse and review the work of other authors in their slide presentations, in terms of content and HCI constructs. Authors are required to respond to such reviews.
3. To review and reflect on the outcomes of parts 1 and 2.
Rationale of assessment piece
In order to create or analyse effective interface design for interaction and communication, the use of PowerPoint slides provides a powerful challenge. To create some form of dialogue between viewers and the medium, authors will need to have a good understanding of the content and principles of HCI. The authors will need to plan their presentation so that a good balance of graphics and text will create interest and understanding to the reader. Assume that viewers of your slides are from a variety of backgrounds.
Division of marks
(a) Seminar (15%)
All students are placed in teams of three persons. Each team will prepare one PowerPoint slide presentation with accompanying notes (use PowerPoint Notes). Internal students will deliver their seminar topic to other students in class, while external students will deliver their presentation to a small email group. All teams of students will complete review sheets of other presentations (one per team for each presentation). Each student will submit a summary of their reviews and reflect on the processes of teamwork, feedback for their presentations and improvements that could be made to their presentations.
Formal Submission (please submit as one piece of work for each team)
Rationale for the use of teams
The advantage of the team approach is that there are three people to share in the development process of the seminar. Industry encourages the use of team projects, and with the global economy upon us, the use of email correspondence is a suitable means for discussion. Alternatively, chat lines may offer real time discussion. A chat line is available on the web page for 25338. However, we note that the advantage of email for this assignment is that you have a permanent record of your discussions.
Teams, Seminar Topics and PowerPoint Slides
Seminar topics are placed at the end of this assignment and are also listed on the web site under the link Assignment Details. Each week has 5 topics from which Teams may choose one topic. No topic can be presented by more than one team. Each team is expected to present an interesting viewpoint of the selected topic, provide examples to explain the theory, and use graphics and tables where appropriate. The authors need to focus on communication via PowerPoint slides, with attention paid to the aesthetic quality of the presentation, including colours, fonts and format of the slides. The use of the notes facility provides the presenter (or reader) useful guidelines for the presentation and background of the points of discussion. For external students, this format enables them to imagine your presentation style…
(b) Seminar Presentation, review and feedback
It is important that you review your mail account at least twice a week. The list subscription will advise each student of their team members’ email addresses and the week of seminar presentation. Each team will then choose a topic from the five available topics for that particular week. If teams wish to change their week or topic then they need to swap with other teams within the group. It will be necessary to update such changes on the web, so please advise me if such a change is made. The group lists will facilitate their own presentations. It is suggested that each team prepare their presentation for submission to the list by the Monday of the due week, as an attached file. It is suggested that a common naming format may be useful for the slides, as follows:
course_group number_topic number with the extension ppt
Presentation format and timing:
In order to review a presentation, both the slides and the notes attached to the slides need to be reviewed. It may be necessary to download the actual file. Please take care to virus check any downloaded files, before you use them.
Each week, following the team submission, all other teams in that group must prepare a review sheet and attach it to the list. It is expected that authors will respond to the review to support their arguments or to supplement question feedback. This is intended to simulate the internal discussion at the end of a seminar delivery.
Notes for presentation/delivery: Refer to Unit Outline Page 20-21
Assignment 1: Seminar Topics
The selection of ONE topic is required for assignment 1.
Topic 4 / WEEK
Topic 5 /
WEEK FIVE (5)
Topic 6 / WEEK SIX (6)
1. Illustrate three examples of
different menu driven systems and discuss.
Topic 7 / WEEK SEVEN (7)
1. Define and illustrate several
examples of hypertext and hypermedia. Discuss the advantages
and disadvantages of these media formats.
Topic 8 / WEEK EIGHT (8)
1. Discuss how 3D objects can be
perceived in a 2D interface.
Topic 9 / WEEK NINE (9)
1. Good HCI design relies on
principles that come from traditional graphics design. Discuss
the seven design principles of such design: contrast, balance, proportion,
rhythm, harmony, movement, and unity.
Topic 10 / WEEK TEN (10)
1. Compare and contrast two different
types of help systems.
Topic 11 / WEEK ELEVEN (11)
1. Discuss the purpose of guidelines.
Illustrate the difference between principles and rules
with reference to the IBM system.
Topic 12 (new topic)
2 (2000): Report
Due Date: Monday, Week 9 (28 August 2000)
Penalties will apply to late assignments unless an extension has been obtained from the lecturer.
This assignment has two parts for you to complete.
Part A: Screen Design and Evaluation (17%)
Part B: Interface Evaluation (8%)
3 (2000): Software Prototype and Report
Penalties will apply to late assignments unless an extension is obtained from the lecturer.
Students are asked to develop an executable prototype. The topic of the prototype is the student’s choice. All students may choose either internal or external mode. Internal mode will present their team effort to class for review and discussion. As such, this presentation will be formally marked (10%), with review (5%). Visual Basic version 6.0 can be used, and it is expected that each project will include at least one scanned image or picture and one sound message.
Topic suggestions include:
Important: There is a large number of students so we must be able to run your program easily. Make sure all files needed are on disk(s) or a CD ROM disk. It must run "stand–alone". We might have a different version of the language from you. Ensure operating instructions are very clear.
You are to submit (hardcopy and zipped softcopy via email to firstname.lastname@example.org):
Created on 17 Jun 2000. Last revised on 1
Maintained by Tralvex Yeap