<!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>Usability in software development process -Proposal of Society/Stakeholder Centered Design (SCD)-</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Shin'ichi fukuzumi</string-name>
          <email>Shin-ichi.fukuzumi@riken.jp</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Otaru University of Commerce Otaru</institution>
          ,
          <country country="JP">Japan</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>RIKEN Center for Advanced Intelligence Project Tokyo</institution>
          ,
          <country country="JP">Japan</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>-This paper is a proposal about Society/Stakeholder Centered Design (SCD) concept for usability of software. Traditionally, to achieve high usability, Human Centered Design (HCD) process is adopted in development process. However, this usability is mainly focuses to direct users who interacts the system, product and service directly. Recently, as workstyle using ICT (Information Communication Technology) has been changed, ICT users are not only direct users who interacts system and product directly but also indirect user who use output obtained by using ICT. This paper proposes a concept of outcome and consequence of use. This includes not only use of system, product or service but also use of their outputs. To the future, by preparing concrete examples, concept of SCD would like to be proposed. (Abstract)</p>
      </abstract>
      <kwd-group>
        <kwd>-Human centered design</kwd>
        <kwd>usability</kwd>
        <kwd>development process</kwd>
        <kwd>software engineer</kwd>
        <kwd>quality (key words)</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>INTRODUCTION</title>
      <p>
        In 2010, ISO9241-210 “Human-centred design for
interactive system” which is an ergonomic related standard
about human centered design was published [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. This standard
is put to practical use as an example which shape HCD
concept. Fig. 1 shows the relationship among each HCD
activity. As shown in this figure, HCD has six activities [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
      </p>
      <p>They are,
1) “Plan the human-centered design process” which is a
decision phase of a project to apply HCD to a target system,
2) “Understand and Specify the context of use” which is a
phase that a project get information how user uses a target
system,
3) “Specify the user needs and the user requirements” which
is a phase to extract users’ needs to a target system and to
specify the needs,
4) “Produce design Solution to meet user requirements” which
is a phase to make a prototype or production according to the
specification,
5) “Evaluate the design against requirements” which evaluates
whether the design meets the requirements,</p>
      <p>Nowky Hirasawa
6) “Design solution meet user requirements” which evaluates
whether the solution meets requirements”.</p>
      <p>In these, 2), 3), 4) and 5) are main activities in HCD
process.</p>
      <p>
        To achieve high usability, these are applied to each
development process shown in Fig. 2. Like this, HCD is a
method to provide system and product with high usability for
users and stakeholders [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ].
      </p>
      <p>
        About usability in software engineering, Quality in use
model is defined in ISO/IEC25010 [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. Figure. 3 shows the
Quality in use model. As this model is structured by referring
to usability standard related to ergonomics, mainly focuses to
human-system interaction interacting by direct user.
      </p>
      <p>Copyright © 2020 for this paper by its authors. Use permitted under Creative Commons License Attribution 4.0 International (CC BY 4.0).</p>
    </sec>
    <sec id="sec-2">
      <title>ISSUES OF CURRENT USABILITY</title>
      <p>
        Recently, as workstyle using ICT (Information
Communication Technology) has been changed, ICT users are
not only direct users who interacts system and product directly
but also indirect user who use output obtained by using ICT.
Concept of usability also has been changed. Fig. 4. Shows the
recent usability concept defined in ISO9241-11[
        <xref ref-type="bibr" rid="ref5">5</xref>
        ].
This figure explains that usability is outcome of use of
system, product or service in specified context of use.
However, this usability still only describes outcomes from
direct use.
      </p>
      <p>III.</p>
    </sec>
    <sec id="sec-3">
      <title>PROPOSAL FOR QUALITY IN USE</title>
      <p>
        Direct user means a user who interacts with product,
system or service directly. For example, ATM users in
banking system, customers for electric commerce system.
There are other direct users, called “secondary users”. They
also interact product, system or service directly, but their main
task is not use a product or system or receive service, but
operate and maintain of these system. Moreover, there are the
other kinds of users, they are indirect users of other
stakeholders. They usually use an output of products or
system. For example, in case of self-driving car (level four or
low), a driver is one of direct user and operators of traffic
infrastructure are kinds of secondary user. As for pedestrians,
they are indirect users. Figure 5 shows the proposal concept
of quality in use include other stakeholders.
This figure is still under proposal. To progress discussion, it
is necessary to have the viewpoint of not only product
and/or system but also data and service quality [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ],[
        <xref ref-type="bibr" rid="ref7">7</xref>
        ].
      </p>
    </sec>
    <sec id="sec-4">
      <title>FUTURE THEME</title>
      <p>In Figure 5, discussion of subcharacteristics of “Outcome
by use of output from product/system” and “Influence on
circumstances” are not enough.</p>
      <p>So, to the future, we will describe subcharacteristics of
consequence of use by using some example (e.g. self-driving
system, traffic control system and so on).</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <fpage>ISO9241</fpage>
          -
          <lpage>210</lpage>
          :
          <article-title>Ergonomics of human-system interaction -Part210: Human-centred design for interactive systems (</article-title>
          <year>2010</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <surname>Fukuzumi</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tanikawa</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Noda</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          :
          <article-title>How to apply humancentered design process (HCDP) to software development process</article-title>
          ?,
          <source>2017 IEEE/ACM 1st International Workshop on Design and Innovation in Software Engineering (DISE)</source>
          ,
          <source>Proceedings of 39th International Conference on Software Engineering</source>
          ,
          <fpage>pp13</fpage>
          -
          <lpage>16</lpage>
          ,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <surname>Tanikawa</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Suzuki</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kato</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fukuzumi</surname>
            ,
            <given-names>S. :</given-names>
          </string-name>
          <article-title>Problems in Usability Improvement Activity by Software Engineers - Consideration through verification experiments for human-centered design process support environment; HCI International 2014</article-title>
          Proceedings Vol.
          <volume>12</volume>
          LNCS8521, pp.
          <fpage>641</fpage>
          -
          <lpage>651</lpage>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4] 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="ref5">
        <mixed-citation>
          [5]
          <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="ref6">
        <mixed-citation>
          <article-title>[6] ISO/TS25011: "Software Engineering - Software product Quality Requirements and Evaluation (SQUARE) - IT service quality model quality</article-title>
          ,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7] ISO/IEC 25012:
          <article-title>"Software Engineering - Software product Quality Requirements and Evaluation (SQUARE) - Data quality model"</article-title>
          ,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>