<!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>
      <article-id pub-id-type="doi">10.4018/978-1-7998</article-id>
      <title-group>
        <article-title>Benefits of Usability and User Experience in Automated Driving</article-title>
      </title-group>
      <contrib-group>
        <aff id="aff0">
          <label>0</label>
          <institution>Mikko Rajanen INTERACT Research Unit University of Oulu Oulu</institution>
          ,
          <country country="FI">Finland</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>[10] M. Rajanen, “Applying Usability Cost-Benefit Analysis - Explorations in Commercial and Open Source Software Development Contexts,” PhD Dissertation. Acta Universitatis Ouluensis Series A 587. University of Oulu</institution>
          ,
          <addr-line>2011</addr-line>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2020</year>
      </pub-date>
      <abstract>
        <p>-This paper proposes a list of potential benefits of better usability and user experience adapted to automated driving and autonomous mobility. These benefits could be useful for understanding and communicating the importance of usability and user experience for the success of automated driving to be accepted by the non-technical public and becoming mainstream and successful. In this paper, the focus is on identifying usability and user experience benefits of humanmachine interaction (HMI) in automated driving context. The goal of the paper is to legitimize the usability and the user experience activities in the eyes of the management of automated driving application and HMI development organizations. The user-centered design process focuses on users, their needs and requirements. This paper shows that the benefits of better usability and user experience through usercentered design can be identified in use context as well as application development context through competitive advantage, reduced risks, and reduced development costs.</p>
      </abstract>
      <kwd-group>
        <kwd>Usability</kwd>
        <kwd>user experience</kwd>
        <kwd>benefits</kwd>
        <kwd>automated driving HMI</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>I. INTRODUCTION</title>
      <p>
        Usability is defined as one of the main quality attributes
for applications, software products, information systems and
online services in many international quality standards,
which have been developed to offer different focus on
usability processes and stakeholders [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Good usability can
be achieved through adopting user-centered design process,
performing usability activities (e.g., usability testing, expert
evaluation, prototyping), and by having an overall focus on
usability issues through the entire development process [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
The importance of good usability has been highlighted also
in the context of driver-car interaction, where easy to learn,
fast to operate and error-free human-machine interaction
(HMI) has been identified as an important requirement for
safety, satisfaction and acceptance of new technologies in
automotive context (see e.g. [3], [4], [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]).
      </p>
      <p>
        Research on human-machine interaction showed that the
evaluation of the user satisfaction with a certain product,
system, or service had to be expanded with more subjective
aspect of personal emotions and experiences. Since the turn
of the millennia, the concept of user experience (UX) has
been introduced to take into account the emotions and
attitudes of user about using a particular product, system or
service [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. While usability is crucial in order the users to
take advantage of the product’s functionality, good UX is
needed in addition of good usability to guarantee a product’s
success with customers and in the market [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ].
      </p>
      <p>
        Usability and UX have been recognized as important
aspects of autonomous mobility acceptability before the first
use as well as the acceptance after the first use (see [3], [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]).
Therefore, it is important that the usability and UX activities
are brought also into the automated driving HMI design and
development life cycle. However, bringing usability and UX
activities into the software development life cycle in general
have been a challenge since the beginning of the usability
activities over fifty years ago as often the focus is on
developing technological solutions rather than on the people
that will actually use these technologies [10]. Furthermore,
there is still a lot of diversity on the usability and UX
professionals’ practices, as well as how they conceptualize
usability and user experience and motivate it for their
management [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], [11]. Nevertheless, there has been a lot of
progress making usability improvement activities a
recognized and integral part of the development process.
      </p>
      <p>Nowadays many of the development companies
acknowledge the strategic importance of usability and UX,
and see them as potential competitive factors for their
success [11]. However, even in these cases, the usability and
UX activities are often amongst the first to be sacrificed
whenever there is a rush to deliver the product to the market.
Furthermore, the development company management may
still see the usability and UX improvement activities as just
“nice to have” optional task in projects. In the eyes of these
managers, such an ‘extra’ task is always a potential risk for
project deadlines and therefore is often among the first to be
cut from the project planning. Often these managers try to
justify not investing to better usability through user-centered
design with the argument that the users can be trained and
that sooner or later, these users will learn to overcome the
usability problems in the system and adapt their work flow to
the intricacies of the software, system or service. However, it
is also possible that the users simply refuse to learn to use the
system with poor usability, or to accept and adopt a new
technology, and that the technology that has been developed
and the functionality that has been implemented in the
system with so much cost and effort is never used [11].</p>
      <p>
        Even today there are quite few product development
organizations reportedly having incorporated usability
activities fully in their product development process [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. One
reason for these difficulties is that the benefits of better
usability are not easily identified or assessed [10]. Usability
activities have been competing for resources against other
stakeholders in the software development projects that do
have objective and convincing cost-benefit data available for
management decision making when the resources are
allocated. Justifying the costs and identifying the benefits of
the usability and UX improvement activities have been seen
as key goals for successfully integrating usability activities
into development projects in ICT development [11].
Furthermore, explicit introduction and justification of user
centered design and usability work by managers is important
in the development context, because developers cling to
status quo and seek to preserve it, by claiming that they
follow the principles of user centred design and evaluation
while in practice they do not, even if they genuinely desire to
develop for high usability [12].
      </p>
      <p>Usability and UX work will be integrated in the
development context when a strategic decision is made by
the decision makers to incorporate it into the business and
development processes of the organization [13]. Usability
has many different forms of potential benefits also for the
development organization. These benefits include increased
productivity due to less user errors and less time spent on
work tasks. In addition to the traditional software
development context, the emergence of online commerce has
shifted the emphasis from the advantages of better usability
to the penalties of the online commerce site not having good
usability. Usability cost-benefit analysis has been identified
as a potential method for arguing for strategic usability (see
e.g. [14], [15], [10], [11]).</p>
    </sec>
    <sec id="sec-2">
      <title>II. USABILITY COST-BENEFIT ANALYSIS</title>
      <p>
        Cost-benefit analysis is a method for assessing the
projects from the investment point of view [
        <xref ref-type="bibr" rid="ref10">16</xref>
        ]. This method
involves making an investment decision by comparing the
estimated costs and benefits of the planned actions. This
comparison is based on collected and analyzed data
regarding technological and financial aspects of the project.
As a result, the management concentrates the available
resources in the most useful way on such planned activities
that have low costs and potentially high benefits, as well as
finding new strategic openings for their business [10]. The
usability cost-benefit analysis is in practice conducted in the
planning phase of a development project [
        <xref ref-type="bibr" rid="ref11">17</xref>
        ].
      </p>
      <p>
        While there are many different cost-benefit analysis
models for different contexts, there are still relatively few
published models for analysing the costs and benefits of
usability work in general, and they focus on the company
software development context [11]. While cost-benefit
analysis has been used in the automated driving context, the
focus has been on analyzing the autonomous mobility
services and not on the human-machine interaction, usability
or UX (see e.g. [
        <xref ref-type="bibr" rid="ref12">18</xref>
        ]).
      </p>
      <p>
        Generally, the five traditional models of usability
costbenefit analysis differ by the focus and perspective they
adopt. Mayhew et al. [
        <xref ref-type="bibr" rid="ref13">19</xref>
        ] focuses on the benefits that are of
most interest to the audience of the analysis. Ehrlich et al.
[
        <xref ref-type="bibr" rid="ref14">20</xref>
        ] focuses on the benefits of usability from the viewpoint
of the vendor company, corporate customer, and end user.
Karat [
        <xref ref-type="bibr" rid="ref10">16</xref>
        ] analyses the usability benefits through
costbenefit calculation of human factors work. Donahue [
        <xref ref-type="bibr" rid="ref15">21</xref>
        ]
divides the focus between the costs for the development
organization and the benefits for the customer organization.
Bevan [
        <xref ref-type="bibr" rid="ref16">22</xref>
        ] analyses the benefits of usability to the
development organization during different phases:
development, sales, use, and support.
      </p>
      <p>
        There are also other approaches, such as cost-justification
of usability and UX activities through fear-setting, where the
focus is on potential losses of inaction if the technology is
not adopted or market is lost due to inferior usability and UX
of the product, system or service (see e.g. [
        <xref ref-type="bibr" rid="ref17">23</xref>
        ]).
      </p>
      <p>
        There is still a need for research studies where usability
cost-benefit analysis perspective has been employed in and
adapted to specific contexts such as automated driving HMI,
or where the results of using usability cost-benefit analysis in
a case study would have been contrasted with the literature
on usability cost-justification or usability cost-benefit
analysis to validate especially the benefits identified in the
literature [11]. Furthermore, special care should be taken
when using usability cost-benefit analysis as motivational
factor for usability activities, as management can focus on
the costs of usability instead of its benefits and get
discouraged, even though the costs such as interface
development would be realized in any case [
        <xref ref-type="bibr" rid="ref18">24</xref>
        ]. Therefore, it
is better to focus on usability and UX benefits instead of the
complete cost-benefit analysis of usability and UX activities
[11].
      </p>
      <p>III. BENEFITS OF USABILITY AND UX IN AUTOMATED DRIVING</p>
      <p>
        This paper proposes the following preliminary usability
benefits for automated driving applications in organizational
context and use context. This paper addresses autonomous
driving applications and HMIs on all SAE driving
automation classification levels from basic warnings and
cruise control to no direct human intervention needed during
driving and covers different use cases such as privately
owned vehicles, communally shared vehicles, mobility on
demand, public transportation, and autonomous delivery
vehicle. These preliminary benefits can then be further
refined, validated through empirical and experimental
testing, and further refined for example to the context of
completely autonomous mobility solutions. These proposed
usability benefits are based on the existing general usability
cost-benefit literature (see e.g. [14], [15], [10], [11]), as well
as on a continuous longitudinal literature review on the
usability and UX benefits that the author has studied for over
20 years from different perspectives and in different contexts
(see e.g. [10], [11], [15], [
        <xref ref-type="bibr" rid="ref18">24</xref>
        ], [
        <xref ref-type="bibr" rid="ref19">25</xref>
        ]). Furthermore, the
proposed benefits are also based on the literature of adapting
usability and UX benefits into different contexts, such as
open source software development [
        <xref ref-type="bibr" rid="ref18">24</xref>
        ], games and
gamification [
        <xref ref-type="bibr" rid="ref19">25</xref>
        ], and on the literature on HMI in driving,
automated driving and autonomous mobility contexts.
      </p>
      <sec id="sec-2-1">
        <title>A. Usability benefits in automated driving context</title>
      </sec>
      <sec id="sec-2-2">
        <title>1) Organizational context (development and sales)</title>
        <sec id="sec-2-2-1">
          <title>Increased sales</title>
          <p>As a result of usability and UX methods and processes,
the business objectives of the automated driving and its HMI
are well defined, understood, and embedded in the design,
especially through user-centered design. The better usability
will result in increased user acceptability and acceptance of
novel technology and therefore increased level of adoption of
new technology. This may result increased sales and strategic
competitive advantage when compared to competitors with
worse HMI usability (see e.g. [11]).</p>
        </sec>
        <sec id="sec-2-2-2">
          <title>Reduced development costs</title>
          <p>
            The user-centered design makes the whole design and
development process of automated driving HMI iterative and
incremental, therefore making sure that the critical issues,
concerns and functionalities are well designed and tested
with real users before implementation, thus resulting in less
need for later costly changes. Furthermore, this speeds up the
development of the new technology and time to enter the
market (see e.g. [
            <xref ref-type="bibr" rid="ref14">20</xref>
            ], [4], [3]).
          </p>
        </sec>
        <sec id="sec-2-2-3">
          <title>Reduced training and support costs</title>
          <p>
            The automated driving HMI is tailored and adapted to the
drivers and not vice versa, by understanding, knowing and
modelling the expectations and behaviors of drivers. Better
usability makes the automated driving application easier to
learn, therefore reducing the need for providing training and
support (see [
            <xref ref-type="bibr" rid="ref16">22</xref>
            ]). Easier learning can also be used as
competitive factor [11].
          </p>
        </sec>
        <sec id="sec-2-2-4">
          <title>Easier and faster acceptance and adoption of automated driving</title>
          <p>
            Automated driving is a complete paradigm shift for car
users, and all kinds of problems, issues, mistakes and
problems with the new technology and its HMI will hinder
the acceptance and adoption of automated driving [
            <xref ref-type="bibr" rid="ref20">26</xref>
            ].
Better usability will make it easier and faster for the former
active car drivers to accept the automated driving and to
adopt it, by allowing the users to see the benefits of the new
technology instead of concentrating on everyday problems
and issues emerging from it [
            <xref ref-type="bibr" rid="ref20">26</xref>
            ]. Therefore, good, intuitive
and error-free HMI allows previously active car drivers to be
confidently adopt more and more passive role in automated
driving and still feel that they are in control. Furthermore, it
can be argued that the acceptance and adoption of different
levels of automated driving is a crucial step for further
development and acceptability of autonomous mobility
solutions.
          </p>
        </sec>
        <sec id="sec-2-2-5">
          <title>Reduced risk of legal liability</title>
          <p>
            User errors and mistakes when using automated driving
HMI may potentially cause accidents, which would carry a
risk of legal liabilities for the developer of the HMI. The
ethical and legal responsibilities emerging from the HMI
design have been highlighted in the literature (see e.g. [
            <xref ref-type="bibr" rid="ref21">27</xref>
            ]).
Better usability reduces the risk of user errors and
unintentional mistakes made by users, and therefore reduces
the liability risks of the developer. Furthermore, this could
further reduce the costs associated with injuries and
damages, as well as legal services and insurances (see e.g.
[
            <xref ref-type="bibr" rid="ref12">18</xref>
            ]).
          </p>
        </sec>
        <sec id="sec-2-2-6">
          <title>Conforming to regulations and ethical principles</title>
          <p>
            Automated driving has huge impacts on national and
international legislations, regulations, and ethical principles.
Better usability of automated driving HMIs through
usercentered design will ensure that important regulative and
ethical aspects such as accessibility, inclusive design, and
user empowerment are explicitly taken into account in the
design of automated driving HMI, as the users and other
important stakeholders can actively participate in the design
process from the beginning. By proactively conforming to
the regulations, as well as to the ethical and inclusive
principles, the automated driving HMI manufacturers could
show that automated driving HMIs do not have to be heavily
regulated by the legislators (see e.g. [
            <xref ref-type="bibr" rid="ref22">28</xref>
            ]).
          </p>
        </sec>
      </sec>
      <sec id="sec-2-3">
        <title>2) Use context</title>
        <sec id="sec-2-3-1">
          <title>Reduced errors</title>
          <p>
            Automated driving application is designed according to
usability requirements for ease of use, effectiveness, and
efficiency, as well as UX requirements of subjective
experience with respect to the target user groups and the
business objectives. User errors and mistakes especially
during the everyday use will decrease user satisfaction and
the level of trust to the new technology, therefore generally
decreasing the willingness to accept and adopt the automated
driving (see e.g. [
            <xref ref-type="bibr" rid="ref23">29</xref>
            ]). Furthermore, errors in automated
driving HMI may have dangerous unintended consequences
and endanger both lives and property.
          </p>
        </sec>
        <sec id="sec-2-3-2">
          <title>Reduced learning effort</title>
          <p>
            The automated driving application is designed for easy of
learning, therefore requiring less learning effort and reducing
the potential barrier of acceptance and adoption. Ease of
learning further increases user satisfaction and willingness to
adopt new technology (see e.g. [
            <xref ref-type="bibr" rid="ref24">30</xref>
            ]).
          </p>
        </sec>
        <sec id="sec-2-3-3">
          <title>Increased user satisfaction</title>
          <p>The potential end-users are accepting and adopting the
automated driving application, accepting and adopting the
automated driving as a concept, and provide positive
feedback about them through different means and channels.
Positive user satisfaction will have an impact on general
acceptability of the new technology, as well as to the sales.</p>
        </sec>
        <sec id="sec-2-3-4">
          <title>Increased safety</title>
          <p>
            Automated driving and autonomous mobility can
potentially increase the safety of the driving in addition to
increasing efficiency in driving time and costs. (see e.g. [
            <xref ref-type="bibr" rid="ref7">7</xref>
            ]).
Therefore, better usability of automated driving HMI may
help to prevent accidents and other dangers to both life and
property. Furthermore, increased safety may make automated
driving and autonomous mobility more appealing to
consumers as well as to businesses.
          </p>
        </sec>
      </sec>
      <sec id="sec-2-4">
        <title>B. UX benefits in automated driving context</title>
      </sec>
      <sec id="sec-2-5">
        <title>1) Organizational context (development and sales)</title>
        <sec id="sec-2-5-1">
          <title>Increased brand appeal</title>
          <p>
            In addition to fast, efficient and error-free HMI achieved
through usability methods, the HMI can be further improved
from UX perspective by making it more visually appealing
and integrating it as part of the organizational brand. The
customers are more willing to spend money on expensive
products, systems, or services if they consider the brand
more appealing. (see e.g. [
            <xref ref-type="bibr" rid="ref25">31</xref>
            ]). One example of this
approach is Apple, which has been focusing in their strategy
on UX and visual design as important parts of their brand
appeal [
            <xref ref-type="bibr" rid="ref25">31</xref>
            ]. Increased brand appeal through better HMI from
UX perspective would help automated driving HMI
manufacturer to gain further competitive advantage over
competitors with less visually appealing and
brandconnected HMI.
          </p>
        </sec>
      </sec>
      <sec id="sec-2-6">
        <title>2) Use context</title>
        <sec id="sec-2-6-1">
          <title>Increased perceived value</title>
          <p>
            While good usability in automated driving HMI is the
prerequisite for its acceptability and acceptance from the user
perspective, an automated driving HMI and its related brand
can further be made more attractive for the customers
through better UX design. Users attach perceived value on
good UX design. Therefore, good design from UX
perspective makes the user feel like they have good value for
their money, which further increases user satisfaction and the
value of the brand in the eyes of the customers (see e.g. [
            <xref ref-type="bibr" rid="ref25">31</xref>
            ],
[
            <xref ref-type="bibr" rid="ref7">7</xref>
            ]).
          </p>
        </sec>
        <sec id="sec-2-6-2">
          <title>Increased automated driving appeal</title>
          <p>
            The pace of automated driving adoption beyond early
adopters depends on automated driving having not only
positive image among potential users, but also having an
appeal. Potentially automated driving can increase the levels
of user comfort, safety and traffic efficiency (see e.g. [
            <xref ref-type="bibr" rid="ref26">32</xref>
            ],
[
            <xref ref-type="bibr" rid="ref27">33</xref>
            ]). Automated driving HMIs with good UX would make
automated driving more desirable than conventional forms of
driving and move the automated driving adoption from
innovators and early adopters to more mainstream (see e.g.
[
            <xref ref-type="bibr" rid="ref6">6</xref>
            ], [
            <xref ref-type="bibr" rid="ref7">7</xref>
            ]).
          </p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>IV. CONCLUSIONS</title>
      <p>This paper is the first step on filling one of the gaps in the
literature of usability in automated driving context by
highlighting the strategic role of usability and user-centered
design in the development of automated driving HMIs. This
paper contributes to the literature by proposing a list of
dedicated usability benefits for automated driving context.
Furthermore, this paper contributes to the theory by
exploring, contrasting and adapting the usability benefits
identified in productivity software development context to
create usability benefits perspectives fitting the automated
driving HMI context. The preliminary results from this paper
indicate that it is possible to fit the usability benefits into the
automated driving context and to identify the benefits from
better usability and UX through user-centered design in
automated driving application in both development context
and in use context.</p>
      <p>The results of this paper can be utilized by the
practitioners (e.g., managers, usability specialists, and HMI
developers) in the automated driving context to motivate and
justify the usability and UX activities, and the resources
needed for them. Furthermore, researchers interested in
usability and UX benefits can use the identified usability and
UX benefits as systematic criteria to further develop better
usability and UX cost-benefit analysis models in general as
well as developing further specific usability cost-benefit
models tailored to the contexts of automated driving and
autonomous mobility HMIs.</p>
      <p>With regard to future areas of research, one future area of
study is to evaluate and validate empirically the proposed
usability and UX benefits in automated driving HMI context.
This kind of empirical study could be done in development
companies or educational settings. This evaluation could be
carried out as an exploratory case study in a car
manufacturing company, automated driving research
organization, automated driving HMI development company,
or as a survey among these companies, as well as among
end-users, decision-makers and other stakeholders.
Furthermore, another future area of research is to expand the
proposed usability and UX benefits to explicitly take into
account different aspects of usability and UX such as
effectiveness, efficiency, satisfaction, safety, safety,
processes, methods, as well as to integrate these benefits into
service design perspective as well as autonomous mobility
service perspective.
[12] A. Wale-Kolade and P. A. Nielsen, “Apathy towards the integration
of usability work: a case of system justification,” Interacting with
Computers, 28(4), 2016, pp. 437-450.
[13] G. Venturi, J. Troost and T. Jokela, “People, organizations, and
processes: An inquiry into the adoption of user-centred design in
industry,” International Journal of Human-Computer Interaction,
21(2), 2006, pp. 219-238.
[14] R. G. Bias, and D. J. Mayhew, (Eds.) “Cost-justifying usability: An
update for the Internet age,” Elsevier, 2005.
[15] M. Rajanen, “Usability Cost-Benefit Models - Different Approaches
to Usability Benefit Analysis,” In proceedings of 26th Information
Systems Research Seminar in Scandinavia (IRIS26), Haikko, Finland,
2003.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>D.</given-names>
            <surname>Marghescu</surname>
          </string-name>
          ,
          <string-name>
            <surname>D.</surname>
          </string-name>
          “
          <article-title>Usability evaluation of information systems: A review of five international standards,”</article-title>
          <source>In Information Systems Development</source>
          , Springer, Boston, MA,
          <year>2009</year>
          , pp.
          <fpage>131</fpage>
          -
          <lpage>142</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>D.</given-names>
            <surname>Rajanen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Clemmensen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Iivari</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Inal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Rızvanoğlu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Sivaji</surname>
          </string-name>
          and
          <string-name>
            <given-names>A.</given-names>
            <surname>Roche</surname>
          </string-name>
          ,
          <article-title>UX professionals' definitions of usability and UX-A comparison between Turkey, Finland</article-title>
          , Denmark, France and Malaysia.
          <source>In IFIP Conference on Human-Computer Interaction</source>
          , Springer, Cham,
          <year>2017</year>
          , pp.
          <fpage>218</fpage>
          -
          <lpage>239</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          <string-name>
            <given-names>M.</given-names>
            <surname>Körber</surname>
          </string-name>
          , and
          <string-name>
            <given-names>K.</given-names>
            <surname>Bengler</surname>
          </string-name>
          ,
          <article-title>Measurement of momentary user experience in an automotive context</article-title>
          .
          <source>In Proceedings of the 5th International Conference on Automotive User Interfaces and Interactive Vehicular Applications</source>
          ,
          <year>2013</year>
          , pp.
          <fpage>194</fpage>
          -
          <lpage>201</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          <string-name>
            <surname>M. J. Pitts</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          <string-name>
            <surname>Skrypchuk</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Attridge</surname>
            and
            <given-names>M. A.</given-names>
          </string-name>
          <string-name>
            <surname>Williams</surname>
          </string-name>
          , “
          <article-title>Comparing the user experience of touchscreen technologies in an automotive application,”</article-title>
          <source>In Proceedings of the 6th International Conference on Automotive User Interfaces and Interactive Vehicular Applications</source>
          ,
          <year>2014</year>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>8</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>J.</given-names>
            <surname>Orlovska</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Wickman</surname>
          </string-name>
          , and
          <string-name>
            <given-names>R.</given-names>
            <surname>Söderberg</surname>
          </string-name>
          , “
          <article-title>Big data analysis as a new approach for usability attributes evaluation of user interfaces: an automotive industry context,”</article-title>
          <source>In DS 92: Proceedings of the DESIGN 2018 15th International Design Conference</source>
          ,
          <year>2018</year>
          , pp.
          <fpage>1651</fpage>
          -
          <lpage>1662</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>H.</given-names>
            <surname>Cornet</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Stadler</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Kong</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Marinkovic</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Frenkler and P. M. Sathikh</surname>
          </string-name>
          , “
          <article-title>User-centred design of autonomous mobility for public transportation in Singapore</article-title>
          ,” Transportation Research Procedia,
          <volume>41</volume>
          ,
          <year>2019</year>
          , pp.
          <fpage>191</fpage>
          -
          <lpage>203</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>O.</given-names>
            <surname>Hagman</surname>
          </string-name>
          and
          <string-name>
            <given-names>J.</given-names>
            <surname>Lindh</surname>
          </string-name>
          , “
          <article-title>How autonomous cars can affect the car industry - Implications for user experience and competition</article-title>
          ,”
          <source>Master's thesis</source>
          ,
          <year>2019</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>K.</given-names>
            <surname>Battarbee</surname>
          </string-name>
          and
          <string-name>
            <surname>I. Koskinen</surname>
          </string-name>
          , “
          <article-title>Co-experience: user experience as interaction</article-title>
          ,” CoDesign,
          <volume>1</volume>
          (
          <issue>1</issue>
          ),
          <year>2005</year>
          , pp.
          <fpage>5</fpage>
          -
          <lpage>18</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>V.</given-names>
            <surname>Distler</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Lallemand</surname>
          </string-name>
          , and T. Bellet, “
          <article-title>Acceptability and acceptance of autonomous mobility on demand: The impact of an immersive experience,”</article-title>
          <source>In Proceedings of the 2018 CHI conference on human factors in computing systems</source>
          ,
          <year>2018</year>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>10</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [16]
          <string-name>
            <surname>C-M. Karat</surname>
          </string-name>
          , “
          <article-title>A Business Case Approach to Usability Cost Justification</article-title>
          ,” In Bias, R.,
          <string-name>
            <surname>Mayhew</surname>
            ,
            <given-names>D</given-names>
          </string-name>
          . (eds.):
          <string-name>
            <surname>Cost-Justifying Usability</surname>
          </string-name>
          . Academic Press,
          <year>1994</year>
          , pp.
          <fpage>45</fpage>
          -
          <lpage>70</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [17]
          <string-name>
            <given-names>M.</given-names>
            <surname>Maguire</surname>
          </string-name>
          , “
          <article-title>Methods to support human-centred design,” International journal of human-computer studies</article-title>
          ,
          <volume>55</volume>
          (
          <issue>4</issue>
          ),
          <year>2001</year>
          , pp.
          <fpage>587</fpage>
          -
          <lpage>634</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [18]
          <string-name>
            <surname>P. M. Bösch</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          <string-name>
            <surname>Becker</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          <string-name>
            <surname>Becker</surname>
            and
            <given-names>K. W.</given-names>
          </string-name>
          <string-name>
            <surname>Axhausen</surname>
          </string-name>
          , “
          <article-title>Cost-based analysis of autonomous mobility services</article-title>
          ,
          <source>” Transport Policy</source>
          ,
          <volume>64</volume>
          ,
          <year>2018</year>
          , pp.
          <fpage>76</fpage>
          -
          <lpage>91</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [19]
          <string-name>
            <given-names>D.</given-names>
            <surname>Mayhew</surname>
          </string-name>
          and
          <string-name>
            <given-names>M.</given-names>
            <surname>Mantei</surname>
          </string-name>
          , “
          <article-title>A Basic Framework for Cost-Justifying Usability Engineering</article-title>
          ,” In Bias, R.,
          <string-name>
            <surname>Mayhew</surname>
            ,
            <given-names>D</given-names>
          </string-name>
          . (eds.): CostJustifying Usability. Academic Press,
          <year>1994</year>
          , pp.
          <fpage>9</fpage>
          -
          <lpage>43</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [20]
          <string-name>
            <given-names>K.</given-names>
            <surname>Ehrlich</surname>
          </string-name>
          and
          <string-name>
            <given-names>J.</given-names>
            <surname>Rohn</surname>
          </string-name>
          , “
          <article-title>Cost Justification of Usability Engineering: A Vendor's Perspective,</article-title>
          ” In: Bias,
          <string-name>
            <given-names>R.</given-names>
            ,
            <surname>Mayhew</surname>
          </string-name>
          ,
          <string-name>
            <surname>D</surname>
          </string-name>
          . (eds.): CostJustifying Usability. Academic Press,
          <year>1994</year>
          , pp.
          <fpage>73</fpage>
          -
          <lpage>110</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [21]
          <string-name>
            <given-names>G.</given-names>
            <surname>Donahue</surname>
          </string-name>
          , “
          <article-title>Usability and the Bottom Line,”</article-title>
          <source>IEEE Software</source>
          , Vol.
          <volume>18</volume>
          (
          <issue>1</issue>
          ),
          <year>2001</year>
          , pp.
          <fpage>31</fpage>
          -
          <lpage>37</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [22]
          <string-name>
            <given-names>N.</given-names>
            <surname>Bevan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Carter</surname>
          </string-name>
          and
          <string-name>
            <given-names>S.</given-names>
            <surname>Harker</surname>
          </string-name>
          ,
          <source>“ISO 9241-11 revised: What have we learnt about usability since</source>
          <year>1998</year>
          ?,” In International Conference on Human-Computer Interaction, Springer International Publishing,
          <year>2015</year>
          , pp.
          <fpage>143</fpage>
          -
          <lpage>151</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [23]
          <string-name>
            <given-names>M.</given-names>
            <surname>Aly</surname>
          </string-name>
          and
          <string-name>
            <given-names>C.</given-names>
            <surname>Sturm</surname>
          </string-name>
          , “
          <article-title>Hacks for Cost-Justifying Usability: FearSetting vs</article-title>
          . Goal-Setting,”
          <source>In Proceedings of the 21st International Conference on Human-Computer Interaction with Mobile Devices and Services</source>
          , ACM,
          <year>2019</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [24]
          <string-name>
            <given-names>M.</given-names>
            <surname>Rajanen</surname>
          </string-name>
          and
          <string-name>
            <given-names>N.</given-names>
            <surname>Iivari</surname>
          </string-name>
          , “
          <article-title>Usability Cost-Benefit Analysis: How Usability Became a Curse Word?,”</article-title>
          <source>In Proceedings of the INTERACT</source>
          <year>2007</year>
          . Rio de Janeiro, Brasil,
          <year>2007</year>
          , DOI: 10.1007/978-3-
          <fpage>540</fpage>
          -74800- 7_
          <fpage>47</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [25]
          <string-name>
            <given-names>M.</given-names>
            <surname>Rajanen</surname>
          </string-name>
          and
          <string-name>
            <given-names>D.</given-names>
            <surname>Rajanen</surname>
          </string-name>
          , “Usability Benefits in Gamification,
          <source>” Proceedings of the 1st GamiFIN Conference</source>
          , Pori, Finland,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          [26]
          <string-name>
            <given-names>M.</given-names>
            <surname>König</surname>
          </string-name>
          and
          <string-name>
            <given-names>L.</given-names>
            <surname>Neumayr</surname>
          </string-name>
          , “
          <article-title>Users' resistance towards radical innovations: The case of the self-driving car,” Transportation research part F: traffic psychology</article-title>
          and behaviour,
          <volume>44</volume>
          ,
          <year>2017</year>
          , pp.
          <fpage>42</fpage>
          -
          <lpage>52</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          [27]
          <string-name>
            <given-names>T.</given-names>
            <surname>Bellet</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Cunneen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Mullins</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Murphy</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Pütz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Spickermann</surname>
          </string-name>
          and
          <string-name>
            <given-names>M.</given-names>
            <surname>Baumann</surname>
          </string-name>
          , “
          <article-title>From semi to fully autonomous vehicles: New emerging risks and ethico-legal challenges for humanmachine interactions,” Transportation research part F: traffic psychology</article-title>
          and behaviour,
          <volume>63</volume>
          ,
          <year>2019</year>
          , pp.
          <fpage>153</fpage>
          -
          <lpage>164</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          [28]
          <string-name>
            <given-names>W.</given-names>
            <surname>Ribbens</surname>
          </string-name>
          , “
          <article-title>Understanding automotive electronics: an engineering perspective</article-title>
          ,” Butterworth-Heinemann,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          [29]
          <string-name>
            <surname>H. M. Sitorus</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          <string-name>
            <surname>Govindaraju</surname>
            ,
            <given-names>I. I.</given-names>
          </string-name>
          <string-name>
            <surname>Wiratmadja</surname>
            and
            <given-names>I. Sudirman</given-names>
          </string-name>
          , “
          <article-title>Interaction perspective in mobile banking adoption: The role of usability and compatibility</article-title>
          ,”
          <source>In 2017 International Conference on Data and Software Engineering (ICoDSE)</source>
          , IEEE,
          <year>2017</year>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>6</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          [30]
          <string-name>
            <given-names>G.</given-names>
            <surname>Nayanajith</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K. A.</given-names>
            <surname>Damunupola and R. J. M. Ventayen</surname>
          </string-name>
          , “
          <article-title>Website Usability, Perceived Usefulness and Adoption of Internet Banking Services in the Context of Sri Lankan Financial Sector,”</article-title>
          <source>Asian Journal of Business and Technology Studies</source>
          ,
          <volume>2</volume>
          (
          <issue>1</issue>
          ),
          <year>2019</year>
          , pp.
          <fpage>28</fpage>
          -
          <lpage>38</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          [31]
          <string-name>
            <given-names>R. R.</given-names>
            <surname>Gehani</surname>
          </string-name>
          , ”
          <article-title>Corporate brand value shifting from identity to innovation capability: from Coca-Cola to Apple,”</article-title>
          <source>Journal of technology management &amp; innovation</source>
          ,
          <volume>11</volume>
          (
          <issue>3</issue>
          ),
          <year>2016</year>
          , pp.
          <fpage>11</fpage>
          -
          <lpage>20</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          [32]
          <string-name>
            <given-names>A.</given-names>
            <surname>Nunes</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Reimer</surname>
          </string-name>
          and
          <string-name>
            <given-names>J. F.</given-names>
            <surname>Coughlin</surname>
          </string-name>
          , “
          <article-title>People must retain control of autonomous vehicles</article-title>
          ,
          <source>” Nature 556</source>
          ,
          <year>2018</year>
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          [33]
          <string-name>
            <given-names>G. H.</given-names>
            <surname>Walker</surname>
          </string-name>
          and
          <string-name>
            <given-names>N. A.</given-names>
            <surname>Stanton</surname>
          </string-name>
          , “
          <article-title>Human factors in automotive engineering</article-title>
          and technology,” CRC Press,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>