Skip to main content

2 posts tagged with "Research"

View All Tags

· 2 min read
Robbie Morris

HCI Presentation Blog

Welcome back to our Systems Engineering (COMP0016) project blog! In this installment, we will delve into the exciting world of Human-Computer Interaction (HCI) as we share our journey from understanding user needs to building and refining our motion input Bluetooth controller prototype.

Personas and Scenarios

Armed with valuable insights from user surveys and interviews, we set out to create personas and scenarios that would guide the design and development of our MotionInput Bluetooth Controller. Personas help us empathise with our users, and scenarios provide a narrative context for how our product fits into their lives.

Prototypes and Wireframes

With our personas and scenarios in mind, we embarked on the exciting phase of sketching multiple possible prototypes. These sketches explored different design ideas and interaction patterns, ensuring that we considered various user preferences.

Prototype Sketche 1 Prototype Sketche 2

The most promising sketches were then translated into a digital wireframe prototype using Figma. Figma allowed us to create a clickable prototype that simulated the user journey through our motion input controller app.

Figma Wireframe

Prototype Evaluation and Refinement

To ensure the usability and effectiveness of our prototype, we conducted a rigorous evaluation based on HCI principles. We identified potential issues and areas for improvement, addressing each problem systematically:

Problem NumberLocation & DescriptionHeuristicSolutionSeverity
1Disabled users misclick connect and settings buttonsFlexibility and efficiency of useMove buttons further apart3
2Awkward drop-down menu for controller switchingAesthetic and minimalist designImplement a minimal toolbar for controller selection1
3Unclear status of MotionInput settingsConsistency and standardsAdd a visual indicator for MotionInput options2
4Lack of language optionsSpeak the user's languageInclude language selection on the home page1

We have taken this valuable feedback to heart, making iterative improvements to our prototype. The user experience is our top priority, and these refinements bring us one step closer to delivering a good final product.

· 3 min read
Robbie Morris

Setting the Stage: Project Inception

Welcome to our first blog post! Today, we are introducing our Systems Engineering (COMP0016) project, a MotionInput Bluetooth Controller. From setting up our project repository to clarifying goals with Dean, we have been hard at work laying the foundation for an innovative and user-centric experience.

1. Project Repository Setup

Every great project starts with a well-organised and accessible repository. We kicked off our journey by creating a project repository on GitHub. This centralised hub serves as the backbone of our development process, providing version control, collaboration tools, and a space for seamless integration with other tools.

Key Repository Components:

  • README.md: A comprehensive guide to the project, including installation instructions, project structure, and contribution guidelines.
  • Issue Tracker: A place to log and discuss tasks, enhancements, bugs, and other project-related topics.
  • Branching Strategy: Defined branches for features, bug fixes, and development staging, ensuring a streamlined development process.

2. Notion Page for Better Teamwork

Effective communication and collaboration are essential for the success of any project. To enhance our teamwork, we incorporated Notion into our workflow. Notion provides a centralised platform for documentation, task tracking, and knowledge sharing.

Notion Page Highlights:

  • Project Roadmap: A visual representation of our project timeline, milestones, and deliverables.
  • Gantt Chart: An interactive timeline with task dependencies and progress tracking.
  • Meeting Notes: A record of discussions, decisions, and action items from our team meetings.
  • Requirements: Detailed list of functional and non-functional requirements, including user stories, usability criteria, and specific system capabilities.

Understanding User Needs: HCI Requirements Gathering

To prepare for our HCI presentation, we began with a deep dive into understanding user needs. We conducted surveys and interviews to gather valuable insights that would shape our project's direction.

User Requirements Highlights:

  • User Surveys: Collected feedback on existing input methods and pain points experienced by users.
  • Interviews: Engaged with potential users to understand their preferences, expectations, and challenges related to MotionInput.

Clarifying Goals

We had a meeting with Prof Dean Mohamedally, our project mentor, to ensure that our goals and objectives were in sync with his.

Meeting Outcome:

  • Project Scope: Defined the boundaries of our project to ensure a manageable and achievable scope.
  • Budget and Resources: Discussed resource requirements and received necessary approvals for additional tools or equipment.
  • Timeline and Milestones: Agreed upon a realistic timeline for project milestones and deliverables.