[report]: Add Heuristic Evaluation headings
This commit is contained in:
Binary file not shown.
@ -1610,6 +1610,53 @@ Overall, $\frac{14}{18} = 77.\dot{7} \%$ of the specified objectives were comple
|
|||||||
objectives that were not completed were nonetheless researched and planned.
|
objectives that were not completed were nonetheless researched and planned.
|
||||||
|
|
||||||
\section{Heuristic Evaluation: Nielsen's 10}
|
\section{Heuristic Evaluation: Nielsen's 10}
|
||||||
|
Nielsen's 10 usability heuristics for user interface design are a commonly-applied evaluation framework used by UX professionals to identify common usability issues, and so the application was defined with these heuristics in mind.
|
||||||
|
|
||||||
|
\subsection{Visibility of System Status}
|
||||||
|
\begin{quote}
|
||||||
|
\textit{The design should always keep users informed about what is going on, through appropriate feedback within a reasonable amount of time}
|
||||||
|
\end{quote}
|
||||||
|
|
||||||
|
\subsection{User Control \& Freedom}
|
||||||
|
\begin{quote}
|
||||||
|
\textit{Users often perform actions by mistake. They need a clearly marked "emergency exit" to leave the unwanted action without having to go through an extended process.}
|
||||||
|
\end{quote}
|
||||||
|
|
||||||
|
\subsection{Consistency \& Standards}
|
||||||
|
\begin{quote}
|
||||||
|
\textit{ Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform and industry conventions. }
|
||||||
|
\end{quote}
|
||||||
|
|
||||||
|
\subsection{Error Prevention}
|
||||||
|
\begin{quote}
|
||||||
|
\textit{ Good error messages are important, but the best designs carefully prevent problems from occurring in the first place. Either eliminate error-prone conditions, or check for them and present users with a confirmation option before they commit to the action. }
|
||||||
|
\end{quote}
|
||||||
|
|
||||||
|
\subsection{Recognition Rather than Recall}
|
||||||
|
\begin{quote}
|
||||||
|
\textit{ Minimize the user's memory load by making elements, actions, and options visible. The user should not have to remember information from one part of the interface to another. Information required to use the design (e.g. field labels or menu items) should be visible or easily retrievable when needed. }
|
||||||
|
\end{quote}
|
||||||
|
|
||||||
|
\subsection{Flexibility \& Efficiency of Use}
|
||||||
|
\begin{quote}
|
||||||
|
\textit{ Shortcuts — hidden from novice users — may speed up the interaction for the expert user so that the design can cater to both inexperienced and experienced users. Allow users to tailor frequent actions. }
|
||||||
|
\end{quote}
|
||||||
|
|
||||||
|
\subsection{Aesthetic \& Minimalist Design}
|
||||||
|
\begin{quote}
|
||||||
|
\textit{ Interfaces should not contain information that is irrelevant or rarely needed. Every extra unit of information in an interface competes with the relevant units of information and diminishes their relative visibility. }
|
||||||
|
\end{quote}
|
||||||
|
|
||||||
|
\subsection{Help users Recognise, Diagnose, \& Recover from Errors}
|
||||||
|
\begin{quote}
|
||||||
|
\textit{ Error messages should be expressed in plain language (no error codes), precisely indicate the problem, and constructively suggest a solution. }
|
||||||
|
\end{quote}
|
||||||
|
|
||||||
|
\subsection{Help \& Documentation}
|
||||||
|
\begin{quote}
|
||||||
|
\textit{ It’s best if the system doesn’t need any additional explanation. However, it may be necessary to provide documentation to help users understand how to complete their tasks. }
|
||||||
|
\end{quote}
|
||||||
|
|
||||||
\section{User Evaluation}
|
\section{User Evaluation}
|
||||||
|
|
||||||
\chapter{Conclusion}
|
\chapter{Conclusion}
|
||||||
|
Reference in New Issue
Block a user