Skip to content

Achievement System Board Interaction Testing

Kai9613 edited this page Sep 13, 2022 · 1 revision

Purpose

The primary purpose of this user test was to survey and assess user perceptions and feelings about the current implementation of the achievement panel interaction. This user test was very important to our project because our team's final design might have some flaws. Therefore, the test results will be used to improve the system.

Process

Due to the current COVID-19 situation, user testing will be done by an online zoom meeting. Testers will experience the system through the remote control of zoom functionality.

image

This is the achievement panel screen that the user will see during the test.

  1. Testers will look closely at and use the achievement screen.
  2. Write down some important observations.
  3. After experiencing the overall interaction, we'll ask the testers some key open-ended questions about the panel.

Key Questions Asked

  • What is the purpose of this achievement panel?
  • What do you think of the design of achievement panel?
  • What do you think about the achievement design of this achievement panel?
  • Any suggestions for improvement?

Results

Q1

On the whole, users clearly know what this function is used for, and all users can quickly conduct interactive operation to find the final result after receiving the instruction.

Q2

It looks like the layout is OK, but so far the design of the implementation is very casual, including the background which is not well designed and still uses blue. Hopefully there will be some interesting design content, the style is not very clear

Q3

The design still needs to be improved greatly; It does not highlight the design concept and still looks like a sketch.

Q4

It is hoped that the design can be well added to the interesting, rich panel design to make it look less conflicted.

Summary

Through this user test, we get some qualitative data of the design system. Since the theme of the game is a decryption game, all participants have high expectations for the background of this picture. However, some testers mentioned that the current design is a bit arbitrary, but the overall interaction is comfortable and can quickly find the desired results, For the design part, this is something our team might want to consider focusing on in the next sprint.

Table of Contents

Home

Game Design

User survey

Sprint 4

Eviction Menu and Win/lose Logic: Polishing tasks (Team 7)

Button Sounds and Ending Menu improve (Team 3)

Sound effect and Fixing the clue bug (Team 6)

Improvement of Enemy and Attack (Team 1)

Add Features When The Player Get Attacked and Overall UI Improvement (Team 8)

Sprint 1

Achievement System (Team 2)

Player Eviction Menu (Team 7)

Countdown Clock (Team 4)

Music (Team3)

Map (Team6)

Sprint 2

Player Eviction Menu (Team 7)

Character Design & Animation (Team 1)

Music (Team 3)

Inventory System and Consumables Items (Team 8)

Scenario design

Achievement System(team 2)

Storyline (Team 5)

Countdown Clock (Team 4)

Sprint 3

Ending Menu (Team 3)

NPC interaction (Team 2)

Win/lose Condition (Based on Eviction Menu) (Team 7)

Player Profile (Team 4)

Game Logo (Team 8)

Clue storage (Team 6)

Enemy Design and Attack (Team 1)

Scenario design for village(Team5)

Game design
Entities and Components

Service Locator

Loading Resources

Logging

Unit Testing

Debug Terminal

Input Handling

UI

Animations

Audio

AI

Physics

Game Screens and Areas

Terrain

Concurrency & Threading

Settings

Troubleshooting

MacOS Setup Guide

Clone this wiki locally