<!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>A Systematic View on Speech Assistants for Service Technicians?</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Joachim Baumeister</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Veronika Sehne</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Carolin Wienrich</string-name>
        </contrib>
      </contrib-group>
      <abstract>
        <p>The paper gives a systematic view on speech assistants in the eld of technical service of industrial machines. We describe the results of a requirements analysis targeting companion technologies for service technicians and we report on a rst reference implementation. The effectiveness of the approach is evaluated in a diagnosis task scenario and preliminary results of a user study are discussed. knowledge-based diagnosis system intelligent personal assistant speech interaction dialog systems ?Supported by German BMWi Project Grant ZF4172703BZ7 (MARS project) Copyright c 2019 for this paper by its authors. Use permitted under Creative Commons License Attribution 4.0 International (CC BY 4.0).</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Motivation</title>
      <p>Intelligent personal assistants for private use are implemented in many devices
nowadays. With their availability in smartphones, watches, and TVs, they
diffused into daily life and support users when, for instance, sending text messages,
setting reminders, and starting apps or media channels. They simplify the use
of existing technology by making it more intuitive and quicker in execution.</p>
      <p>
        In general, an intelligent personal assistant provides a natural language
interface to take requests from the user and perform corresponding actions. Today,
many assistants interact with the user by a speech interface. In research, the
development of (smart) speech assistants was elaborated in many works, for
instance see [
        <xref ref-type="bibr" rid="ref1 ref11 ref12 ref3 ref9">1, 3, 9, 11, 12</xref>
        ]. In this paper, we ask the research question, whether
and how the obvious bene ts of such assistants can be transferred from personal
life to industrial use cases. Here, we especially look for applications of speech
assistants in the context of Technical Service. In general, the domain of
Technical Service considers the operation, the optimization and maintenance, and the
repair of often very complex industrial machines.
      </p>
    </sec>
    <sec id="sec-2">
      <title>Background and Related</title>
    </sec>
    <sec id="sec-3">
      <title>Work</title>
      <sec id="sec-3-1">
        <title>Assistance Systems for Service Technicians</title>
        <p>Today's assistance systems for service technicians are often structured like search
applications of the 2000er years: Providing simple textual search interfaces the
technician need to manually formulate an appropriate query and click through
the delivered results. Only a few number of systems provide a kind of semantic
interface that is able to return relevant information bits not necessarily
matching the original but the intended meaning of the query. Also, the technicians
are required to actually hold and touch the assistance system's device. Speech
assistants would enable the technicians to intuitively formulate the information
request and also free them to touch a keyboard device while doing so. The aim of
the present study is an user-centered development of a personal speech assistant
for service technicians.
2.2</p>
      </sec>
      <sec id="sec-3-2">
        <title>User-Centered Design Process</title>
        <p>
          Norman and Draper [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ] introduced the user-centered-design (UCD) process which
condensed di erent approaches and methods known in the eld of
human-computer-interaction (HCI). Similar, the DIN EN ISO 13407 describes the basic
steps of user-centered design processes consisting of the analysis of the context,
the analysis of requirements as well as the iterative design and evaluation of
gestalt solutions [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ]. Integrating di erent perspectives, the approach of
contextual design [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ] involves users to analyze and evaluate systems (includes often
summative evaluations) and the approach of usability engineering [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ] involves
experts (includes often formative evaluations) [
          <xref ref-type="bibr" rid="ref10 ref8">8, 10</xref>
          ]. The outer blue circle of
Figure 1 demonstrates the common steps of the UCD process and how they are
intertwined.
        </p>
        <p>
          Even though, the UCD process is well established in the HCI, context and
requirement analyses for speech assistance systems are rare. Dumas et al. [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ]
developed a guideline for multi-modal user interfaces including speech. However,
the guideline seems rather universal and not speci c enough to meet the
requirements of a personal speech assistance for service technicians. Thus, the present
article analyses the context and requirements of service technicians to design an
user-centered speech assistance including an expert and user evaluation.
3
        </p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Analyzing Phase in the Present Study</title>
      <p>Our use-context is the domain of the Technical Service, focusing particularly on
the service technician. For this reason, we rst introduce the domain of
Technical Service of industrial machines and then domain speci c tasks, environmental
conditions, and experiences of a service technician. The use-context and rst
implications for the development of a speech assistant were analyzed iteratively by
three experts from the domains human-computer-interaction and technical
services. The analyses of context result in four prototypical personas. We conclude
the section with a description of the context-related requirements, that|in the
view of experts|a targeted speech assistant need to meet. Figure 1 shows the
key points of the analyzing phase in the present study (inner red circle, green
area).
3.1</p>
      <sec id="sec-4-1">
        <title>Analyzing the Use-Context: The Domain of Technical Service</title>
        <p>Advanced industrial machinery is one of the most driving domains in today's
life. Machinery produces almost all consumer goods with high e ciency. In this
case, it touches all aspects of personal life, for instance harvesting machines
feeding the food production of animals and humans, paper making and printing
machines to produce newspapers, and automotive factories to produce cars and
trucks.</p>
        <p>However, machinery needs to be safely operated and maintained for its
optimal performance. In case of malfunction it need to be brought back to work
quickly. Often, the standstill of such machines yield exceptional costs in the area
of hundreds of euros and more|per minute. The Technical Service, and namely
the service technicians, are responsible for the maintenance, performance
optimization, diagnosis and repair of industrial machinery.
3.2</p>
      </sec>
      <sec id="sec-4-2">
        <title>Analyzing Work-related Characteristics of a Service Technician:</title>
      </sec>
      <sec id="sec-4-3">
        <title>Domain Tasks, Environmental Conditions, and Domain</title>
      </sec>
      <sec id="sec-4-4">
        <title>Experiences</title>
        <p>Domain Tasks As an overall goal, the service technician should make sure
to maintain the machine state and sometimes even to optimize the machine
performance. To archive these goals we distinguish the following sub-tasks:
1. Operation and monitoring of the machine performance
2. Disassembly/assembly of machine components (optimization/repair)
3. Diagnosis of faulty machine behavior
4. Maintenance operations for a machine
5. Documentation of accomplished work for commercial and knowledge
management reasons</p>
        <p>The present paper focuses on the task of diagnosis including the use of an
information system with a guided troubleshooting on the one hand and the work
around/in/on/under the machine during the diagnosis on the other hand. The
latter involves the use of special tools or working gloves while the former
requests two free hands for navigate through the di erent diagnosis steps. As
consequences for the development of the speech assistance result the implications of
the integration of the speech assistant in a diagnosis interface of a semantic
information system on the one hand and the possibility of a hands-free interaction
on the other hand.</p>
        <p>Environmental Conditions The service technician accomplishes the tasks
within changing environmental parameters. Basically, the experts distinguish the
following main parameters that a ect the quality and speed of the technicians
work:
1. Location The technician is working in a workshop or \in- eld". As
consequences for the development of the speech assistant we see:
{ (Reduced) availability of required tools
{ (Reduced) support and knowledge provided by on-site colleagues
{ (Reduced) Internet access for remote communication
2. Supporting Information and Infrastructure considers the availability of
information resources in breadth and depth, e.g., technical documentation,
diagnostic systems, maintenance plans, communication channels, and
mobile devices. As consequences for the development of the speech assistant
result we see:
{ Required infrastructure for providing information resources (cloud
systems and storage)
{ Di erent levels of information can be provided depending on the
availability of mobile devices
3. Limited Time may stress the technician to complete the task. This primary
limitation in uences the use of tools, the quality of work, and the type of
possible tasks. As consequences for the development of the speech assistant
result we see:
{ Speech assistants need to be adaptable with respect to the available time
and mental workload of the user. This a ects the query patterns, the
possible intents, and the (extensive) answers provided by the assistant.
Domain Experience The performance of the overall service task heavily
depends on the experience of the technician. In general, it is di cult to classify the
individual experience, but some indicators can help to distinguish di erent
experience levels: a) The number and type of training sessions completed in recent
years and b) The years of work in the particular domain.</p>
        <p>Some companies de ne speci c levels of experience based on the type of
work the technician can complete individually, e.g., from Level 1 (Technician
can safely operate the machine) to Level 4 (Technician can safely diagnose and
repair faulty behaviour for which diagnostic knowledge is available) and up to
Level 5 (Technician can safely diagnose and repair a previously unknown issue).
Consequentially, a speech assistant should support the individual experience level
of a service technician.
3.3</p>
      </sec>
      <sec id="sec-4-5">
        <title>Four Prototypical Personas of a Service Technician</title>
        <p>Based on the analysis of basic work-related characteristics of a service
technician's tasks, environmental conditions, and domain experiences, the experts
identi ed four typical personas, that represent di erent prototypes of service
technicians. They focus in variations on domain experience and the available
time to complete a given task. Thus, the four personas represent a typical
crossselection of the domain of Technical Service.</p>
        <p>e Brad
iTm Brave
Carl
Conservative</p>
        <p>Teresa
Thorough
Frank
Frantic</p>
        <p>Experience</p>
        <p>In Figure 2, we see a classi cation of the identi ed personas: Brad Brave ("I
am happy to learn new stu every day!") is innovation friendly, but a beginner
of the domain. He has the motivation to use new things and invests time into
the exploration and use of information systems. Carl Conservative ("I cannot
spend extra time for this additional stu .") also has not much experience in the
eld but has not motivation to invest time, e.g., in the exploration and use of an
information system. Frank Frantic ("It is about the bolts not about the apps!")
is very experienced in the domain, but shows no interest to explore new tools
that possibly may improve his work. Theresa Thorough ("I love to improve every
day!") has much experience in the domain and also is very innovation-friendly.
She is interested to further improve her personal performance by trying and
using advanced tools.
3.4</p>
      </sec>
      <sec id="sec-4-6">
        <title>Analyzing Requirements</title>
        <p>Following the context analysis, three experts analyzed speci c requirements for
developing a speech assistant for service technicians. In summary, 28
requirements were identi ed and clustered in ve categories. Table 1 shows the ve
clusters and examples of the corresponding speci c requirements.</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>Evaluation Phase 1: Expert Evaluation of Analyzed</title>
    </sec>
    <sec id="sec-6">
      <title>Requirements</title>
      <p>In order to proof the relevance of the analyzed requirements, ten independent
experts (age: 23 to 43 years, 9 male) from the eld of diagnostic dialogues
revisited the 28 requirements and rated the importance on a ve-point Likert scale,
ranging from 1 (strongly disagree) to 5 (strongly agree).</p>
      <p>Table 2 shows the requirement clusters and ratings of the second expert
group. Symptom detection was rated as most important, followed by
orientation within the dialog, speech recognition, and explanations. Trust in the speech
assistant was rated as less important.</p>
      <p>In addition to the 28 requirements identi ed by the rst expert group, the
second expert group found 11 requirements. These 11 additional requirements t
in the above presented requirement clusters and did not changed the importance
pattern of the clusters.</p>
      <p>In sum, the two expert groups identi ed 40 requirements clustered in ve
groups with di erent importance for the development of a speech assistant for
service technicians.</p>
      <p>The rst conceptional design of the speech assistant targets on the
prototypical persona of Brad Brave (see Figure 2), because he is innovation-friendly and
invests time into the exploration and use of information systems. Due to his
limited working experience (Level 3, i.e., needs guidance), his working performance
and experience can be improved by companion technologies. From the identi ed
requirements, Brad needs the following:
{ The assistant works o ine and online, because the availability is required
not only in the workshop but also on{ eld with a probably worse internet
connection.
{ Brad often needs both hands to accomplish the service work, thus the
assistant should be able to operate hands-free.
{ The assistant needs to support the following tasks:</p>
      <p>Basic information research for technical documentation</p>
      <p>Support a diagnosis task by a guided diagnostic dialog</p>
      <p>Following these requirements the assistant should be helpful for the
remaining personas as well, at least in some situations. In the subsequent section, we
introduce a concept of a speech assistant for the service technician Brad Brave,
that takes the considerations from above into account.
5
5.1</p>
    </sec>
    <sec id="sec-7">
      <title>Design Phase: Personal Assistant for Technicians</title>
      <sec id="sec-7-1">
        <title>Conceptual View</title>
        <p>The competence of a personal speech assistant can be characterized by the
collection of intents it understands and can react on. Intents are formulated by
the user in natural language and require one or more corresponding actions
performed by the assistant. The requirements stated above yield the following
main intents: a) Search for information in the available technical documentation.
b) Provide diagnostic support for a speci c problem description.</p>
        <p>User Interface</p>
        <p>Automated</p>
        <p>Speech
Recognition</p>
        <p>Image
Recognition
action
query
query</p>
        <p>Action
Execution</p>
        <p>Intent
Identification</p>
        <p>update
use</p>
        <p>Context
Query Formulation An advanced user interface of an assistant is able to capture
the user query in di erent modalities, e.g., speech utterances, video images and
basic touch/text input. In the context of this paper, we focus on query
formulation using speech utterances. The query needs to be transparently elicited by
the system, i.e., the user sees the entered input instantly in the system while
actually providing it. This is trivial for keyboard entries but also the text of
recognized speech input and captured video images should be displayed to the
user for transparent tracability.</p>
        <p>Deliver Action The user interface outputs the results of the actions derived by
the assistant. In the simplest case, the assistant simply displays the document
the user asked for. In the case of a guided diagnosis system, the action module
delivers an interactive dialog with the user.</p>
      </sec>
      <sec id="sec-7-2">
        <title>Automated Speech Recognition (ASR) This module transforms spoken</title>
        <p>text (sound waves) into text input, so it can be later analyzed by the subsequent
intent module.</p>
        <p>Intent Identi cation The intent identi cation is responsible for the semantic
interpretation of the recognized text. The module tries to identify the request
of the user in order to nd an appropriate action for the request. It includes
techniques from natural language understanding and question answering. Classic
approaches are based on rules and patterns, but recently also statistical learning
approaches were introduced.</p>
        <p>Action Module Based on the recognized intents an appropriate action is
selected. In our scenario, we refer to the tasks that a speech assistant should
support (see Section 3.4): Support the documentation research by providing
useful information and facts for a given question and the support for diagnostic
questionnaires.</p>
        <p>Context Update The assistant is able to track the work of the technician
and uses this work context to support the intent identi cation and the action
selection.</p>
        <p>Typical task information elements are the previously stated queries, the
selected actions, and the environment of the current use.
5.2
A prototypical implementation of the speech assistant was developed for the
existing information system Service Mate (http://www.servicemate.de). Originally,
the application serves as an information system for the research and
consumption of technical service documentation. For the implementation of the diagnosis
capabilities, the existing speech assistant was extended by an interactive speech
dialog. The diagnostic dialog now can be started by simply stating "start
diagnosis" into the speech input.</p>
        <p>Figure 4 depicts an example dialog of the diagnosis system. Here, the
malfunction of a bicycle is analyzed by a question{answer dialog. The gure shows
a question asking for the wear of the wheel rim with possible answers "visible"
and "not visible". The multi-modal interface of the system allows for simply
touching the buttons to answer the question, but also the answer can be given
by speech input. After answering the question the next best relevant question is
asked in order to derive a possible cause for the observed fault of the bike.</p>
        <p>The next section outlines the second evaluation phase. Note, that the
complete user evaluation is not described in this paper due to space constraints.
6</p>
      </sec>
    </sec>
    <sec id="sec-8">
      <title>Evaluation Phase 2: User Evaluation of Speech</title>
    </sec>
    <sec id="sec-9">
      <title>Assistant</title>
      <p>In order to investigate whether the speech assistant indeed support the service
technician, we compared the user experience of the developed speech interaction
with the established touch interaction of the system as well as expectations
previous the usage.
Participants The study was conducted by 26 participants having a mean age
M = 31.23 with standard deviation SD = 7.98, 4 females. The participants had
medium experience with the information system.</p>
      <p>Material and Procedure The empirical study use an exemplary but fully
functional service system for a bicycle, i.e., the dBike system. Besides the
technical documentation, a circuit diagram, and a 3D model the system also contains
diagnosis routines for the most relevant functions of the bike. The experiments
were conducted at a bike, a roughedized tablet computer was running the
information system with the touch and speech interaction. Additionally, a separate
speaker broadcasts the speech instructions. A further notebook was provided
for answering the questionnaires of the experiment study. Participants had two
tasks: (i) the diagnosis of faults with the gear shift and (ii) the diagnosis of a
malfunction of the brake. The bike was specially prepared for each task. For
the examination of the bike, the persons need to use the work gloves. Hence,
for using the tablet computer, participants had to undress the gloves for touch
interaction. In addition, some diagnostic steps request the usage of a special
measuring tool.</p>
      <p>Half of participants conducted the diagnosis using the speech assistant, the
other half was using the touch interaction on the tablet (independent variable:
mode of interaction). The groups only di er in the mode of interaction
implying that participants using the touch interaction had to move between the bike
and the laptop for each diagnostic step and had to undress the gloves for
interaction on the one side. On the other side, participants using touch interaction
saw pictures with instruction. If participants of the speech interaction need a
visualization, they had to move to the touch laptop, too.</p>
      <p>Previous to the interaction, all participants provided demographical
information. Participants using speech interaction rated the expected usefulness and
expected problems of speech interaction for the diagnosis process on a 5-point
Likert scale ranging from 1 (not useful) to 5 (very useful), or 1 (many
problems) to 5 (no problems), respectively. After their interaction with the speech
assistant, we assessed qualitatively positive and negative experiences. While the
participants using speech interaction assessed their expectation prior the
experiment, participants using touch interaction assessed the expected usefulness and
problems of speech interaction after the experiment on a 7-point Likert scale
ranging from 1 (not useful) to 7 (very useful), or 1 (many problems) to 7 (no
problems), respectively. Other questionnaires were applied, but are not reported
in the present paper.
6.2</p>
      <sec id="sec-9-1">
        <title>Results</title>
        <p>Prior the interaction with the speech assistant, participants rated speech
assistance to support the diagnosis process as rather useful (M = 3.92, SD = .64,
range between 1 and 5). The auditive interaction mode and the corresponding
free-hand interaction were mentioned as most frequent reasons. But also
problems were expected (M = 3.62, SD = .51, range between 1 and 5). Most problems
were expected for the speech recognition. Further, some participants expected
problems with the comprehension of diagnostic instructions. After the
interaction with the speech assistant, most participants liked the hand-free interaction,
the ease of use, and the intuitive control commands. On the other side,
participants reported negative experience concerning the restricted use of language and
the fact that they cannot interrupt the speech assistant when it was speaking.</p>
        <p>After the interaction with the touch based assistant, participants also
expected speech assistance as rather useful to support the diagnosis process (M =
5.58, SD = 1.31, range between 1 and 7) and as medium problematic (M = 4.83,
SD = 1.40, range between 1 and 7). The reasons for their ratings were similar
to those of the pre-experimental ratings. Free-hand interaction were mentioned
most frequently for a useful application. Speech detection and the comprehension
of diagnostic instructions were mentioned as most frequently problems. Further,
participants using touch interaction reported positive experiences with pictures
supporting the comprehensive of the corresponding diagnosis steps. Undressing
the gloves for touch interaction was experienced as negatively.
6.3</p>
      </sec>
      <sec id="sec-9-2">
        <title>Discussion</title>
        <p>The results revealed the potentials of speech assistance in the domain of
technical services. Particularly, the possibility of hand-free interaction is expected as
useful. However, the results also revealed concerns. The use of auditive guidance
might lead to comprehensive problems and pictures support the
comprehension of corresponding diagnosis steps. Thus, a multi-modal interaction providing
hands-free speech interaction and the visualization of 3D-models might be the
best support for service technicians.
7</p>
      </sec>
    </sec>
    <sec id="sec-10">
      <title>Conclusions</title>
      <p>In this paper we introduced speech assistants in the domain of Technical
Service. Based on a user-centered requirements analysis for service technicians, we
selected a number of relevant requirements to be implemented in an existing
information system. We evaluated the research question, whether and how speech
assistants can support a service technician. In the experiment we focused on
the diagnosis task. In the future, we are planning to extend the reported user
studies to a diverse range of speci c research questions. Particularly, a
comparison of speech, touch, and multi-modal interaction is planned for future studies.
Further, a eld study including real service technicians is planned.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Christensen</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Casanueva</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cunningham</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Green</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hain</surname>
          </string-name>
          , T.:
          <article-title>homeService: Voice-enabled assistive technology in the home using cloud-based automatic speech recognition</article-title>
          .
          <source>In: 4th Workshop on Speech and Language Processing for Assistive Technologies</source>
          . pp.
          <volume>29</volume>
          {
          <issue>34</issue>
          (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Dumas</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lalanne</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Oviatt</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Multimodal interfaces: A survey of principles, models and frameworks</article-title>
          .
          <source>In: Human machine interaction</source>
          , pp.
          <volume>3</volume>
          {
          <fpage>26</fpage>
          . Springer (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Hamerich</surname>
            ,
            <given-names>S.W.</given-names>
          </string-name>
          :
          <article-title>Benutzerfreundliche Sprachdialoge im Automobil</article-title>
          .
          <source>In: Sprachbedienung im Automobil</source>
          , pp.
          <volume>61</volume>
          {
          <fpage>77</fpage>
          . Springer (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Holtzblatt</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Beyer</surname>
          </string-name>
          , H.:
          <article-title>Contextual design: Design for life</article-title>
          . Morgan Kaufmann (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>ISO</surname>
          </string-name>
          , I.:
          <volume>13407</volume>
          :
          <article-title>Human-centred design processes for interactive systems</article-title>
          .
          <source>Geneva: ISO</source>
          (
          <year>1999</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Nielsen</surname>
          </string-name>
          , J.:
          <article-title>Heuristic evaluation</article-title>
          .
          <source>In: Usability inspection methods</source>
          . pp.
          <volume>25</volume>
          {
          <fpage>62</fpage>
          . John Wiley &amp; Sons, Inc. (
          <year>1994</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Norman</surname>
            ,
            <given-names>D.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Draper</surname>
            ,
            <given-names>S.W.:</given-names>
          </string-name>
          <article-title>User centered system design: New perspectives on human-computer interaction</article-title>
          . CRC Press (
          <year>1986</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Rubin</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chisnell</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Handbook of usability testing: how to plan, design and conduct e ective tests</article-title>
          . John Wiley &amp; Sons (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Santos</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rodrigues</surname>
            ,
            <given-names>J.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Casal</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Saleem</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Denisov</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          :
          <article-title>Intelligent personal assistants based on internet of things approaches</article-title>
          .
          <source>IEEE Systems Journal</source>
          <volume>12</volume>
          (
          <issue>2</issue>
          ), 1793{
          <year>1802</year>
          (
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Sarodnick</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Brau</surname>
          </string-name>
          , H.:
          <article-title>Methoden der usability evaluation</article-title>
          .
          <source>Wissenschaftliche Grundlagen und praktische Anwendung</source>
          <volume>1</volume>
          (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Sidner</surname>
            ,
            <given-names>C.L.</given-names>
          </string-name>
          :
          <article-title>Building Spoken-Language Collaborative Interface Agents</article-title>
          , pp.
          <volume>197</volume>
          {
          <fpage>226</fpage>
          . Springer Netherlands, Dordrecht (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Wobcke</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ho</surname>
            ,
            <given-names>V.H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nguyen</surname>
            ,
            <given-names>A.T.L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Krzywicki</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>A BDI agent architecture for dialogue modelling and coordination in a smart personal assistant</article-title>
          . IEEE/WIC/ACM International Conference on Intelligent Agent Technology pp.
          <volume>323</volume>
          {
          <issue>329</issue>
          (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>