<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: RafaelGarrett</title>
    <description>The latest articles on Forem by RafaelGarrett (@rafaelgarrett).</description>
    <link>https://forem.com/rafaelgarrett</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F618774%2F45871e81-8bca-449f-9b6e-4e8be2d81b72.jpeg</url>
      <title>Forem: RafaelGarrett</title>
      <link>https://forem.com/rafaelgarrett</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/rafaelgarrett"/>
    <language>en</language>
    <item>
      <title>Avaliação Heurística</title>
      <dc:creator>RafaelGarrett</dc:creator>
      <pubDate>Thu, 22 Apr 2021 01:09:33 +0000</pubDate>
      <link>https://forem.com/rafaelgarrett/avaliacao-heuristica-2n4</link>
      <guid>https://forem.com/rafaelgarrett/avaliacao-heuristica-2n4</guid>
      <description>&lt;p&gt;As heurísticas originais (1990) surgiram da análise de 249 problemas, identificados a partir de avaliações realizadas por especialistas em 11 projetos distintos. Proposta por Nielsen análise Heurística é um método de engenharia de usabilidade para encontrar os erros de usabilidade em uma interface para que sejam corrigidos em um processo de desenvolvimento iterativo. Usa um grupo de avaliadores e tem como resultados compilados. Avaliadores devem ter conhecimento da aplicação, usuários e suas reações. &lt;/p&gt;

&lt;p&gt;Número de Avaliadores:&lt;/p&gt;

&lt;p&gt;N(i) = N (1-(1-p)i) &lt;/p&gt;

&lt;p&gt;Aonde i= número de avaliadores, N = nº de problemas e p = probabilidade de encontrar um problema com 1 único participante. Um único avaliador até 35% dos problemas. 5 avaliadores encontram 75% dos problemas. &lt;/p&gt;

&lt;p&gt;Examinar a interface separadamente percorrendo para ter noção do fluxo de navegação e focar em elementos específicos.&lt;/p&gt;

&lt;p&gt;Compilação, reunir os avaliadores e discutir os problemas e soluções. Importante lembrar que nenhum problema deve ser descartado. &lt;/p&gt;

&lt;p&gt;Severidade de cada problema: frequência (nº de vezes), impacto (impedimento de continuar) e persistência, tempo do usuário. Para cada tópico mencionado a cima usasse os níveis: 0 não concordo, 1 cosmético (não precisa ser corrigido), 2 baixa prioridade, 3 importante corrigir e 4 corrigir urgente.&lt;/p&gt;

&lt;p&gt;As heurísticas:&lt;/p&gt;

&lt;p&gt;1.Diálogo simples e natural;&lt;br&gt;
&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--uPwCOs6f--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/6nrm0ostyazqvitllblz.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--uPwCOs6f--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/6nrm0ostyazqvitllblz.png" alt="Diálogo simples e natural"&gt;&lt;/a&gt;&lt;br&gt;
2.Usar a linguagem do usuário;&lt;br&gt;
&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s---ZXu6bJK--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/izgkzho7s5w17mt1jue2.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s---ZXu6bJK--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/izgkzho7s5w17mt1jue2.png" alt="Usar a linguagem do usuário"&gt;&lt;/a&gt;&lt;br&gt;
3.Minimizar carga de memória;&lt;br&gt;
&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--EO5Ksvco--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/4q5hrt99hucuixxn9kes.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--EO5Ksvco--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/4q5hrt99hucuixxn9kes.png" alt="Minimizar carga de memória"&gt;&lt;/a&gt;&lt;br&gt;
4.Ser consistente;&lt;br&gt;
&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--GRvf7yeO--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/qzt8j9ulr20eznurbla6.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--GRvf7yeO--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/qzt8j9ulr20eznurbla6.png" alt="Ser consistente"&gt;&lt;/a&gt;&lt;br&gt;
5.Fornecer realimentação;&lt;br&gt;
&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--fWB-uZQ1--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/m72sh4jk66cpp9aiq3c8.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--fWB-uZQ1--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/m72sh4jk66cpp9aiq3c8.png" alt="Fornecer realimentação"&gt;&lt;/a&gt;&lt;br&gt;
6.Apresentar saídas claras;&lt;br&gt;
&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--FXxlzRLF--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/2myy3ez9civ31whzo36j.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--FXxlzRLF--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/2myy3ez9civ31whzo36j.png" alt="Apresentar saídas claras"&gt;&lt;/a&gt;&lt;br&gt;
7.Fornecer atalhos e padrões;&lt;br&gt;
&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--gS1iThLG--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/97v00axuxhx0l43209zn.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--gS1iThLG--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/97v00axuxhx0l43209zn.png" alt="Fornecer atalhos e padrões"&gt;&lt;/a&gt;&lt;br&gt;
8.Mensagens de erros claras e construtivas;&lt;br&gt;
&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--7n_gyH2j--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/4vtuppurrj6vrua31erd.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--7n_gyH2j--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/4vtuppurrj6vrua31erd.png" alt="Mensagens de erros claras e construtivas"&gt;&lt;/a&gt;&lt;br&gt;
9.Evitar erros;&lt;br&gt;
&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--TUK5TmRx--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/77rm0oan5w4tram1ias4.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--TUK5TmRx--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/77rm0oan5w4tram1ias4.png" alt="Evitar erros"&gt;&lt;/a&gt;&lt;br&gt;
10.Fornecer ajuda e documentação.&lt;/p&gt;

&lt;p&gt;Referências:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Como os artigos científicos são escritos &lt;a href="https://www.youtube.com/watch?v=Pkb-ScoKwko"&gt;https://www.youtube.com/watch?v=Pkb-ScoKwko&lt;/a&gt;;&lt;/li&gt;
&lt;li&gt;Design Interativo em processos ágeis de 
desenvolvimento de software &lt;a href="https://www.cin.ufpe.br/%7Etg/2004-2/cpbb.pdf"&gt;https://www.cin.ufpe.br/~tg/2004-2/cpbb.pdf&lt;/a&gt;;&lt;/li&gt;
&lt;li&gt;Processo de teste ágil x tradicional &lt;a href="https://www.devmedia.com.br/processo-de-teste-agil-x-tradicional/36854"&gt;https://www.devmedia.com.br/processo-de-teste-agil-x-tradicional/36854&lt;/a&gt; .&lt;/li&gt;
&lt;/ol&gt;

</description>
      <category>heuristica</category>
      <category>nielse</category>
      <category>avaliadores</category>
      <category>niveis</category>
    </item>
  </channel>
</rss>
