Reference no: EM133687197

UX Major Project

Semester Overview
This semester you will be assuming the role of UX Practitioner, with the tasks of user experience analysis, research, design, and evaluation.
Each student is provided with a different product and scenario requirements for a mobile application. Your goal is to research, analyse, and design a high-fidelity clickable prototype of the application's interface with an exceptional user experience, and then evaluate and analyse the usability and user experience of your prototype.

Learning Outcome 1: Review Human Factors and Human-Computer Interaction (HCI) in IT systems;

Learning Outcome 2: Evaluate the elements of User Experience (UX) of an IT system using design thinking, and compare the effects of positive and negative user experiences;

Learning Outcome 3: Classify User Experience (UX) problems in real-world systems;

Learning Outcome 4: Establish the diverse needs and requirements that users may have of a system.

S1. Evaluate the usability of IT systems using quantitative and qualitative metrics;
S2. Analyse and assess IT systems from a human-centred perspective;
S3. Design and evaluate User Interfaces using formal and informal processes.

A1. Analyse, design and evaluate a suitable User Experience design to meet specific IT system design requirements.

Requirements

Most tutorials will come in two parts:

Part 1: Test your knowledge and skills on the concepts taught that week in the lecture.
These are independent tasks from one another that allow you to learn about vital concepts that may help with other assessments. Represented by the red rectangles in the flow chart on page 1.
Part 2: Create, analyse and/or evaluate a small deliverable in relation to your UX scenario assessment.
These deliverables flow from one week to the next, building toward your major deliverables of the design and evaluation of your scenario product. Missing out on any of these may have negative consequences for future deliverables. Represented by the blue rectangles in the flow chart on page 1.

Requirements

You have been provided with a UX scenario for your assessments on Moodle. Each student has been randomly assigned a different company and product, along with other randomised scenario constraints. Therefore, every student has different assignment criteria.
For this assignment (UX Design), you are required to create a high-fidelity clickable prototype for the product and scenario you have been assigned. Make sure you carefully read your scenario and its constraints.
Each week during the tutorials from week 1 to 7, you will be submitting smaller UX deliverables such as product objectives, user personas, user tasks, competitive reports, product flows, wireframes, and preliminary designs. These all support and lead up to the creation of your high-fidelity clickable prototype for this assignment. It is advised to submit every tutorial, or this UX Design assignment will be very difficult to complete satisfactorily.
The requirements are as follows:
Generate your Major Assignment UX Scenario through Moodle.
Follow your Major Assignment UX Scenario and its constraints for this assignment.
The design will be a mobile smartphone application for the company outlined in your scenario.
It will include registration of an account and a once-off purchase or regular subscription of an assorted box of delivered goods (based on your scenario product), as well as other tasks you have decided during the weekly tutorials. See your Major Assignment UX Scenario for full details.
You should consider everything learned up to and including week 8 of this unit when designing this application for smartphones.
You must use Evolus Pencil (prototyping software available on Moodle) to create your screens for the application and link them together into a high-fidelity clickable prototype (taught during tutorials).
"High-fidelity" means that mockups of the screens visually appear like a fully developed application with no placeholders.
"Clickable prototype" means that a user can navigate through the static screens using navigation, menu items, and/or action buttons as would be present in a developed product.
You must provide annotations with details describing anything that may not be clear on the static screens, such as animations, transitions, dropdown menu options, selections, validation, error prevention, etc.

UX Evaluation

Requirements

You have now designed your application based on your personal UX scenario, delivering a high-fidelity clickable prototype.
For this assignment (UX Evaluation), you are required to conduct usability testing with five users on your high-fidelity clickable prototype and produce a report with results, evaluation, and recommendations for further design iterations.
During tutorials 9 to 11, you will be submitting smaller UX deliverables such as consideration of user testing methods, creating user task scenarios, metrics, desirability testing, and designing questions. These all support and lead up to your evaluation report for this assignment. It is advised to submit every tutorial, or this UX Evaluation assignment will be very difficult to complete satisfactorily.
The requirements are as follows:

Use your previously submitted high-fidelity clickable prototype for all evaluation.
Recruit five participants for usability testing:
The participants must be REAL and representative of your user personas (from tutorial 2).
Record their demographics as necessary, but do not record any identifiable data such as their name. You can use pseudonyms in your report.
Conduct usability tests:
Should be observed remotely or in-person. Remote allows you to record the screen.
Use four task scenarios (created during tutorials) for the usability testing.
Record usability metrics (identified in tutorials) as you proceed through the tests.
Conduct surveys:
Post-task: Use the Single-Ease Question (SEQ) (discussed in lectures) after each of the four task scenarios.
Post-test: Use the System Usability Scale (SUS) (discussed in lectures) after entire test is completed.
Post-test: Ask questions regarding Desirability testing (identified in tutorials).
Throughout: Ask your own created qualitative questions (created during tutorials).

Analyse the results and write your report:
It should be a formal professional report with title page, headings using heading styles, numbered sections, tables, figures, APA referencing, etc. (see Lecture 10 for example report structure).

Consider the appropriate use of dot lists, numbered lists, and tables, and using interesting ways to present your data visually.
Must include the following:

Executive Summary: Provide a brief overview of the report, highlighting the overall usability of the application, and summarising the key findings and recommendations.

Goals: Clearly define the goals of the usability testing.

Methodology: Discuss the methods of how the usability testing was conducted and reasoning for the approach. Describe the tools used for your testing and surveys. You should research these and justify their use in usability testing.

Participants: Discuss the demographics of the users and their relationship to the user personas and product.

Task Scenarios: Describe the user task scenarios that you tested and how they matched the product objectives, user needs, and your scenario requirements.

Results and Discussion: Present the data and metrics obtained in easy-to-read formats, including diagrams, charts, and detailed discussion. Summarise the results presented of the usability testing.

Reflection: Critically reflect upon the testing methods. What worked? What did not? Why? How could you do it better? What other evaluation methods would you use (considering both expert and user evaluation)? Consider additional tasks you did during the week 9 to 11 tutorials.

Recommendations: Discuss key findings, strengths, weaknesses and summarise a list of recommendations for changes to the design of your mobile application.