1 / 17

HCI Final Project

HCI Final Project. Outline. Recap of exam rules Definition of “Final Project” Domains Technologies Materials for exemplification and discussion What to do and to deliver Schedule. Recap: EVALUATION CRITERIA. Active participation during lectures and/or online (max 2 points)

urania
Download Presentation

HCI Final Project

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. HCI Final Project

  2. Outline • Recap of exam rules • Definition of “Final Project” • Domains • Technologies • Materials for exemplification and discussion • What to do and to deliver • Schedule

  3. Recap: EVALUATION CRITERIA • Active participation during lectures and/or online (max 2 points) • Exercises and Question Discussion (max 4 points) • One specific exercise on Usability Evaluation (max 4 points) • Mid-term Project (max 5 points) • Final Project (max 20 points) If not delivered during the course, all exercises will be done at official appello dates, when also final and mid-term projects must be delivered

  4. Mid-term Project • Publishing applications to the Windows Phone Marketplace (3 points) • Using advance features: GPS, accelerometers, webcam,… (4 points) • 5° pointat the discretion of the professor DEADLINES: • 13th December - Start publishing procedural • 20th December - App presentations in classroom

  5. Final Project: What is this? The design and protypical development of a content-intensive interactive application • in a given domain • using a specific hw/sw technology and interaction paradigm among the ones presented during the course Outcome: key users’ requirements + concept + prototype + documentation (preferably) a GROUP WORK

  6. Final Project: Domains & Technologies DOMAINS • Cultural Heritage • Architecture planning/design TECHNOLOGIES: • Multi-touch (Microsoft Surface or other Multi-touch table based on Windows 7) • Kinect

  7. Cultural Heritage Projects • Innovative patterns of (individual or collaborative) interaction with cultural heritage multimedia content (e.g., for museum or exhibition experiences) • Contents: Man Ray or Nippon Exhibitions • http://www.manraylugano.ch/en/index.html • http://www.nipponlugano.ch/en/

  8. Examples • Multi-touch: • http://www.youtube.com/watch?v=vpsQpltGol4 • http://www.youtube.com/watch?v=c1SKr8dQKwo • Kinect • http://www.youtube.com/watch?v=KBHgRcMPaYI • http://www.youtube.com/watch?v=TEnFhyOIlVA • http://www.youtube.com/watch?v=_qvMHAvu-yc • http://www.youtube.com/watch?v=-yxRTn3fj1g

  9. Architecture planning/design projects • Collaborative scenarios for Architecture planning and design • Contents: from real Architecture projects

  10. Examples • Multi-touch: • http://www.youtube.com/watch?v=hbv-4cc8ouM • http://www.youtube.com/watch?v=HVJpDlhORxw • http://www.youtube.com/watch?v=O7ENumwMohs • http://www.youtube.com/watch?v=heXEVecLi0c

  11. Final Project: Outcome key users’ requirements + concept + prototype + documentation

  12. Requirements & Concept Requirements • A description of the “problem” you are addressing (target users and general needs/goals addressed) Concept • A set of paper based or video based relevant scenarios (if useful, at multiple levels of abstraction and detail) • A feasibility study explaining why the solution is feasible and the general sw/hw architecture needed to implement it

  13. Prototype An evolutionary prototype (see lesson 4) • “Horizontal” in the interface and interaction features • Covers all major aspects, omit heavy “background aspects” of implementation • “Vertical”in implementation • MODULAR, only some parts of final system implemented

  14. Documentation • A short report describing requirements, concept, and key implementation solutions • A short (10 min) presentation of your work

  15. What to deliver • A CD/DVD containing • report describing requirements and concept • short (10 min) presentation of your work • Any further file (images, videos, prototype, …) + • A printedversionof the report and the presentation IMPORTANT!! CD/DVD cover + cover of ALL documents MUST contain: COURSE NAME, TEACHER NAME, ACADEMIC YEAR, DELIVERY DATE, PROJECT TITLE, STUDENT’S NAMES, EMAIL + CELL PHONE NUM OF GROUP CONTACT PERSON

  16. Potential follow-ups • SubmissionofyourconcepttoImagineCup (checkdeadlines!) • Constraints: ImagineCupdeadlines (check!) + useof MS technology + MilleniumGoalstheme + interactiveprotyping (checkrules) • Advantages: greatvisibility, challengingopportunity • Completionofyourconcept (revision, extension, implementation, validation) during2° semester “Project Course” (ProblemAnalysis Atelier: 5 CFU): subjecttoteachers‘ approval • Completion of your concept (revision, extension, implementation, validation) in your master thesis: subject to teachers‘ approval

  17. Preliminary Schedule Today

More Related