Applied Computer Science and Artificial Intelligence

The course deals with: - the models and theories underlying human-computer interaction, and in particular cognitive models, communication and collaboration models, task analysis, notation and dialogue design, system modeling, models for advanced interaction, social and collaborative aspects; - the integration of HCI in the software development cycle, and in particular the user centered design, the iterative development process, the scenarios, the evaluation techniques, the integration with agile programming. List of topics: need finding interviews and questionnaires storyboard expert-based interface evaluation techniques user-based interface evaluation techniques paper prototypes development process of an interface agile, user-centered design iterative cycles of interaction design, software development and evaluation interaction with mobile systems interface design criteria in the iOS environment interface design criteria in the Android environment assignment and discussion of the themes of the exam projects

No other teachings are a prerequisite for this.

- Alan Dix - Janet Finlay - Gregory Abowd - Russell Beale "HUMAN-COMPUTER INTERACTION", 3rd edition, http://dl.acm.org/citation.cfm?id=1203012. It is also available in Italian translation: http://www.catalogo.mcgraw-hill.it/catLibro.asp?item_id=1746

The course is based on lessons, exercises and development of a project. In general, every week we follow a lesson and an exercise (recorded by the teacher himself). During the lessons, presentations are shown which are then made available on the site. The exercises generally cover the topics covered in the previous lesson. The exercises can be carried out in groups of three students or individually. Some tutorials require users to interview users or perform usability tests. Students are then invited to look for users among their acquaintances or between students and staff in the university city. The result of the exercises is developed in the following days and sent to the teacher by email within the next lesson. Approximately one month after the start of the course, the teacher assigns projects to be carried out individually or in groups. The work consists in designing an interface according to the criteria explained during the course. The themes of the projects are chosen by the teacher, but the students must deepen the topics through the Needfinding techniques explained in the course. The design on paper is sufficient, without development of code, provided it is carried out according to the criteria of paper prototyping. It is recommended to use programs that facilitate prototype testing with users, such as POP or Marvel. Students are required to perform two project reviews with the teacher before delivery. For revisions a calendar is established, in the period between mid-November and February of each academic year, and individuals or groups will have to book by email. Priority will be given to groups wishing to take the exam in the winter appeals. For those who intend to take the exam in other appeals, however, the reviews will take place during normal receptions students who must be booked as indicated above. The tutorials and projects will be discussed in the webinars. Students can actively participate by asking questions and describing their work. At the end of the project, ten days before the date of each appeal, the material produced during the project must be delivered to the teacher in a compressed .zip file attached to an email. The material includes the report of the work done (10-20 pages .pdf file), which describes all the phases, the activities carried out, the information acquired and the results obtained, the design decisions taken and the relative reasons, the description of the organization and execution of usability tests, as well as feedback from these and the resulting changes to the project. Furthermore, all the material produced during the work must be included in the zip file: interview texts and answers by the interviewees questionnaire texts and answer files, as well as links to the corresponding online forms images of the storyboards images of the mockups, of all the versions that have been gradually developed observer notes for all usability tests performed POP / Marvel / etc. prototypes navigable other material that can be useful to the teacher to verify and validate what is written in the report

Attending classes is strongly recommended.

The exam consists of the evaluation of the project and the oral. The evaluation of the project is based on the material delivered as well as on the two discussions carried out during the revision. The evaluation is unique for the projects carried out in a group (ie the same grade for the whole group), unless during the revisions it is shown that one or more students are not participating in the work with a commitment equal to that of the others. The evaluation consists of a band of votes that constitute the basis for the final grade: A => 27..30 B => 25..28 C => 23..26 D => 21..24 E => 18. .21 The oral consists of two questions on the topics covered in class. Each question is worth 2 points that add up to the basic vote of the project - 1. For example, a student who took B to the project and 2 to each question would have 25-1 + 4 = 28. Who scores less than 1 point overall between two questions, does not exceed the oral and must redo the next appeal or in any case within a year so as not to lose the vote of the project. Members of a project group are not required to perform the oral exam in the same date.

- Apple Human Interface Guidelines, available as iBooks (https://itunes.apple.com/us/book/ios-human-interface-guidelines/id877942287?mt=11) or online: https://developer.apple.com /library/ios/documentation/UserExperience/Conceptual/MobileHIG/index.html - Introduction - Material Design - Google design guidelines (available on the web http://www.google.com/design/spec/material-design/introduction.html)

The course is based on lessons, exercises and development of a project. In general, every week we follow a lesson and an exercise (recorded by the teacher himself). During the lessons, presentations are shown which are then made available on the site. The exercises generally cover the topics covered in the previous lesson. The exercises can be carried out in groups of three students or individually. Some tutorials require users to interview users or perform usability tests. Students are then invited to look for users among their acquaintances or between students and staff in the university city. The result of the exercises is developed in the following days and sent to the teacher by email within the next lesson. Approximately one month after the start of the course, the teacher assigns projects to be carried out individually or in groups. The work consists in designing an interface according to the criteria explained during the course. The themes of the projects are chosen by the teacher, but the students must deepen the topics through the Needfinding techniques explained in the course. The design on paper is sufficient, without development of code, provided it is carried out according to the criteria of paper prototyping. It is recommended to use programs that facilitate prototype testing with users, such as POP or Marvel. Students are required to perform two project reviews with the teacher before delivery. For revisions a calendar is established, in the period between mid-November and February of each academic year, and individuals or groups will have to book by email. Priority will be given to groups wishing to take the exam in the winter appeals. For those who intend to take the exam in other appeals, however, the reviews will take place during normal receptions students who must be booked as indicated above. The tutorials and projects will be discussed in the webinars. Students can actively participate by asking questions and describing their work. At the end of the project, ten days before the date of each appeal, the material produced during the project must be delivered to the teacher in a compressed .zip file attached to an email. The material includes the report of the work done (10-20 pages .pdf file), which describes all the phases, the activities carried out, the information acquired and the results obtained, the design decisions taken and the relative reasons, the description of the organization and execution of usability tests, as well as feedback from these and the resulting changes to the project. Furthermore, all the material produced during the work must be included in the zip file: interview texts and answers by the interviewees questionnaire texts and answer files, as well as links to the corresponding online forms images of the storyboards images of the mockups, of all the versions that have been gradually developed observer notes for all usability tests performed POP / Marvel / etc. prototypes navigable other material that can be useful to the teacher to verify and validate what is written in the report