8
HCI 2011-2012 Exam and Evaluation Rules Recap and minor adgiustements (see also slides about: course introduction and the various assigmements/projects )

HCI 2011-2012 Exam and Evaluation Rules Recap and minor adgiustements (see also slides about: course introduction and the various assigmements/projects

Embed Size (px)

Citation preview

Page 1: HCI 2011-2012 Exam and Evaluation Rules Recap and minor adgiustements (see also slides about: course introduction and the various assigmements/projects

HCI 2011-2012Exam and Evaluation Rules

Recap and minor adgiustements

(see also slides about: course introduction and the various assigmements/projects )

Page 2: HCI 2011-2012 Exam and Evaluation Rules Recap and minor adgiustements (see also slides about: course introduction and the various assigmements/projects

1. STUDENTS WHO ATTEND THE COURSE REGULARLY

For attending students, evaluation will be based on

1. Active partecipation to classroom or online lectures and activities (max 2 points)

2. «Readings» Homeworks assigned every 1-2 weeks (max 5 points)

3. Usability Evaluation of an assigned web site (max 4 points)-MANDATORY

4. Mid-term Project: WP7 App (max 5 points)- MANDATORY5. Final Project (max 20 points) MANDATORY

All materials not delivered during the course must be posted on Beep – section HOMEWORKS-ATTENDING STUDENTS - by an appello date, notifying the posting to [email protected] – email subject: HCI exam

Page 3: HCI 2011-2012 Exam and Evaluation Rules Recap and minor adgiustements (see also slides about: course introduction and the various assigmements/projects

1. STUDENTS WHO DO NOT ATTEND THE COURSE

For non-attending students, evaluation will be based on

1. «Readings» Homeworks assigned during the course (max 5 points): OPTIONAL

2. Usability Evaluation of an assigned web site (max 4 points)-MANDATORY

3. Mobile APP Project: WP7 App (max 5 points)- MANDATORY

4. Final Project (max 20 points) MANDATORY

All materials must be posted on Beep – section HOMEWORKS-NON ATTENDING STUDENTS - by an appello date, notifying the posting to [email protected] – email subject: HCI exam

Page 4: HCI 2011-2012 Exam and Evaluation Rules Recap and minor adgiustements (see also slides about: course introduction and the various assigmements/projects

General Evaluation Criteria

• Attitude/Risources invested in the course

• Correctness and Completeness of Homeworks

• Quality of Mid Term and Final Projects

Page 5: HCI 2011-2012 Exam and Evaluation Rules Recap and minor adgiustements (see also slides about: course introduction and the various assigmements/projects

Readings Homeworks• See section «Teaching Material» including the spes of

the readings assigned during the various course and required documentation to deliver

Page 6: HCI 2011-2012 Exam and Evaluation Rules Recap and minor adgiustements (see also slides about: course introduction and the various assigmements/projects

• A Windows Phone 7 APP• What to do and to deliver: see slides

Points:• Publishing applications to the Windows Phone Marketplace (3

points)• Using advanced features: GPS, accelerometers, webcam,… (4

points) • 1 extra point at professor’s discretion

Mid-term Project

Page 7: HCI 2011-2012 Exam and Evaluation Rules Recap and minor adgiustements (see also slides about: course introduction and the various assigmements/projects

Usability Evaluation HomeworkWhat to do and to deliver: see slides lesson 7

Evaluation criteria: • correcteness and completeness of– Scenarios– Mile Inspection– User Testing

• Quality of documentation– Clearness, completeness– Good discussion– Comparison of methods– ...

Page 8: HCI 2011-2012 Exam and Evaluation Rules Recap and minor adgiustements (see also slides about: course introduction and the various assigmements/projects

Final Project

What to do and to deliver: see slides «Final Project»

Evaluation criteria: • Complexity (of the problem, of technology, of design...)• Technical Quality • UX Quality• Originality• Effectiveness of documentation

– all the required sections must be reported, clearly and concisely– from the documentation it must be evident which are the needs, users,

and context of use for the system you are prototyping, what are the design and technical challenges of the project