Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: modify layout when a new test is created #548

Open
marcgc21 opened this issue Jan 19, 2025 · 0 comments
Open

feat: modify layout when a new test is created #548

marcgc21 opened this issue Jan 19, 2025 · 0 comments
Labels
Enhancement New feature or request good for wannabe gsocers Issues for the wannabe contributors to get to know the code better

Comments

@marcgc21
Copy link
Member

Translation of Usability Evaluation Methods

When categorizing usability evaluation methods, they can be divided into three main groups based on the type of interaction and primary goal:


1. Inspection

  • Description: Evaluations carried out by usability experts without the direct involvement of users. They focus on analyzing the design of the interface to identify potential problems.
  • Key characteristics:
    • Based on heuristic principles, standards, or guidelines.
    • Does not require real users, making it quick and cost-effective.
    • Useful in early stages of design.
  • Examples:
    • Heuristic Evaluation: Based on principles such as Jakob Nielsen's heuristics.
    • Cognitive Walkthrough: Analyzes the mental workload of tasks.
    • Guided Walkthroughs: Step-by-step simulation of typical tasks.
    • Automated Evaluations: Use of tools to verify accessibility or detect errors.

2. Inquiry

  • Description: Methods that collect information directly from users about their needs, opinions, and experiences. These are useful to understand how users perceive the system or how they might interact with it.
  • Key characteristics:
    • Can be qualitative (exploring perceptions) or quantitative (measuring satisfaction).
    • Focus on directly or indirectly gathering data from users.
    • Useful for identifying expectations and perceived problems.
  • Examples:
    • Interviews: One-on-one conversations to explore needs.
    • Focus Groups: Moderated group discussions to identify common issues.
    • Surveys and Questionnaires: Tools like SUS, QUIS, or UMUX.
    • Field Studies: Observation in the user's natural environment.

3. Testing

  • Description: Methods that involve active user participation while interacting with the system, allowing direct observation of behavior, identification of problems, and measurement of usability metrics.
  • Key characteristics:
    • Provide objective data on effectiveness, efficiency, and satisfaction.
    • Usually conducted in a controlled environment.
    • Involve specific tasks designed to evaluate the system.
  • Examples:
    • User Testing: Observing users performing tasks (e.g., think-aloud protocols).
    • A/B Testing: Comparing two versions to measure performance.
    • Eye-Tracking: Analyzing visual patterns through eye movement tracking.
    • Log Analysis: Collecting data from real interactions.

To prepare the system, we need an initial layout that allows the user to select one of those categories. Inside of the category, he will find different methodologies to choose.

Most of them are yet unavailable, so until now, until user testing and heuristic evaluation are available.

@marcgc21 marcgc21 added Enhancement New feature or request good for wannabe gsocers Issues for the wannabe contributors to get to know the code better labels Jan 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement New feature or request good for wannabe gsocers Issues for the wannabe contributors to get to know the code better
Projects
None yet
Development

No branches or pull requests

1 participant