Reference no: EM133116869

1. A 3D visualisation tool to simulate buying furniture at IKEA

2. A single student app that integrates all student apps in one

3. A mobile app that translates teenage slang in received messages and emails for the elderly

4. An Interface that tracks energy usage at the home and provides alerts, suggestions

5. An Interface that tracks the medicine intake of patients at home

After you have selected your topic you will further research on the idea and proceed with developing both low and hi-fidelity prototypes for your intended system.

The three assessments that together form the HCI project are now described in detail hereunder.

Assessment - Project Brief

Relevant Details

Instructions
The goal of this project brief report is to present your topic, the rationale and motivation of choosing your topic and to relate its importance with relevant HCI literature. You will also need to benchmark your proposed idea/concept by comparing it against 3 existing commercial applications that are similar. The main purpose of this assessment is to provide feedback to you on your chosen topic so that you may address any concerns for the remaining two assessments. You are strongly recommended to use this feedback to keep the project on track and improve your subsequent submission of other assessments in the subject.

The project brief report must be written and formatted using the SIGCHI conference template (which will be provided on vUWS). You must follow the SIGCHI template completely and meticulously. Therefore, all formatting must be according to the template. The best way to manage that would be to replace the text in the template with your own text. After you have written all your content, remove text that is leftover from the template. The content (not formatting!) of the headings, subheadings are somewhat your choice and the suggested headings below are a good starting point.

The required length of the report is approximately 1200 words; excluding the bibliography section. There is no threshold associated with this first assessment.

The following subsections/subheadings must be included in the project brief report:

1. Introduction and Motivation: introducing your topic and problem; providing a context for your topic/problem; justifying the choice of the topic/problem and highlighting the importance of the topic/problem.

2. Literature Review or also known as Related Work Section: Linking your chosen topic and its importance by showcasing what other HCI researchers have done in similar areas and if any gaps exist. A minimum of three relevant academic articles must be cited. A sample literature review document will be provided which will clarify tips and techniques on how to approach a literature review (such as starting from the general themes and drilling down to the specifics). In this assessment the literature review can be about three short paragraphs (approximately 300-500 words).

3. Benchmark Design: Benchmark your proposed idea/concept by comparing it against 3 existing applications that are similar (either iOS or Android). Clearly state at least one issue with each of the existing apps (conceptual or interface/UI related). Give more details than "hard for user to navigate, etc.". Discuss pros and cons and how your idea advances the app, web or system market in comparison to the existing 3 applications.

4. Design Statement: One line design statement describing what you will attempt to do.

5. Personas: Present two personas (i.e. major stakeholders) of your interactive solution. You can present the two personas as text or visually or in a tabular format.

6. Conclusion and Future Work: A short paragraph on the way forward.

7. Bibliography: listing all references using the Harvard referencing style

Assessment: Low-Fidelity (Design Concept) Report Relevant

Instructions
In this report you will present your initial design ideas of how the interface that addresses your chosen topic should look like and behave using paper wireframes only. Please use the templates for paper wireframes as provided on vUWS and as discussed in the lecture and tutorials. All paper wireframes must be hand sketched and annotated extensively; use of software is not allowed to enhance the sketches.

The low-fidelity prototype report must be written and formatted using the SIGCHI conference template (which will be provided on vUWS). You must follow the SIGCHI template completely and meticulously. Therefore, all formatting must be according to the template. The best way to manage that would be to replace the text in the template with your own text. After you have written all your content, remove text that is leftover from the template. The content (not formatting!) of the headings, subheadings are somewhat your choice and the suggested headings below are a good starting point.

The required length of the report is approximately 1250 words; excluding the bibliography section. The wireframes can be included in the appendix. Please scan the paper wireframes and then insert into the report; do not take a picture with your smart phone camera as that will reduce the quality of the image when inserted in the document! Since the wireframes are hand-sketched, legibility will only be ensured when they are scanned into the document.

The following subsections must be included in the low-fidelity prototype report:

1. Introduction: Brief recap of your chosen topic and its motivation.

2. Scenario Description: Clearly highlight and then briefly describe 3 interaction scenarios within your chosen topic. As stated prior, a scenario will typically be one feature of your system. Showcase the scenario description by employing one of the following techniques: use cases, storyboards or task analysis. Feel free to use any one of the 3 but not more than one mentioned visual techniques to represent each of the scenarios. So for example Scenario 1 can be represented by Task Analysis, Scenario 2 by storyboards, Scenario 3 by Use cases OR Scenario 1 can be represented by Task Analysis, Scenario 2 by Task Analysis, Scenario 3 also by Task Analysis and so on any combination thereof. Also each scenario must be explained through text and through one visual technique as mentioned above.

3. Design Conceptualisation: For each of the 3 scenarios present your paper wireframes (each scenario can be a subheading for the sake of readability and clarity). Also clearly indicate any user actions that result in traversing the wireframes and describe the layout and design of the interface. Some of the wireframes will be identical

Attachment:- Project.rar