<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>What Is the Difference between Usability in ISO 25000 and ISO/IEC 9241-11? - The Term “usability” as Part of the Product Quality Model Used in the SQuaRE Series in Contrast to the Term Usability in ISO 9241-11-</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Shin'ichi Fukuzumi</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Thomas Geis</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jonathan V Earthy</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Lloyd's Register Group Limited</institution>
          ,
          <addr-line>London</addr-line>
          ,
          <country country="UK">UK</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>ProContext</institution>
          ,
          <addr-line>Cologne</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>RIKEN</institution>
          ,
          <addr-line>15F, 1-4-1 Nihonbashi, Chuo-ku, Tokyo, 103-0027</addr-line>
          ,
          <country country="JP">Japan</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>The ISO/IEC 25000 SQuaRE series of standards (System and software Quality Requirements and Evaluation) deals with quality of systems and software. In ISO/IEC 25010:2011, “usability” is described as a product quality characteristic. On the other hand, “effectiveness”, “efficiency” and “satisfaction” exist as quality characteristics within the quality-in-use model. However, the usability definition used in ISO/IEC 25010 is “degree to which a product or system can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use”. As usability for quality characteristics in product quality does not include effectiveness, efficiency and satisfaction. So, there is a contradiction between usability definition and quality characteristics of usability in product quality. This paper describes the meaning of the two “usability” terms, and proposes “interaction capability” as the alternative term for “usability” in product quality to eliminate confusion for the readers of the standard.</p>
      </abstract>
      <kwd-group>
        <kwd>1 usability</kwd>
        <kwd>software engineer</kwd>
        <kwd>quality in use</kwd>
        <kwd>product quality</kwd>
        <kwd>interaction</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>The ISO/IEC 25000 SQuaRE (System and
software Quality Requirements and Evaluation)
series comprises international standards for
systems and software quality. There is a quality
model division that is one of five main divisions
and extension division. There are four quality
models. including“ data quality”, “service
quality”, “product quality” and “quality-in-use”.</p>
      <p>Figure 1 shows the structure of SQuaRE series.</p>
      <p>
        In this series, two of four quality models, that
is, product quality model and quality in use model
are described in ISO/IEC 25010:2011. Figure 2
shows the product quality model and figure 3
shows the quality in use model as describes in
ISO/IEC 25010: 2011 [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]
Figure 2 Product quality model including usability as a quality characteristic and its sub-characteristics [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]
      </p>
      <p>In figure 2, we find the term “usability” as one of
the characteristics of product quality. On the other hand,
we find the terms “effectiveness”, “efficiency” and
“satisfaction” as quality characteristics of the quality in
use model in figure 3. In ISO 9241-11, usability is
defined in terms of effectiveness, efficiency and
satisfaction. So, the same term “usability” is used in
both standards, but the meanings are different.</p>
      <p>This paper describes the difference between the
definitions and proposes an alternative term to
“usability” in product quality.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Meaning of “usability” as defined in ISO 9241-11</title>
      <p>
        effectiveness, efficiency and satisfaction in a specified
context of use”. Figure 4 explains that the outcome of
“use” in context of use is usability in terms of
effectiveness, efficiency and satisfaction. In figure 4,
“use” is emphasized.
There are other popular usability definitions. For
example, Nielsen[
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] defined usability in terms of
five characteristics, including “easy to learn, i.e.,
learnability”, “efficient to use, i.e., efficiency”,
“easy to remember, i.e., memorability”, “few
error” and “subjectively pleasing satisfaction”.
Jordan[
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] defined usability in terms of
“guessability (of interaction), “learnability” (of
interaction), and so on. These definitions are both
related to user system interaction. They are
focused on interface design for interaction, e.g.,
“learnable interaction process”, “guessable
button for intended operation” or “font size for
minimizing reading errors”. As these definitions
focus on “ease of interaction”, , there is a
difference between these definitions and the ISO
definition used in ISO/IEC 25010 and ISO
924111.
      </p>
    </sec>
    <sec id="sec-3">
      <title>3. Proposal for an alternative term</title>
      <p>to not confuse readers of</p>
    </sec>
    <sec id="sec-4">
      <title>Standards of the SQuaRE series</title>
      <p>As described in section 2, the
subcharacteristics of “usability” in the product
quality model as shown in figure 2 focus on “ease
of interaction”, not effectiveness, efficiency and
satisfaction in context of use. The authors wish to
note that from an international standards
perspective, inconsistency in terminology will
result in significant problems:
A) It weakens standards if they state different
things about the same term especially when
each of them is widely used. Double
definition of terms between established
disciplines is a problem. In this case it
cannot be represented characteristics of
product quality. Replacing "usability" with
"interaction capability" would solve this
thirty-year-old problem.</p>
      <p>B) Both ISO/IEC 25010 and ISO 9241-11 are
widely used and conceptual inconsistencies
between them weakens confidence of the
readers. Though “usability” is only used in
ISO/IEC 25010 as a term, the concept of
usability is defined in ISO 9241-11.</p>
      <p>C) Two standards use usability as ISO 9241-11
defines it. They will both have trouble
relating to ISO/IEC 25010, especially now
that the product quality model and
qualityin-use are in different document (25010 and
25019).</p>
      <p>Some of the quality sub-characteristics of
usability as quality characteristics of product
quality are taken from ISO9241-110
(“Interaction principles”). From this, these
quality sub- characteristics are deeply related to
“interaction”. So, we propose the term
“interaction capability” as a replacement term for
“usability” for quality characteristics in the
product quality model.</p>
    </sec>
    <sec id="sec-5">
      <title>4. Conclusion</title>
      <p>This paper describes the meaning of two
“usability” terms in ISO/IEC 25010 and ISO
9241-11. “Interaction capability” is proposed as
the alternative term to “usability” for the product
quality model. Irrespective of whether this
proposal will be accepted for new versions of
ISO/IEC 25010, we have to clarify the
misunderstanding between the capability of
product attributes to serve as prerequisites for
usability (“interaction capability”) as defined in
the software engineering area and usability itself
as defined in the ergonomics area</p>
    </sec>
    <sec id="sec-6">
      <title>5. References</title>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <surname>Komiyama</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fukuzumi</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Azuma</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Washizaki</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          <article-title>and</article-title>
          <string-name>
            <surname>Tsuda</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Usability of Software-Intensive Systems from Developers' Point of View -Current Status and Future Perspectives of International Standardization of Usability Evaluation-</article-title>
          ,
          <string-name>
            <surname>M. Kurosu</surname>
          </string-name>
          (Ed.):
          <source>HCII</source>
          <year>2020</year>
          , LNCS 12181, pp.
          <fpage>450</fpage>
          -
          <lpage>463</lpage>
          ,
          <year>2020</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2] ISO/IEC 25010:
          <article-title>Systems and software engineering -Systems and software Quality Requirements and Evaluation (SQuaRE) - System and software quality, 2011</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <fpage>ISO9241</fpage>
          -
          <lpage>11</lpage>
          :
          <article-title>Ergonomics of human-system interaction -Part11: Usability for definition and concept (</article-title>
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <surname>Fukuzumi</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          : Context Coverage in “Quality in Use Model”, IWESQ2021, https://ceurws.org/Vol-
          <volume>3114</volume>
          /paper-06.pdf,
          <year>2021</year>
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <surname>Nielsen</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          : Usability Engineering, Academic Press,
          <year>1993</year>
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <surname>Jordan</surname>
            ,
            <given-names>P. W.</given-names>
          </string-name>
          : “What is Usability”, in Robertson, S. (ed.) Contemporary Ergonomics, pp.
          <fpage>454</fpage>
          -
          <lpage>458</lpage>
          , Taylor &amp; Francis,
          <year>1994</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <surname>ISO</surname>
          </string-name>
          9241-110:
          <article-title>Ergonomics of humansystem interaction -Part110: Interaction principles (</article-title>
          <year>2020</year>
          ).
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>