\documentclass[11pt,twoside]{article}\makeatletter

\IfFileExists{xcolor.sty}%
  {\RequirePackage{xcolor}}%
  {\RequirePackage{color}}
\usepackage{colortbl}
\usepackage{wrapfig}
\usepackage{ifxetex}
\ifxetex
  \usepackage{fontspec}
  \usepackage{xunicode}
  \catcode`⃥=\active \def⃥{\textbackslash}
  \catcode`❴=\active \def❴{\{}
  \catcode`❵=\active \def❵{\}}
  \def\textJapanese{\fontspec{Noto Sans CJK JP}}
  \def\textChinese{\fontspec{Noto Sans CJK SC}}
  \def\textKorean{\fontspec{Noto Sans CJK KR}}
  \setmonofont{DejaVu Sans Mono}
  
\else
  \IfFileExists{utf8x.def}%
   {\usepackage[utf8x]{inputenc}
      \PrerenderUnicode{–}
    }%
   {\usepackage[utf8]{inputenc}}
  \usepackage[english]{babel}
  \usepackage[T1]{fontenc}
  \usepackage{float}
  \usepackage[]{ucs}
  \uc@dclc{8421}{default}{\textbackslash }
  \uc@dclc{10100}{default}{\{}
  \uc@dclc{10101}{default}{\}}
  \uc@dclc{8491}{default}{\AA{}}
  \uc@dclc{8239}{default}{\,}
  \uc@dclc{20154}{default}{ }
  \uc@dclc{10148}{default}{>}
  \def\textschwa{\rotatebox{-90}{e}}
  \def\textJapanese{}
  \def\textChinese{}
  \IfFileExists{tipa.sty}{\usepackage{tipa}}{}
\fi
\def\exampleFont{\ttfamily\small}
\DeclareTextSymbol{\textpi}{OML}{25}
\usepackage{relsize}
\RequirePackage{array}
\def\@testpach{\@chclass
 \ifnum \@lastchclass=6 \@ne \@chnum \@ne \else
  \ifnum \@lastchclass=7 5 \else
   \ifnum \@lastchclass=8 \tw@ \else
    \ifnum \@lastchclass=9 \thr@@
   \else \z@
   \ifnum \@lastchclass = 10 \else
   \edef\@nextchar{\expandafter\string\@nextchar}%
   \@chnum
   \if \@nextchar c\z@ \else
    \if \@nextchar l\@ne \else
     \if \@nextchar r\tw@ \else
   \z@ \@chclass
   \if\@nextchar |\@ne \else
    \if \@nextchar !6 \else
     \if \@nextchar @7 \else
      \if \@nextchar (8 \else
       \if \@nextchar )9 \else
  10
  \@chnum
  \if \@nextchar m\thr@@\else
   \if \@nextchar p4 \else
    \if \@nextchar b5 \else
   \z@ \@chclass \z@ \@preamerr \z@ \fi \fi \fi \fi
   \fi \fi  \fi  \fi  \fi  \fi  \fi \fi \fi \fi \fi \fi}
\gdef\arraybackslash{\let\\=\@arraycr}
\def\@textsubscript#1{{\m@th\ensuremath{_{\mbox{\fontsize\sf@size\z@#1}}}}}
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\def\abbr{}
\def\corr{}
\def\expan{}
\def\gap{}
\def\orig{}
\def\reg{}
\def\ref{}
\def\sic{}
\def\persName{}\def\name{}
\def\placeName{}
\def\orgName{}
\def\textcal#1{{\fontspec{Lucida Calligraphy}#1}}
\def\textgothic#1{{\fontspec{Lucida Blackletter}#1}}
\def\textlarge#1{{\large #1}}
\def\textoverbar#1{\ensuremath{\overline{#1}}}
\def\textquoted#1{‘#1’}
\def\textsmall#1{{\small #1}}
\def\textsubscript#1{\@textsubscript{\selectfont#1}}
\def\textxi{\ensuremath{\xi}}
\def\titlem{\itshape}
\newenvironment{biblfree}{}{\ifvmode\par\fi }
\newenvironment{bibl}{}{}
\newenvironment{byline}{\vskip6pt\itshape\fontsize{16pt}{18pt}\selectfont}{\par }
\newenvironment{citbibl}{}{\ifvmode\par\fi }
\newenvironment{docAuthor}{\ifvmode\vskip4pt\fontsize{16pt}{18pt}\selectfont\fi\itshape}{\ifvmode\par\fi }
\newenvironment{docDate}{}{\ifvmode\par\fi }
\newenvironment{docImprint}{\vskip 6pt}{\ifvmode\par\fi }
\newenvironment{docTitle}{\vskip6pt\bfseries\fontsize{22pt}{25pt}\selectfont}{\par }
\newenvironment{msHead}{\vskip 6pt}{\par}
\newenvironment{msItem}{\vskip 6pt}{\par}
\newenvironment{rubric}{}{}
\newenvironment{titlePart}{}{\par }

\newcolumntype{L}[1]{){\raggedright\arraybackslash}p{#1}}
\newcolumntype{C}[1]{){\centering\arraybackslash}p{#1}}
\newcolumntype{R}[1]{){\raggedleft\arraybackslash}p{#1}}
\newcolumntype{P}[1]{){\arraybackslash}p{#1}}
\newcolumntype{B}[1]{){\arraybackslash}b{#1}}
\newcolumntype{M}[1]{){\arraybackslash}m{#1}}
\definecolor{label}{gray}{0.75}
\def\unusedattribute#1{\sout{\textcolor{label}{#1}}}
\DeclareRobustCommand*{\xref}{\hyper@normalise\xref@}
\def\xref@#1#2{\hyper@linkurl{#2}{#1}}
\begingroup
\catcode`\_=\active
\gdef_#1{\ensuremath{\sb{\mathrm{#1}}}}
\endgroup
\mathcode`\_=\string"8000
\catcode`\_=12\relax

\usepackage[a4paper,twoside,lmargin=1in,rmargin=1in,tmargin=1in,bmargin=1in,marginparwidth=0.75in]{geometry}
\usepackage{framed}

\definecolor{shadecolor}{gray}{0.95}
\usepackage{longtable}
\usepackage[normalem]{ulem}
\usepackage{fancyvrb}
\usepackage{fancyhdr}
\usepackage{graphicx}
\usepackage{marginnote}

\renewcommand{\@cite}[1]{#1}


\renewcommand*{\marginfont}{\itshape\footnotesize}

\def\Gin@extensions{.pdf,.png,.jpg,.mps,.tif}

  \pagestyle{fancy}

\usepackage[pdftitle={A New View at Usability Test Methods of Interfaces for Human Computer Interaction},
 pdfauthor={}]{hyperref}
\hyperbaseurl{}

	 \paperwidth210mm
	 \paperheight297mm
              
\def\@pnumwidth{1.55em}
\def\@tocrmarg {2.55em}
\def\@dotsep{4.5}
\setcounter{tocdepth}{3}
\clubpenalty=8000
\emergencystretch 3em
\hbadness=4000
\hyphenpenalty=400
\pretolerance=750
\tolerance=2000
\vbadness=4000
\widowpenalty=10000

\renewcommand\section{\@startsection {section}{1}{\z@}%
     {-1.75ex \@plus -0.5ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large\bfseries}}
\renewcommand\subsection{\@startsection{subsection}{2}{\z@}%
     {-1.75ex\@plus -0.5ex \@minus- .2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large}}
\renewcommand\subsubsection{\@startsection{subsubsection}{3}{\z@}%
     {-1.5ex\@plus -0.35ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\large}}
\renewcommand\paragraph{\@startsection{paragraph}{4}{\z@}%
     {-1ex \@plus-0.35ex \@minus -0.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\normalsize}}
\renewcommand\subparagraph{\@startsection{subparagraph}{5}{\parindent}%
     {1.5ex \@plus1ex \@minus .2ex}%
     {-1em}%
     {\reset@font\normalsize\bfseries}}


\def\l@section#1#2{\addpenalty{\@secpenalty} \addvspace{1.0em plus 1pt}
 \@tempdima 1.5em \begingroup
 \parindent \z@ \rightskip \@pnumwidth 
 \parfillskip -\@pnumwidth 
 \bfseries \leavevmode #1\hfil \hbox to\@pnumwidth{\hss #2}\par
 \endgroup}
\def\l@subsection{\@dottedtocline{2}{1.5em}{2.3em}}
\def\l@subsubsection{\@dottedtocline{3}{3.8em}{3.2em}}
\def\l@paragraph{\@dottedtocline{4}{7.0em}{4.1em}}
\def\l@subparagraph{\@dottedtocline{5}{10em}{5em}}
\@ifundefined{c@section}{\newcounter{section}}{}
\@ifundefined{c@chapter}{\newcounter{chapter}}{}
\newif\if@mainmatter 
\@mainmattertrue
\def\chaptername{Chapter}
\def\frontmatter{%
  \pagenumbering{roman}
  \def\thechapter{\@roman\c@chapter}
  \def\theHchapter{\roman{chapter}}
  \def\thesection{\@roman\c@section}
  \def\theHsection{\roman{section}}
  \def\@chapapp{}%
}
\def\mainmatter{%
  \cleardoublepage
  \def\thechapter{\@arabic\c@chapter}
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \pagenumbering{arabic}
  \setcounter{secnumdepth}{6}
  \def\@chapapp{\chaptername}%
  \def\theHchapter{\arabic{chapter}}
  \def\thesection{\@arabic\c@section}
  \def\theHsection{\arabic{section}}
}
\def\backmatter{%
  \cleardoublepage
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \setcounter{secnumdepth}{2}
  \def\@chapapp{\appendixname}%
  \def\thechapter{\@Alph\c@chapter}
  \def\theHchapter{\Alph{chapter}}
  \appendix
}
\newenvironment{bibitemlist}[1]{%
   \list{\@biblabel{\@arabic\c@enumiv}}%
       {\settowidth\labelwidth{\@biblabel{#1}}%
        \leftmargin\labelwidth
        \advance\leftmargin\labelsep
        \@openbib@code
        \usecounter{enumiv}%
        \let\p@enumiv\@empty
        \renewcommand\theenumiv{\@arabic\c@enumiv}%
	}%
  \sloppy
  \clubpenalty4000
  \@clubpenalty \clubpenalty
  \widowpenalty4000%
  \sfcode`\.\@m}%
  {\def\@noitemerr
    {\@latex@warning{Empty `bibitemlist' environment}}%
    \endlist}

\def\tableofcontents{\section*{\contentsname}\@starttoc{toc}}
\parskip0pt
\parindent1em
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\newenvironment{reflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemsep}{0pt}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\itshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{sansreflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\itemsep}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\upshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{specHead}[2]%
 {\vspace{20pt}\hrule\vspace{10pt}%
  \phantomsection\label{#1}\markright{#2}%

  \pdfbookmark[2]{#2}{#1}%
  \hspace{-0.75in}{\bfseries\fontsize{16pt}{18pt}\selectfont#2}%
  }{}
      \def\TheFullDate{2015-01-15 (revised: 15 January 2015)}
\def\TheID{\makeatother }
\def\TheDate{2015-01-15}
\title{A New View at Usability Test Methods of Interfaces for Human Computer Interaction}
\author{}\makeatletter 
\makeatletter
\newcommand*{\cleartoleftpage}{%
  \clearpage
    \if@twoside
    \ifodd\c@page
      \hbox{}\newpage
      \if@twocolumn
        \hbox{}\newpage
      \fi
    \fi
  \fi
}
\makeatother
\makeatletter
\thispagestyle{empty}
\markright{\@title}\markboth{\@title}{\@author}
\renewcommand\small{\@setfontsize\small{9pt}{11pt}\abovedisplayskip 8.5\p@ plus3\p@ minus4\p@
\belowdisplayskip \abovedisplayskip
\abovedisplayshortskip \z@ plus2\p@
\belowdisplayshortskip 4\p@ plus2\p@ minus2\p@
\def\@listi{\leftmargin\leftmargini
               \topsep 2\p@ plus1\p@ minus1\p@
               \parsep 2\p@ plus\p@ minus\p@
               \itemsep 1pt}
}
\makeatother
\fvset{frame=single,numberblanklines=false,xleftmargin=5mm,xrightmargin=5mm}
\fancyhf{} 
\setlength{\headheight}{14pt}
\fancyhead[LE]{\bfseries\leftmark} 
\fancyhead[RO]{\bfseries\rightmark} 
\fancyfoot[RO]{}
\fancyfoot[CO]{\thepage}
\fancyfoot[LO]{\TheID}
\fancyfoot[LE]{}
\fancyfoot[CE]{\thepage}
\fancyfoot[RE]{\TheID}
\hypersetup{citebordercolor=0.75 0.75 0.75,linkbordercolor=0.75 0.75 0.75,urlbordercolor=0.75 0.75 0.75,bookmarksnumbered=true}
\fancypagestyle{plain}{\fancyhead{}\renewcommand{\headrulewidth}{0pt}}

\date{}
\usepackage{authblk}

\providecommand{\keywords}[1]
{
\footnotesize
  \textbf{\textit{Index terms---}} #1
}

\usepackage{graphicx,xcolor}
\definecolor{GJBlue}{HTML}{273B81}
\definecolor{GJLightBlue}{HTML}{0A9DD9}
\definecolor{GJMediumGrey}{HTML}{6D6E70}
\definecolor{GJLightGrey}{HTML}{929497} 

\renewenvironment{abstract}{%
   \setlength{\parindent}{0pt}\raggedright
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
   \textcolor{GJBlue}{\large\bfseries\abstractname\space}
}{%   
   \vskip8pt
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
}

\usepackage[absolute,overlay]{textpos}

\makeatother 
      \usepackage{lineno}
      \linenumbers
      
\begin{document}

             \author[1]{Shana Balchi  }

             \author[2]{Ali Mirarab  }

             \affil[1]{  University of Technology, Qom, Iran.}

\renewcommand\Authands{ and }

\date{\small \em Received: 13 December 2014 Accepted: 5 January 2015 Published: 15 January 2015}

\maketitle


\begin{abstract}
        


As a basic and important term in the interaction design, usability is an overall rating of the degree of use in the human computer interaction, which guarantees the realization of interaction. Usability test is a necessary process in the human computer interface design. It is a process of through systematically collecting the usability data of interface and assessing and improving the data. Designers can enhance the usability through testing and improving the present interface; designers can also evaluate the usability of the present interface, borrowing its strongpoint, improving its shortcomings, and applying in the new design.Conducting sufficient usability test requires planning and attention to the evaluation details.In common, usability test methods for software take into considerations, planning usability questions, selecting a representative sample and recruiting participant s, and preparing the test materials and actualtest environment.In order to make a way to select an appropriate method to perform a usability test, this paper has introduced the usability test methods in the human computer interface design, then analyzed and summarized the methods and finally state of the art taxonomy is presented.

\end{abstract}


\keywords{human computer interaction, usability, test, method, user experience, user interface}

\begin{textblock*}{18cm}(1cm,1cm) % {block width} (coords) 
\textcolor{GJBlue}{\LARGE Global Journals \LaTeX\ JournalKaleidoscope\texttrademark}
\end{textblock*}

\begin{textblock*}{18cm}(1.4cm,1.5cm) % {block width} (coords) 
\textcolor{GJBlue}{\footnotesize \\ Artificial Intelligence formulated this projection for compatibility purposes from the original article published at Global Journals. However, this technology is currently in beta. \emph{Therefore, kindly ignore odd layouts, missed formulae, text, tables, or figures.}}
\end{textblock*}


\let\tabcellsep& 	 	 		 
\section[{Introduction}]{Introduction}\par
sability test is a necessary process in the human computer interface design. It is a process of through systematically collecting the usability data of interface and assessing and improving the data. Designers can enhance the usability through testing and improving the present interface; designers can also evaluate the usability of the present interface, borrowing its strongpoint, improving its shortcomings, and applying in the new design. By doing this, the design of the interface can achieve its usability goal more effectively, reduce the learning time of users, and improve the using efficiency and satisfaction. On the other hand, usability test can also help designers highlight the interface characteristics of the product, reduce the expenditure of development and support, and boost its market competitiveness \hyperref[b0]{[1]}.One of the factors that affect the acceptability of software is its usability. Smith \& Mayes \hyperref[b1]{[2]} state that "usability is now recognized as a vital determining factor in the success of any new computer system or computer-based service."\par
Human computer interface is a medium in the communication, a platform in the flow of information and feedbacks, and a way to interact between human and computer. Human computer interface is also called user interface. A good design of user interface can make the communication more effective, more easily and less mistaking guidance for users. User interface should meet different kinds of proper needs of various users, so the usability research of interface design has become particularly important. As a basic and important term in the interaction design, usability is an overall rating of the degree of use in the human computer interaction, which guarantees the realization of interaction. It is also a quality term from the point of users to evaluate whether the product is effective, easy to learn, safe, efficient, easy to remember and few mistakes or not. Besides, it also needs to consider the expectation and experience of users, which should bring some larruping and unexpected feelings to users \hyperref[b3]{[4]}.\par
The primary goal of usability is to have products developed to maximize the users' ease of use.International Standards Organization in the ISO 9241-11 Guidance of Usability defined usability as "[t]he extent to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use." Jakob Nielsen, in his online column of August 2003, further defined usability by five quality components.\par
The first problem that should be solved is the cognition of users in the usability design of human computer interface. First of all, users must know and understand the interface, and then they can use it. However, how to know the interface depends on how the interface expresses its functions to users. Designers should solve the express of functions by adding less formats and actions, and intentionally design the interface on the basis of goal. Users must clearly understand what the input language needs, which requires approaches to realize functions concisely, and what the output language expresses, which needs understandable and proper feedback channels \hyperref[b4]{[5]}.\par
This paper first look into the give an introduction to usability, then usability testing is discussed in detail. The various methods of usability testing is examined in order to investigate the usability of human-computer interaction interfaces. Evaluation of methods and finally identifying the strengths and weaknesses of the methods is the objectives of this research. 
\section[{II.}]{II.} 
\section[{Usability}]{Usability}\par
Human-Computer-Interaction (HCI) is the area where usability emerged. Several books or papers about HCI present a definition or characterization of usability. For instance, Hix\&Hartson \hyperref[b5]{[6]} consider that usability is related to the interface efficacy and efficiency and to user reaction to the interface. Nielsen  {\ref [7] [8]} integrates usability as one of the parameters associated with system acceptability. He associates five attributes to usability: easy to learn, efficient to use, easy to remember, few errors (the prevention of catastrophic errors is relevant for applications such as process control or medical applications), and pleasant to use.\par
Shackel \hyperref[b8]{[9]} refers to four aspects of interest in usability testing: learnability (easy of learn), throughout, flexibility, and attitude. Rubin \hyperref[b9]{[10]}accepts that usability includes one or more of the four factors outlined by Booth \hyperref[b10]{[11]}: usefulness, effectiveness (ease of use), learnability, and attitude (likeability). For Smith and Mayes \hyperref[b1]{[2]} usability focuses on three aspects: easy to learn, easy to use and user satisfaction in using the system.In international standards, usability refers to effectiveness and efficiency to achieve specified goals and users satisfaction. "Usability:the extent to which a product can be used by specified users to achieve a specified goals with effectiveness, efficiency and satisfaction in a specified context of use" (ISO/DIS 9241-11; European Usability Support Centres).Based on these opinions about usability we may conclude that there are two broad areas to collect relevant data: system and user performance (efficacy, efficiency, easiness to learn and easiness to use) and user satisfaction in using it.\par
The primary goal of usability is to have products developed to maximize the users' ease of use. International Standards Organization in the ISO 9241-11 Guidance of Usability defined usability as "[t]he extent to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use."Jakob Nielsen, in his online column of August 2003, further defined usability by five quality components:\par
1. Learnability: How easy is it for a user to complete a basic task at their first use of a system? 2. Efficiency: How quickly can a user familiar with the system perform tasks? 3. Memorability: How easy is it for a returned user to reestablish proficiency regarding the system? 4. Errors: How many errors does a user make using the system? How severe are the mistakes, and how difficult or easy is it to recover from the mistakes? 5. Satisfaction: How satisfactory is it to use the product?\par
III. 
\section[{Usability Test}]{Usability Test}\par
Usability testing, the process by which products are tested by those who will use them, is intended to help product developers -including information product developers -create, modify, or improve products to better meet the needs of actual or intended users to make those products user-friendly \hyperref[b11]{[12]}.According to Dumas \&Redish \hyperref[b12]{[13]}, authors of A Practical Guide to Usability Testing, usability testing helps product developers determine whether "the people who use the product can do so quickly and easily to accomplish their own tasks". Usability tests identify areas where people struggle with a product and help you make recommendations for improvement. The goal is to better understand how real users interact with your product and to improve the product based on the results. The primary purpose of a usability test is to improve a design. In a typical usability test, real users try to accomplish typical goals, or tasks, with a product under controlled conditions. Researchers, stakeholders, and development team members watch, listen, collect data, and take notes.Since usability testing employs real customers accomplishing real tasks, it can provide objective performance data, such as time on task, errorrate, and task success. There is also no substitute for watching users struggle with or have great success in completing a task when using a product. This observation helps designers and developers gain empathy with users, and help them think of alternative designs that better support tasks and workflow \hyperref[b13]{[14]}.\par
Usability evaluations (UE) consist of methodologies for measuring the usability aspects of a system's user interface (UI) and identifying specific problems.They are an important part of the overall user interface design process, which consists of iterative cycles of designing, prototyping, and evaluating. According to Preece \hyperref[b14]{[15]}, evaluation is concerned with gathering data about the usability of a design or product by a specified group of users for a particular activity within a specified environment or work context. Ivory and Hearst \hyperref[b15]{[17]} suggested that the main activities involved in an evaluation include:\par
? Capture: Collecting usability data, such as task completion time, errors, guideline violations and subjective ratings; ? Analysis: interpreting usability data to identify usability problems in the interface; ? Critique: suggest solutions or improvements to mitigate problems.\par
Usability test is a necessary process in the human computer interface design. It is a process of through systematically collecting the usability data of interface and assessing and improving the data. Designers can enhance the usability through testing and 
\section[{Global Journal of C omp uter S cience and T echnology}]{Global Journal of C omp uter S cience and T echnology}\par
Volume XV Issue I Version I Year ( ) A improving the present interface; designers can also evaluate the usability of the present interface, borrowing its strongpoint, improving its shortcomings, and applying in the new design. By doing this, the design of the interface can achieve its usability goal more effectively, reduce the learning time of users, and improve the using efficiency and satisfaction. On the other hand, usability test can also help designers highlight the interface characteristics of the product, reduce the expenditure of development and support, and boost its market competitiveness \hyperref[b0]{[1]}.\par
IV. 
\section[{Usability Test Methods}]{Usability Test Methods}\par
In this section, we present countermeasure methods that have been proposed for Usability testing. A comparison and critical discussion on the proposed ideas will be detailed in section 6. 
\section[{a) Heuristic evaluation Method}]{a) Heuristic evaluation Method}\par
Heuristic evaluation is an informal system inspection method where a small group of evaluators are presented with an interface design and asked to judge whether each of its elements follows a set of established usability principles \hyperref[b16]{[18]}. The method is intended to be a "discount usability engineering" method \hyperref[b16]{[18]} that provides a way to do a usability evaluation more quickly, and with less cost. Because of its "discount" nature, heuristic evaluation was found to be the most commonly used UEM in a survey to the practitioners \hyperref[b17]{[19]}.Heuristic evaluation can be performed by experts and non-experts. It is difficult to do a heuristic evaluation with a single evaluator; it is near impossible for one person to find all usability problems. Yet it has been shown that when there are multiple evaluators, each were able to find different usability problems, thus the effectiveness of the problem can be improved by having a group of evaluators. Usually, 4 or 5 evaluators are able to report near 70\% of the usability problems; additional evaluators often are not able find much more additional problems \hyperref[b18]{[20]}  \hyperref[b16]{[18]}.The main advantage of heuristic evaluation is its ability to be done in a short period of time with limited resources. The method is also very flexible and does not require advanced planning; it could be carried out as soon as the group of evaluators is assembled and that there is a product or a prototype to evaluate. Heuristic evaluation has also proved to be highly effective in finding usability problems \hyperref[b19]{[21]}  \hyperref[b20]{[22]}. However, there are also several drawbacks. The effectiveness depends largely on the evaluators' skill and experience. Though non-experts are able to perform the evaluation as well as experts, it is very likely that they would not be able to find as many usability problems as the experts. A "bad" evaluator is also more likely to miss the problems that a better evaluator did not pick up, thus lowering the aggregated count of problems found \hyperref[b16]{[18]}.The flexibility given to the evaluators, allowing them to inspect the system anyway they want also means a lack of support and structure to the inspection process \hyperref[b22]{[23]}. When the evaluators are not well informed about the product domain, the inspection may be not as effective. 
\section[{b) Cognitive walkthrough Method}]{b) Cognitive walkthrough Method}\par
Cognitive walkthrough \hyperref[b23]{[24]} [25] \hyperref[b25]{[26]} is a theoretically structured usability evaluation process that focuses on a user's cognitive activities, especially while performing a task. It can be carried out by individuals or groups, software developers or usability specialists, and on finished products or paper prototypes. Based on a theory of exploratory learning and corresponding interface design guidelines, cognitive walkthrough is a task-based methodology that centers an evaluator's attention on the user's goals and actions during a task, and on whether the system design supportsor hinders the effective accomplishment of those goals. Moreover, it is a form-based evaluation methodology in which relies on a set of forms to guide the evaluation process. The theory behind the method describes humancomputer interaction in four steps: the user sets a goal to be accomplished with the system, the user searches the interface for action options, the user selects the action that seems to make progress towards the goal, and finally the user performs the action and evaluates the system feedback \hyperref[b26]{[27]}.\par
Cognitive walkthrough has shown to be an effective UEM \hyperref[b23]{[24]}.It also provided an option for evaluating a system in early development with relatively lower cost. But the details of the procedure created difficulties in its execution. The walkthrough methodology presupposes knowledge of cognitive science terms, concepts, and skills from the evaluators \hyperref[b24]{[25]}. A lack of familiarity with the terminologies in the form, such as the definitions of goal and action, could lead to misunderstandings and affect the outcome. At least one evaluator needs to be familiar with the concepts of the cognitive walkthrough theory, and the cognitive science terminologies used during the process in order for the walkthrough to be effective. Lewis et al. \hyperref[b23]{[24]} conducted cognitive walkthrough with four evaluators, three of which have deep understandings of the core principles of the theory. Throughout the walkthrough, there was a high level of agreement among the three evaluators, but less with the fourth. The fourth evaluator also found fewer errors that the other evaluators \hyperref[b26]{[27]}. 
\section[{c) Scenario-based Method}]{c) Scenario-based Method}\par
Scenario-based methods is the description of people using technology and it is essential in discussing and analyzing how the technology is (or could be) used to reshape their activities. A scenario describes a sequence of events when interacting with a system from the users' perspective and the scenario descriptions can be created before a system is built and its impacts felt. 'Scenarios' are similar to 'Use Cases', which describe interactions at a technical level, but scenarios can be easily understood by anyone regardless of the level of their technical knowledge. Scenarios are especially useful when you need to remove the focus from the technology in order to consider other design possibilities. Scenarios focus in terms of tasks rather than the technology used to support them. E.g. "User enters his pin" is incorrect because it mentions the technology used, whereas "User identifies himself" is okay because it keeps open other alternatives \hyperref[b27]{[28]}. 
\section[{d) Remote Testing Usability Method}]{d) Remote Testing Usability Method}\par
Most of the time, usability evaluations are conduct dinausability laboratory. People that were recruited are invited to come to the test facilities consisting of a test room, where the participants will accomplish specific tasks, an observation room and the "recording" room. A usability laboratory may contain complex and sophisticated audio/visual recordings and analysis facilities. In this context, test sessions are conducted individually. Although this situation has advantages it also has drawbacks, as we will see. Remote usability evaluation refers to a situation in which the evaluators and the test participants are not in the same roomor location. Two approaches to remote usability evaluation have been developed: synchronous and asynchronous. Each approach uses specific tools. In the synchronous approach, a facilitator and the evaluators collect the data and manage the evaluation session in real time with a participant who is remote (the participant may be at home, at work or in another room). The evaluation may require video conferencing applications or remote applications sharing tools that allow to share computer screens so as to allow the evaluator to see what is happening on the user's screen. Incontrast, with a synchronous methods, observers do not have access to the data in real time, and there is no facilitator interacting with the user during data collection. Asynchronous methods also include auto mated approaches, where by users' click streams are collected automatically (e.g., Web Quilt). The key advantage this technique offers is that many more test users can participate (in parallel), with little or no incremental cost per participant. For conducting these asynchronous tests, different strategies have been proposed. One strategy is to ask test participants to download and use an instrumented browser that will capture the users' click streams as well as screen shots, and transmit those data to the evaluator's host site for analysis (an example of this kind of browser is Ergo Browser, http://www.ergolabs.com/resources.htm).Anotherapproa ch consists in using a proxy. The test participants are invited to go to a specific Website and then to follow instructions. They are then brought to the Website under evaluation. The users' behaviors are captured, aggregated and visualized to show the web pages people explored. The visualization also shows the most common paths taken through the website for a given task, as well as the optimal path for that task as implemented by the designer \hyperref[b28]{[29]}.An example of this kind of approach is Web Quilt \hyperref[b29]{[30]} and the work by Atterer, Wnukand Schmidt \hyperref[b30]{[31]}.\par
The asynchronous approach does not allow for observational data and recordings of spontaneous verbalizations during the remote test sessions. The qualitative data can only be recorded through post-test questionnaires or self-report forms. However, the asynchronous approach allows the recording of large groups of users as we said. The synchronous approach is favored by some authors \hyperref[b31]{[32]} because it is analogous to laboratory testing and because it allows the capture of qualitative data. Incomparison to the laboratory user test, the synchronous remote testing is cost effective, especially for travel expenses when participants are recruited in different region in a given country. However, the costs associated with this approach may in some cases be quite similar to those of the laboratory testing (for the recruitment for instance). Two other reasons for preferring the remote synchronous approach to traditional user testing is the freedom from facilities (especially when the product or software can be distributed electronically or when testing a Website) and time saving. However synchronous remote testing can be perceived as more intrusive than traditional laboratory user testing \hyperref[b28]{[29]}. 
\section[{e) User-based Testing Method}]{e) User-based Testing Method}\par
User-based evaluations are usability evaluation methods in which users directly participate. Users are invited to do typical tasks with a product, or simply asked to explore it freely, while their behaviors are observed and recorded in order to identify design flaws that cause user errors or difficulties. During these observations, the time required to complete a task, taskcompletion rates, and number and types of errors, are recorded. Once design flaws have been identified, design recommendations are proposed to improve the ergonomic quality of the product \hyperref[b28]{[29]}. User testing is centered on the feedback of users interacting with a particular interface and is "usually conducted in a scenario-based environment" \hyperref[b32]{[33]}. User testing is good at "assessing the system in action, at identifying problems users experience while performing real tasks" \hyperref[b33]{[34]}. Also, internal issues can be detected quickly and potential problems can be fixed before the product ever reaches the market. User testing on the other hand is not 100\% representative of the target population. The method is qualitative and therefore does not provide large samples of feedback. User testing on the other hand revealed more detail level problems of the interface because it required the users to enact the system at the task level. Despite the fact that user testing identified fewer problems,most were directly related to the true performance and/or user acceptance 
\section[{Year ( )}]{Year ( )}\par
A of the interface. In addition, it is assumed that user testing is time consuming \hyperref[b34]{[35]}. f) Focus group method A focus group is a meeting of about six to nine users wherein users discuss issues relating to the system. The evaluator plays the role of the moderator (i.e., asks about pre-determined issues) and gathers the needed information from the discussion. This is valuable for improving the usability of future releases. This method is a technique used to study human-computer interaction and human factors \hyperref[b35]{[36]}. A traditional focus group is done by inviting a small group of end users in to talk about a product. The discussion is presided over by an experienced moderator, and held in a room with a one-way observation mirror. The moderator takes notes of the happenings, leads the conversation into interesting tangents, encourages comments, prevents the discussion to be dominated by few of the participants, and all the while avoid having any effects on the session's outcome. Some practitioners believe that with well planning, proper guidelines and a good moderator, focus groups can gather valuable usability data.They believe that though it is not suited for comparative, competitive, or bench-marking studies, focus groups can be used to generate ideas, capture and validate user roles as well as tasks and workflows, and validate high level strategy. However, there are also some major drawbacks that led many practitioners to question its validity in gathering useful user data \hyperref[b26]{[27]}.Rauch \hyperref[b36]{[37]} stated that "? the quality of the data obtained from usability focus groups is only as good as the quality of the participant selection and the questions asked." g) Contextual inquiry method Raven and Flanders \hyperref[b38]{[38]} defines contextual inquiry as "a qualitative data-gathering and dataanalysis methodology adapted from the fields of psychology, anthropology, and sociology." It is a field research method wherein usability evaluators go to the users' workplaces, observes them at work, and asks questions regarding to the work content, process, or product usage. Several evaluators may observe different users at the same time. The data is gathered, compared and shared among product development team members after the observation \hyperref[b26]{[27]}. It provides product designers an understanding of user work and usability; and further suggests generic principles of usability and work concepts that might become the initial frame work of new products \hyperref[b39]{[39]}.It is a structured field interviewing method, Contextual inquiry is based on three core principles: 1) understanding the context in which a product is used (the work being performed) is essential for elegant design, 2) that the user is a partner in the design process, 3) that the usability design processes, including assessment methods like contextual inquiry and usability testing, must have a focus. Contextual inquiry may take hours to months or even years to complete; it is a significant time investment to ask for and it is best used in the early stages of development to help develop product design guidelines  {\ref [40]}. 
\section[{h) Model-based evaluation method}]{h) Model-based evaluation method}\par
Model-based evaluation methods can predict measures such as the time to complete a task or the difficulty of learning to use an interface. Some models have the potential advantage that they can be used without the need for any prototype to be developed. Models and simulations uses to evaluation when models can be constructed economically and user testing is not practical. However, setting up a model currently usually requires considerable effort, so model-based methods are cost effective in situations where other methods are impracticable, or the information provided by the model is a cost-effective means of managing particular risks [41].\par
V. 
\section[{Evaluation Criteria for Usability Testing Methods}]{Evaluation Criteria for Usability Testing Methods}\par
Usability testing evaluation criteria will be described in this section. The criteria listed below are most common criteria that discussed in articles and researches with considering all usability test aspect. High Velocity: The time which takes to complete a task done.\par
Low Cost: Costs required for testing (Building and maintenance of laboratory, equipment, the cost of users, costs related to the location and time that employees spend for meetings).\par
Flexibility: The ability of the method to handle the limitation in the use of a special tool or framework and change in it.\par
Resource Requirements: In usability test terminology, resources are required to carry out the test tasks. They can be people, equipment, facilities, funding, or anything else capable of definition required for the completion of test activities.\par
How Many to Test: The number of participants who work with products. Each test methods requires different numbers of users, managers, observers, evaluator or scenario that the exact number of people required to perform each test is still not completely understood.\par
Test Type: Two main approaches to consider the usability of the system are: Experimental and Analytical. The experimental procedure consists of testing systems with users while the analytical method includes the systems evaluation by using the created theories and methods.\par
Impact of evaluators experience on test results: In the some methods for usability testing groupthink, evaluators experience and expertise, view of observers and other people involved in the testing process will affect the test results.\par
Level of found problems: A usability problem is an aspect of the system and/ or a demand on the user which makes it unpleasant, inefficient, onerous or impossible for the user to achieve their goals in typical usage situations. In this paper usability problems categorize to two level: major and minor.\par
Method purpose: The method purpose parameter specifies the basic building blocks of the discussed methods for usability test. The method purpose parameter is included to identify the evaluation requirements of the discussed us ability test methods. 
\section[{VI.}]{VI.} 
\section[{Evaluation and Discussion}]{Evaluation and Discussion}\par
All the methods discussed under the category of usability testing methods have been presented in Table \hyperref[tab_0]{1} chronologically. Each method has been evaluated with reference to evaluation criteria discussed in Section 5.  
\section[{Conclusion}]{Conclusion}\par
The usability design of human computer interface determines the market prospect of the product. Designers should be guided by the natural and human idea, also designers should optimize the use and operation of interface from many different areas, such as design, ergonomics, cognitive psychology, linguistics and semiotic, ultimately achieve the ideal goal of improving the usability of products.Usability evaluation is occupying a central part of software development based on the results extracted from quantitative and qualitative evaluations.This paper introduced and compared the some methods for conducting usability testing which most widely used in human-computer interaction user interfaces.The slandered evaluation criteria related with usability was addressed in this paper based on the previous researches. Based on the data collected, it was found that each method has unique advantages and limitations.According to the investigated research in this paper, none of these methods none of these methods is superior over others. In fact, the degree to which each of usability testing methods identify problems in the system depends on a number of factors and levels of complexity. 
\section[{Global Journal of C omp uter S cience and T echnology}]{Global Journal of C omp uter S cience and T echnology}\par
Volume XV Issue I Version I Year ( ) A\begin{figure}[htbp]
\noindent\textbf{1} \par 
\begin{longtable}{P{0.1434375\textwidth}P{0.025044642857142856\textwidth}P{0.02125\textwidth}P{0.024285714285714285\textwidth}P{0.041741071428571426\textwidth}P{0.056160714285714286\textwidth}P{0.07513392857142857\textwidth}P{0.16544642857142858\textwidth}P{0.01669642857142857\textwidth}P{0.03794642857142857\textwidth}P{0.0015178571428571428\textwidth}P{0.23450892857142858\textwidth}P{0.006830357142857142\textwidth}}
\tabcellsep High\tabcellsep Low\tabcellsep Flexibility\tabcellsep Resource\tabcellsep How Many\tabcellsep Test Type\tabcellsep Impact\tabcellsep of\tabcellsep Level\tabcellsep of\tabcellsep Method\\
\tabcellsep Velocity\tabcellsep Cost\tabcellsep \tabcellsep Requirements\tabcellsep to Test\tabcellsep \tabcellsep \multicolumn{2}{l}{evaluators}\tabcellsep found\tabcellsep \tabcellsep purpose\\
\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \multicolumn{2}{l}{experience}\tabcellsep \multicolumn{2}{l}{problems}\\
\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep on\tabcellsep test\tabcellsep \tabcellsep \\
\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep results\tabcellsep \tabcellsep \tabcellsep \\
Heuristic\tabcellsep Yes\tabcellsep Yes\tabcellsep Yes\tabcellsep Low\tabcellsep 3-5\tabcellsep Experimental\tabcellsep The\tabcellsep more\tabcellsep Major\tabcellsep \tabcellsep Provide\\
evaluation\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep Evaluator\tabcellsep \tabcellsep \multicolumn{2}{l}{experienced}\tabcellsep \tabcellsep \tabcellsep expert\\
Method\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \multicolumn{2}{l}{evaluators,}\tabcellsep \tabcellsep \tabcellsep feedback\\
\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \multicolumn{2}{l}{find problems}\tabcellsep \tabcellsep \tabcellsep on\tabcellsep user\\
\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep more\tabcellsep and\tabcellsep \tabcellsep \tabcellsep interfaces\\
\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep better\tabcellsep \tabcellsep \tabcellsep \\
Cognitive\tabcellsep No\tabcellsep Yes\tabcellsep No\tabcellsep Medium\tabcellsep 4\tabcellsep Analytical\tabcellsep If\tabcellsep the\tabcellsep Minor\tabcellsep \tabcellsep Check\\
walkthrough\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep Evaluator\tabcellsep \tabcellsep \multicolumn{2}{l}{evaluators}\tabcellsep \tabcellsep \tabcellsep structure\\
Method\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep are\tabcellsep not\tabcellsep \tabcellsep \tabcellsep and\\
\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \multicolumn{2}{l}{familiar with}\tabcellsep \tabcellsep \tabcellsep countercurr\\
\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep specific\tabcellsep \tabcellsep \tabcellsep \tabcellsep ent flow of\\
\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \multicolumn{2}{l}{concepts and}\tabcellsep \tabcellsep \tabcellsep user goals\\
\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \multicolumn{2}{l}{principles of}\tabcellsep \tabcellsep \\
\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \multicolumn{2}{l}{method, test}\tabcellsep \tabcellsep \\
\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep is\tabcellsep not\tabcellsep \tabcellsep \\
\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \multicolumn{2}{l}{conducted}\tabcellsep \tabcellsep \\
\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep well\tabcellsep \tabcellsep \tabcellsep \\
Scenario-\tabcellsep Yes\tabcellsep Yes\tabcellsep No\tabcellsep Medium\tabcellsep 3-4\tabcellsep Analytical\tabcellsep -\tabcellsep \tabcellsep Minor\tabcellsep \tabcellsep Requireme\\
based\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep Scenario\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep nts\\
Method\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep description\\
\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep and\\
\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep conceptual\\
\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep design\\
\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep support\\
Remote\tabcellsep Yes\tabcellsep Yes\tabcellsep Yes\tabcellsep Medium\tabcellsep -\tabcellsep Experimental\tabcellsep -\tabcellsep \tabcellsep -\tabcellsep \tabcellsep -\\
Testing\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \\
Usability\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \\
Method\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \\
User-based\tabcellsep No\tabcellsep No\tabcellsep Yes\tabcellsep High\tabcellsep 8 User\tabcellsep Experimental\tabcellsep \tabcellsep \tabcellsep Minor\tabcellsep \tabcellsep Measuring\\
Testing\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep usability\\
Method\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep and\\
\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep interaction\\
\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep problems\\
Focus group\tabcellsep Yes\tabcellsep Yes\tabcellsep Yes\tabcellsep Low\tabcellsep 1\tabcellsep Experimental\tabcellsep \multicolumn{2}{l}{Sometimes}\tabcellsep Minor\tabcellsep \tabcellsep Extraction\\
method\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep Manager,\tabcellsep \tabcellsep \multicolumn{2}{l}{groupthink}\tabcellsep \tabcellsep \tabcellsep requiremen\\
\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep 6-4 User\tabcellsep \tabcellsep prevents\tabcellsep \tabcellsep \tabcellsep \tabcellsep ts / user\\
\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep proper\tabcellsep \tabcellsep \tabcellsep \tabcellsep views\\
\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep testing\tabcellsep \tabcellsep \tabcellsep \tabcellsep through\\
\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep discussion\\
Contextual\tabcellsep No\tabcellsep No\tabcellsep Yes\tabcellsep Medium\tabcellsep -\tabcellsep Experimental\tabcellsep High\tabcellsep \tabcellsep Minor\tabcellsep \tabcellsep Provide\\
inquiry\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep information\\
method\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep about the\\
\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep user's field\\
Model-based\tabcellsep Yes\tabcellsep No\tabcellsep No\tabcellsep -\tabcellsep -\tabcellsep Analytical\tabcellsep -\tabcellsep \tabcellsep -\tabcellsep \tabcellsep Find\\
evaluation\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep learning\\
method\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep problems\\
\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep in\tabcellsep using\\
\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep the\\
\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep interface\end{longtable} \par
 
\caption{\label{tab_0}Table 1 :}\end{figure}
 			\footnote{© 2015 Global Journals Inc. (US) 1} 			\footnote{© 2015 Global Journals Inc. (US)} 		 		\backmatter  			  				\begin{bibitemlist}{1}
\bibitem[Nielsen and Engineering ()]{b5}\label{b5} 	 		\textit{},  		 			J Nielsen 		,  		 			Usability Engineering 		.  		1993. New Jersey: Academic Press.  	 
\bibitem[Doubleday ()]{b31}\label{b31} 	 		‘A comparison of usability techniques for evaluation design’.  		 			Doubleday 		.  	 	 		\textit{Northampton Square}  		2009.  		 			School of Informatics, City University 		 	 
\bibitem[Preece ()]{b13}\label{b13} 	 		\textit{A guide to usability. Human factors in computing},  		 			J Preece 		.  		1993. Addison-Wesley.  	 
\bibitem[Dumas and &redish ()]{b11}\label{b11} 	 		\textit{A practical guide to usability testing},  		 			J S Dumas 		,  		 			J C \&redish 		.  		1993. Norwood, NJ: Ablex Publishing Company. p. 4.  	 
\bibitem[Tsai ()]{b24}\label{b24} 	 		‘A survey of empirical usability evaluation methods’.  		 			Peishan Tsai 		.  	 	 		\textit{GSLIS Independent Study},  				2006.  	 
\bibitem[Rosenbaum et al. (2000)]{b15}\label{b15} 	 		‘A toolkit for strategic usability: results from workshops, panels, and surveys’.  		 			S Rosenbaum 		,  		 			J A Rohn 		,  		 			J Humburg 		.  	 	 		\textit{Proceedings of the SIGCHI Conference on Human Factors in Computing Systems},  				 (the SIGCHI Conference on Human Factors in Computing SystemsThe Hague, The Netherlands; New York, NY)  		2000. April 01 -06, 2000. ACM Press.  	 	 (CHI '00. Retrieved on 9/30/05, from ACM Portal) 
\bibitem[Booth ()]{b9}\label{b9} 	 		\textit{An Introduction to Human-Computer Interaction},  		 			P Booth 		.  		1989. London: Lawrence ErlbaumAssociates.  	 
\bibitem[Law and Hvannberg (2004)]{b19}\label{b19} 	 		‘Analysis of strategies for improving and estimating the effectiveness of heuristic evaluation’.  		 			E L Law 		,  		 			E T Hvannberg 		.  	 	 		\textit{Proceedings of the Third Nordic Conference on Human-Computer interaction},  				 (the Third Nordic Conference on Human-Computer interactionTampere, Finland; New York, NY)  		2004. October 23 -27, 2004. ACM Press. 82 p. .  	 	 (NordiCHI '04. Retrieved on 10/15/05, from ACM Portal) 
\bibitem[Wharton et al. ()]{b22}\label{b22} 	 		‘Applying cognitive walkthroughs to more complex user interfaces: experiences, issues, and recommendations’.  		 			C Wharton 		,  		 			J Bradford 		,  		 			R Jeffries 		,  		 			M Franzke 		.  	 	 		\textit{Proceedings of the SIGCHI Conference on Human Factors in Computing Systems},  				 			P Bauersfeld,  			J Bennett,  			G Lynch 		 (ed.)  		 (the SIGCHI Conference on Human Factors in Computing SystemsMonterey, California, United States; New York, NY)  		May 03 -07, 1992. ACM Press. p. .  	 	 (CHI '92. Retrieved on 9/30/05, from ACM Portal) 
\bibitem[Nicusebe ()]{b3}\label{b3} 	 		\textit{Computer Vision in Human-computer Interaction},  		 			Nicusebe 		.  		2005. Germany: Springer.  	 
\bibitem[Wixon et al. (1990)]{b36}\label{b36} 	 		‘Contextual design: an emergent view of system design’.  		 			D Wixon 		,  		 			K Holtzblatt 		,  		 			S Knox 		.  	 	 		\textit{Proceedings of the SIGCHI Conference on Human Factors in Computing Systems: Empowering People},  				 (the SIGCHI Conference on Human Factors in Computing Systems: Empowering PeopleSeattle, Washington, United States)  		1990. April 01 -05, 1990.  	 
\bibitem[Hix and &hartson ()]{b4}\label{b4} 	 		\textit{Developing User Interfaces: Ensuring Usability through Product and Process},  		 			D Hix 		,  		 			H \&hartson 		.  		1993. New York: John Wiley \& Sons.  	 
\bibitem[Rosenbaum et al. (2002)]{b34}\label{b34} 	 		‘Focus groups in HCI: wealth of information or waste of resources’.  		 			S Rosenbaum 		,  		 			G Cockton 		,  		 			K Coyne 		,  		 			M Muller 		,  		 			T Rauch 		.  	 	 		\textit{CHI '02 Extended Abstracts on Human Factors in Computing Systems},  				 (Minneapolis, Minnesota, USA; New York, NY)  		2002. April 20 -25, 2002. ACM Press. p. .  	 	 (CHI '02. Retrieved on 11/11/05, from ACM Portal) 
\bibitem[Rubin ()]{b8}\label{b8} 	 		\textit{Handbook of Usability Testing},  		 			J Rubin 		.  		1994. New York: John Wiley and Sons.  	 
\bibitem[Nielsen and Molich (1990)]{b16}\label{b16} 	 		‘Heuristic Evaluation of User Interfaces’.  		 			J Nielsen 		,  		 			R Molich 		.  	 	 		\textit{Proceedings of the SIGCHI Conference on Human Factors in Computing Systems: Empowering People},  				 			J C Chew,  			J Whiteside 		 (ed.)  		 (the SIGCHI Conference on Human Factors in Computing Systems: Empowering PeopleSeattle, Washington, United States; New York, NY)  		1990. April 01 -05, 1990. ACM Press. p. .  	 	 (CHI '90. Retrieved on 10/10/05, from ACM Portal) 
\bibitem[Shackel ()]{b7}\label{b7} 	 		‘Human factors and usability’.  		 			B Shackel 		.  	 	 		\textit{human-Computer Interaction: Selected Readings},  				 			J Preece,  			L Keller 		 (ed.)  		 (London)  		1990. Prentice Hall. p. .  	 
\bibitem[Chao (2009)]{b2}\label{b2} 	 		‘Human-computer interaction: The usability test methods and design principles in the human-computer interface design’.  		 			Gong Chao 		.  	 	 		\textit{2nd IEEE International Conference on},  				2009. 2009. 8-11 Aug. 2009. 285 p. 283.  	 
\bibitem[Chao (2009)]{b0}\label{b0} 	 		‘Human-computer interaction: The usability test methods and design principles in the human-computer interface design’.  		 			Gong Chao 		.  	 	 		\textit{2nd IEEE International Conference on},  				2009. 2009. Aug. 2009. 285 p. .  	 
\bibitem[Atterer et al. ()]{b28}\label{b28} 	 		‘Knowing the User's every move -User activity tracking for Website usability evaluation and implicit interaction’.  		 			R Atterer 		,  		 			M Wnuk 		,  		 			A Schmidt 		.  	 	 		\textit{Proceedings of the 15th International Conference on World Wide Web},  				 (the 15th International Conference on World Wide WebEdinburgh, Scotland; New York, NY)  		May 23-26. 2006. ACM. p. .  	 
\bibitem[Nielsen ()]{b6}\label{b6} 	 		 			J Nielsen 		,  		 			Multimedia 		.  		\textit{Hypertext: the Internet and beyond},  				 (Boston)  		1995. AP Professional.  	 
\bibitem[Dray and Siegel (2004)]{b29}\label{b29} 	 		‘Remote possibilities? International usability testing at a distance’.  		 			S Dray 		,  		 			D Siegel 		.  	 	 		\textit{interactions}  		2004. march + april. p. .  	 
\bibitem[Rosson and Carroll ()]{b25}\label{b25} 	 		‘Scenario-based design’.  		 			Mary Beth Rosson 		,  		 			John M Carroll 		.  	 	 		\textit{The human-computer interaction handbook},  				 			Julie A Jacko,  			Andrew Sears 		 (ed.)  		 (Hillsdale, NJ, USA)  		2002. p. .  	 
\bibitem[Smith and Mayes ()]{b1}\label{b1} 	 		 			C \& T Smith 		,  		 			Mayes 		.  		\textit{Telematics Applications for Education and Training: Usability Guide. Commission of the European Communities, DGXIII Project},  				1996.  	 
\bibitem[Lewis et al. (1990)]{b20}\label{b20} 	 		‘Testing a walkthrough methodology for theory-based design of walk-up-and-use interfaces’.  		 			C Lewis 		,  		 			P Polson 		,  		 			C Wharton 		,  		 			J Rieman 		.  	 	 		\textit{Proceedings of the SIGCHI Conference on Human Factors in Computing Systems: Empowering People},  				 (the SIGCHI Conference on Human Factors in Computing Systems: Empowering PeopleSeattle, Washington, United States)  		1990. April 01 -05, 1990.  	 
\bibitem[Petrie and Bevan ()]{b39}\label{b39} 	 		‘The evaluation of accessibility, usability and user experience’.  		 			Helen Petrie 		,  		 			Nigel Bevan 		.  	 	 		\textit{The universal access handbook},  				2009. CRC Press. p. .  	 
\bibitem[Holtzblatt and Beyer ()]{b38}\label{b38} 	 		‘The Interaction Design Foundation’.  		 			Karen Holtzblatt 		,  		 			Hugh R Beyer 		.  		 \url{https://www.interaction-design.org/encyclopedia/contextual\textunderscore design.html}  	 	 		\textit{The Encyclopedia of Human-Computer Interaction},  				 			Mads Soegaard,  			Rikkefriis Dam 		 (ed.)  		 (Aarhus, Denmark)  		2014.  	 	 (Contextual Design. 2nd Ed) 
\bibitem[Ivory et al. (1992)]{b14}\label{b14} 	 		‘The State of the Art in Automating Usability Evaluation of User Interfaces’.  		 			Melody Y Ivory 		,  		 			Marti Hearst 		,  		 			J Nielsen 		.  	 	 		\textit{Proceedings of the SIGCHI Conference on Human Factors in Computing Systems},  				 			P Bauersfeld,  			J Bennett,  			G Lynch 		 (ed.)  		 (the SIGCHI Conference on Human Factors in Computing SystemsMonterey, California; New York, NY)  		December 2001. 2001. 1992. May 03 -07, 1992. ACM Press. 16 p. .  	 	 (CHI '92. Retrieved on 9/30/05, from ACM Portal) 
\bibitem[Usability Evaluation of User Interfaces, Melody Yvette Ivory, PhD Dissertation ()]{b33}\label{b33} 	 		\textit{Usability Evaluation of User Interfaces, Melody Yvette Ivory, PhD Dissertation},  		2001. 2.  		 			UC Berkeley Computer Science Division 		 	 	 (An Empirical Foundation for Automated Web Interface Evaluation) 
\bibitem[Rieman et al. ()]{b23}\label{b23} 	 		‘Usability evaluation with the cognitive walkthrough’.  		 			J Rieman 		,  		 			M Franzke 		,  		 			D Redmiles 		.  	 	 		\textit{Conference Companion on Human Factors in Computing Systems},  				 			I Katz,  			R Mack,  			L Marks 		 (ed.)  		 (New York, NY)  		1995. ACM Press. p. .  	 	 (CHI '95. Retrieved on 9/30/05, from ACM Portal) 
\bibitem[Kantner and Rosenbaum (1997)]{b18}\label{b18} 	 		‘Usability studies of WWW sites: heuristic evaluation vs. laboratory testing’.  		 			L Kantner 		,  		 			S Rosenbaum 		.  	 	 		\textit{Proceedings of the 15th Annual international Conference on Computer Documentation},  				 (the 15th Annual international Conference on Computer DocumentationSalt Lake City, Utah, United States; New York, NY)  		1997. October 19 -22, 1997. ACM Press. p. .  	 	 (SIGDOC '97. Retrieved on 9/30/05, from ACM Portal) 
\bibitem[Smith ()]{b12}\label{b12} 	 		\textit{Usability Testing Basics, An Overview},  		 			Tech Smith 		.  		 \url{http://www.techsmith.com}  		2009.  	 
\bibitem[Usability Testing: Developing Useful and Usable Products (2002)]{b10}\label{b10} 	 		\textit{Usability Testing: Developing Useful and Usable Products},  				October 2002.  		 			Master of Technical andScientific Communication Program Miami University of Ohio 		 	 
\bibitem[Christian Bastien ()]{b26}\label{b26} 	 		\textit{Usability testing: some current practices and research questions},  		 			J M Christian Bastien 		.  		2010.  	 
\bibitem[Jeffries et al. (1991)]{b17}\label{b17} 	 		‘User interface evaluation in the real world: a comparison of four techniques’.  		 			R Jeffries 		,  		 			J R Miller 		,  		 			C Wharton 		,  		 			K Uyeda 		.  	 	 		\textit{Proceedings of the SIGCHI Conference on Human Factors in Computing Systems: Reaching Through Technology},  				 			S P Robertson,  			G M Olson,  			J S Olson 		 (ed.)  		 (the SIGCHI Conference on Human Factors in Computing Systems: Reaching Through TechnologyNew Orleans, Louisiana, United States; New York, NY)  		1991. April 27 -May 02, 1991. ACM Press. p. .  	 	 (CHI '91. Retrieved on 9/30/05, from ACM Portal) 
\bibitem[Raven and Flanders ()]{b35}\label{b35} 	 		‘Using contextual inquiry to learn about your audiences’.  		 			M E Raven 		,  		 			A Flanders 		.  	 	 		\textit{SIGDOC Asterisk Journal of Computer Documentation}  		1996. 20  (1)  p. .  	 	 (Retrieved on 10/1/05, from ACM Portal) 
\bibitem[Tan et al. ()]{b30}\label{b30} 	 		‘Web evaluation: Heuristic evaluation vs. user testing’.  		 			W Tan 		,  		 			D Liu 		,  		 			R \&bishu 		.  	 	 		\textit{International Journal of Industrial Ergonomics}  		2009. 39 p. .  	 
\bibitem[Smith (2010)]{b32}\label{b32} 	 		\textit{Web Page Design: Heuristic Evaluation vs. User Testing},  		 			John Smith 		.  		December 7, 2010.  	 
\bibitem[Hong et al. ()]{b27}\label{b27} 	 		‘WebQuilt: a proxy-based approach to remote Web usability testing’.  		 			J I Hong 		,  		 			J Heer 		,  		 			S Waterson 		,  		 			J A Landay 		.  	 	 		\textit{ACM Transactions on Information Systems}  		2001. 19  (3)  p. .  	 
\bibitem[Whiteside]{b21}\label{b21} 	 		 			Whiteside 		.  		\textit{CHI '90},  				 (New York, NY)  		ACM Portal. p. .  	 
\bibitem[Whiteside]{b37}\label{b37} 	 		 			Whiteside 		.  		\textit{CHI '90},  				 (New York, NY)  		ACM Portal. p. .  	 
\end{bibitemlist}
 			 		 	 
\end{document}
