Hello, dear friend, you can consult us at any time if you have any questions, add WeChat: daixieit

Advanced Human Computer Interaction

(F21AD/F20AD)

Coursework

Sem B 23/24

Important: Read through this document carefully before you begin to work on your assignment.

NB. Before emailing the course teaching team please ensure:

1. You have taken the opportunity to ask questions in the labs/tutorials.

2. That there are no more labs/tutorials at which you have time to ask the question(s).

3. That you have asked the question(s) at relevant times during one of the lectures or asked at the end of a lecture.

4. That you have checked this coursework hand out.

5. That you have gone to one of the tutor open clinic times on Fridays 1200-1245 to ask any questions.

Contacts for assistance and queries :

Course Lecturer (Edinburgh)

   Prof Lynne Baillie                      Email: [email protected]

   Dr Shenando Stals                    Email: [email protected]

Course Lecturer (Dubai)

   Dr Abrar Ullah                          Email: [email protected]

Course Tutors (Edinburgh)

   Carl Bettosi                              Email: [email protected]

   Dr Mehdi Rizvi                          Email: [email protected]

   Kefan Chen                              Email: [email protected]

Tutors student drop in clinic for queries (in person and online) Edinburgh only : Room: EMG1.58 Day & Time: Friday: 1200-1245

COURSEWORK PART 1: WORK TO BE COMPLETED IN A SMALL GROUP (4 max)

This part of the coursework assignment is worth 27% of Module mark available.

Please choose one of the three concepts below and let the lecturer/tutor know.

(NB: please note the first 3 groups for each concept are guaranteed that they will be assigned that concept afterwards a random allocation of concepts will be made) :

1.  Design a gamified approach which allows users to understand code security and helps them to write secure code themselves as well as identify insecure code snippets from third parties. The focus of this fun and interactive gamified approach should be on children from the age of 11-16, who may not have had formal software engineering training/education. There must be at least 3 different modalities used in the game, one of which must be voice.”

2.  People from different minority-ethnic backgrounds, of various age groups and with varying levels of English linguistic fluency (consider reading, writing/typing, speaking, listening) want to access critical online services related to health, social housing and energy. Create a solution which utilises a raspberry-pi and sensors to help them get vital notifications, alerts, announcements etc. Make sure to use multiple modalities to fit the needs of your users allowing tangible interaction without a screen.

3.  Design an application that helps users to meet lifestyle goals in an interactive and fun nature. This may include walking the user through meal preparation in real time or during the undertaking of exercise activities. Assume that at times when the user is performing activities as guided by the application, that interaction should be easily accessible. Some of your users have an accessibility issue, your group must decide what type of issue. You need to include three different interaction modalities in your design. One must be voice, and one gestures.

The above concepts are deliberately open ended because at this level of academic work you are expected to be able to plan how to tackle real world problems.

You are assessed on the quality of the design, the thoroughness of your background research, and most importantly the quality (in terms of Advanced Human

Computer Interaction) of the prototype produced. You do not need to produce a fully working prototype, but at least some parts must be interactive depending on the concept, and at least two task pathways should be able to be completed by a user.

Before starting the coursework it is important that you acknowledge that it must be designed for and work for the END USER(S) specified. Whatever you design should be designed to cater to the needs of your user group, for example your user group may need the design to reflect weak eyesight or certainly learning difficulties (e.g. dyslexia).


Whilst it is not expected of you to have the application fully designed for different disabilities it is expected that elements of these requirements should exist in the design.

Group Size

You should work in groups of 4. You are expected to use the sign-up sheet on Canvas. If anyone has not formed themselves into a group by the end of week 3, then please let the class tutor (Edinburgh)/lecturer (Dubai) know and they will assign you to a group.

Edinburgh based students please contact your class tutor this is Carl Bettosi

([email protected]) by the end of week 3 if you do not have a group. No changes can be made to the groups after week 4.

Individual contributions

It is an important aspect of collaborative work that the strengths of individuals are

harnessed for the overall good of a project. You will be expected to share the workload in the assignment equally between you but division of labour along lines of interest or

expertise is expected. Use your strengths and weaknesses to divide work accordingly.

Problems within collaborative working

Should anyone in your groups conduct be deemed unsatisfactory then this should be reported to the appropriate Class Lecturer for your Campus, who will speak to the

student concerned. In the first instance, you should try to resolve any issues by yourselves.

DETAILED ASSIGNMENT TASK OVERVIEW

The assignment requires the group to carry out the following tasks, each of which we will discuss during the first weeks of the course.

1.  Design Report (section 1) : Requirements Gathering & Planning (35 marks)

i.     Background Research & Requirements analysis: The group should undertake a literature review and use this research to inform your design and

development work. The review must focus on literature from respected Human Computer Interaction conferences and journals, and also

focus on designing for your selected user group. (20 marks)   ii.    Creation of Personae, Storyboards and Use Cases (15 marks)

iii.    Gantt Chart/Time Line: A Gantt Chart or detailed time line should be created detailing all the work to be completed for coursework A. Each task should

have the initials of the person responsible for delivering the task. (3 marks)

The first stage of your work requires your group to undertake the work in points i-iii.

Please create drafts of all of the above and be ready to present them on Friday, 9th

February (Edinburgh, week 4). The lecturers/tutors will provide feedback on all elements during Friday’s class.

2.  Prototype Development (35 marks)

After gaining essential feedback about the first stage of the work the group is now ready to move on to create a software and/or hardware prototype. There are many tools you can use to create early prototypes. The one that we have selected is “FIGMA” Please note: we will only offer tutor/lab support for FIGMA. If your group would like to use something else we will consider this request, but please be aware this is at the groups own risk and if any issues arise in its use it will be the group responsibility.


.     For Concepts 1 and 3, there should be an interactive and clickable prototype on Figma.

.     For Concept 2, there should be flow chart (or similar diagram type) on Figma

showing the intended interaction as well as a hardware prototype implemented on Raspberry Pi.

3. The Design Report (section 2) (25 marks)

A report that contains the requirements gathering & planning (see section 1 above) and  explanation of the design of the prototype. The report should contain annotated versions of the final prototype screenshots (concepts 1 & 3) or interaction diagrams (concept 2)   and should explain how the group implemented Advanced Human Computer Interaction  concepts throughout. Your report should be succinct (no more than 4500 words).

4.  Presentation & Demo (Week 7 Friday session Edinburgh or xx session Dubai (5 marks)

Each group will have approximately 10 minutes to present their final prototype to one of   the class lecturers or tutors. The prototype must be demoed and available for the tutor to check that two tasks can be completed using the partially functioning prototype.

SUBMISSION

There should be two files

1. A Design Report submission should consist of one PDF with all

individual surnames, and HWU email addresses clearly shown.

2. A .fig file downloaded from Figma, containing the prototype design with at least one of the group members surname and email address clearly shown.

PART 1 SUBMISSION TIME AND DATE: 1530 (UK TIME) MONDAY 4TH  MARCH (week 8)

COURSEWORK PART 2: Evaluation & Evaluation Report

This part of the coursework assignment is worth 20% of Module mark available.

PART 2 SUBMISSION TIME AND DATE: A Digital version of the Coursework should be submitted via Canvas no later than 3:30pm (UK TIME) on Thursday March 28th

(week 11).

Very Important!! This Coursework Assignment is to be completed individually.

Please read through this document carefully before you begin to work on your assignment.

NB. Before emailing the course lecturer please ensure:

1. You have taken the opportunity to ask questions in the labs/tutorials.

2. That there are no more labs/tutorials at which you have time to ask the question(s).

3. That you have asked the question(s) at relevant times during one of the lectures or asked at the end of a lecture.

4. That you have checked this coursework hand out.

5. That you have gone to one of the tutor office hours on Fridays 1200-1300 to ask any questions.

Assignment task overview:

1.  Evaluation Methods and Protocol

You need to design an evaluation that will show you how well the design of your assigned group prototype works in practice. You will need to conduct an evaluation study online or in person with 3-5 users. Your classmates will act as users for you and you will act as users for them. You must evaluate both parts of the original design e.g. the interface created and the interaction.

Undergraduate students: You must choose 2 methods 1 qualitative and 1 quantitative. These must be two entirely separate methods e.g. a questionnaire even if it is in a

different format still only counts as one method. You must be sure to critically justify

your selections in terms of Advanced Human Computer Interaction using research from top level journals and conferences. This research must be suitably referenced using

Harvard style formatting. You must further present 1 method that you did not choose and explain why it was not suitable again you must justify this using HCI research literature.

MSc level students: you must select 2 qualitative and 2 quantitative methods for your evaluation and critically justify in terms of Advanced Human Computer Interaction

research why they are suitable. These must be entirely separate methods e.g. a questionnaire even if it has qualitative and quantitative questions only counts as one method). You must also present two methods you did not select and say why  they were not suitable. You must be sure to critically justify your selections in terms of Advanced Human Computer Interaction using research from top level journals and conferences. This research must be suitably referenced using Harvard style formatting.

Evaluation Report

You must provide a report on your evaluation and results and you should complete the report as you go through the different stages e.g. evaluation methodology, analysis, design changes and conclusions. Your report should be succinct (no more than 3500 words) and you should use appendices for the raw data from your evaluation. The appendices are not included in the word count and are not marked.

Report Sections:

1. Protocol

A full evaluation methodology containing your methods and a protocol must be created, which contains a detailed plan of your evaluation. Marks 25

2. Results

The results of the evaluation should be summarised and explained using text, graphical displays and statistics. Marks 40

3. Conclusions & Design Changes

From your results you are expected to draw conclusions as to which parts of the design works well and those that need improvement in some way. Suggestions for design

changes must be provided. Marks 20

4. Appearance and quality of report. Marks 10

5. Taking part in evaluations for other students. Marks 5

NB: Appendices for raw result data (not marked) and declaration of authorship must be included in the submission.

IMPORTANT FURTHER INFORMATION

As part of the University's work to promote Academic Integrity we now require each student to submit a Standard Declaration of Authorship form with each piece of coursework they submit. This will be available on Canvas. Please ensure to complete this for your Coursework B. Without this form your work will not be marked.

Plagiarism will not be tolerated and will incur serious penalties. You can find the university’s plagiarism policy at

https://www.hw.ac.uk/uk/students/studies/examinations/plagiarism.htm

The standard university late submission policy applies. Assignments submitted up to 5 working days late will be penalised by 30% off the achieved mark. Assignments submitted over 5 working days late will not be marked (this includes formative feedback).