<!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>Evaluation of user interface adaptation strategies in the process of model-driven user interface development</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Kai Breiner, Volkmar Gauckler</string-name>
          <email>breiner@cs.uni-kl.de</email>
          <email>breiner@cs.uni-kl.de, volkmar.gauckler@gmx.net</email>
          <email>volkmar.gauckler@gmx.net</email>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Marc Seissler</string-name>
          <email>Marc.Seissler@mv.uni-kl.de</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Gerrit Meixner</string-name>
          <email>Gerrit.Meixner@dfki.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>ACM Classification Keywords</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>German Research Center for, Artificial Intelligence (DFKI)</institution>
          ,
          <addr-line>Trippstadter Str. 122, 67663, Kaiserslautern</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>H5.2. Information interfaces and presentation (e.g., HCI):</institution>
          ,
          <addr-line>Evaluation/methodologie, Prototyping, User-centered, design.</addr-line>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>University of Kaiserslautern, Center for Human-MachineInteraction</institution>
          ,
          <addr-line>Gottlieb-Daimler Str., 67663, Kaiserslautern</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>University of Kaiserslautern, Software Engineering Research, Group</institution>
          ,
          <addr-line>Gottlieb-Daimler Str., 67663, Kaiserslautern</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <fpage>17</fpage>
      <lpage>20</lpage>
      <abstract>
        <p>In this paper, we describe the evaluation of our prototype Universal Control Device (UCD), which enables the control of various devices in modern dynamic production environments, while being able to adapt itself to the current configuration of the environment. While it is hard to apply traditional user interface design heuristics in recent paradigms - such as Ambient Intelligence - there is a demand for suitable compensation strategies addressing usage errors, which can be met by applying an adequate adaptation strategy. In a pilot study, we gained experience regarding differences in the performance of selected adaptation strategies in the case of our demonstrator.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>Device,</p>
      <p>Adaptation</p>
      <p>Strategies,</p>
      <p>
        INTRODUCTION
The ongoing technological development of
microelectronics and communication technology is leading
to more pervasive communication between single devices
or entire pervasive networks of intelligent devices (smart
phone, PDA, netbook, etc.). Especially industrial devices
and applications can take advantage of modern smart
technologies, e.g., based on ad-hoc networks, dynamic
system collaboration, and context-adaptive human-machine
interaction systems. The vision of Mark Weiser [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]
Permission to make digital or hard copies of all or part of this work for
personal or classroom use is granted without fee provided that copies are
Prneo-ptrmocaedeedionrgsdoisfttrhibeu5ttehdInfoterrnpartoiofintaolrWcoormksmhoeprcoinalMaoddvealnDtarigveenanDdevtehlaotpcmoepnites
ofbAeadrvathnicsednoUtsiecreInatnedrfathcees f(uMllDcDitAatUioIn20o1n0)t:hBerifdirgsitngpabgetew. eTeon UcosepryEoxtpheerirewnicsee,
anodr UreIpEunbgliinsehe,ritnog,poorgstanoiznedseartvtheers28otrh tAoCrMedCisotnrifberuetnecetoonliHstusm,arenqFuaicrteosrspirnior
CsopmepcuiftiincgpSeyrmsteismssio(nCHanId2/0o1r0a), fAetel.anta, Georgia, USA, April 10, 2010.
CHI 2009, April 4–9, 2009, Boston, Massachusetts, USA.
      </p>
      <p>
        CCopoypryigrhigth©t 22001009fAorCthMe in9d7iv8i-d1u-a6l0p5a5p8er-s2b4y6-t7he/0p9a/p0e4r.s.'.$au5t.h0o0r.s. Copying
permitted for private and academic purposes. Re-publication of material from this
volume requires permission by the copyright owners. This volume is published by
its editors.
concerning ubiquitous computing – also in production
environments – is becoming a reality [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ].
      </p>
      <p>In today’s production environments, technical devices often
stem from multiple vendors using heterogeneous user
interfaces that differ in terms of complexity, look&amp;feel, and
interaction styles. Such highly complex and networked
technical devices or systems can provide any information at
any time and in any place. This advantage can turn out to be
a disadvantage when information is not presented properly
according to the users’ needs. This leads to problems,
especially concerning the usability of the user interface.
The level of acceptance of a user interface largely depends
on its ease and convenience of use. A user can work with a
technical device more efficiently if the user interface is
tailored to the users’ needs, on the one hand, and to their
abilities on the other hand. Therefore, providing
information in a context- and location-sensitive manner
(depending on user, situation, machine, environmental
conditions, etc.) has to be ensured.</p>
      <p>Hence, in the following we will give a short introduction to
the SmartFactoryKL, which serves as a demonstration
environment for future intelligent production environments,
and a Universal Control Device (UCD), which provides
holistic control to various devices in such environments.
Further, we give a brief introduction to user interface
adaptation, usage errors, as well as to their compensation.
After presenting our idea of how to approach compensation
by using adaptation strategies, we describe the set-up of the
corresponding controlled experiment and the preliminary
results of the pilot study conducted. We conclude with the
interpretation of how the results contribute towards our
hypothesis.</p>
      <p>SmartFactoryKL
Besides these aspects, modern production environments are
characterized by a modular layout. Entire modules can be
replaced or reorganized. Furthermore, these environments
are able to react to errors occurring in the production
process (e.g., device malfunction) and to dynamically
reorganize parts of the process in order to ensure the
production process. Thus, this also affects the user who
interacts with the individual devices – the user’s workflow
will change, or devices will not be available anymore.
Basically, there are two kinds of operating errors that may
lead to a failure of the system.</p>
      <p>
        Serving as a demonstration environment, the
SmartFactoryKL in Kaiserslautern, Germany is able to
simulate such a process. In previous work, we developed a
UCD, which is able to provide access to various devices of
the SmartFactoryKL [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ][
        <xref ref-type="bibr" rid="ref4">4</xref>
        ].
      </p>
      <p>
        Universal Control Device (UCD)
As a result of a model-driven process, the user interface of
the UCD is being generated at run-time [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. Starting with a
topological description of the environment, enriched with
user tasks on the single devices and information about how
to address the single devices, this information is sufficient
for generating a functional user interface [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ][
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. In order to
remain functional to the user, this user interface has to
correspond to the current configuration of the environment
and is additionally restricted to the functionality as
specified in the underlying model. During field studies,
faced by the need to adapt the user interface, we
encountered the demand for a systematic strategy that
would support the user as much as possible [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. This was
the trigger for a study on adaptation, which we will describe
in the following.
      </p>
      <p>
        ADAPTATION
After giving a brief overview of different types of
adaptation – their properties as well as their impact on the
users’ workflow – we will elaborate types of usage errors
resulting from static user interfaces and how adaptive user
interfaces contribute to the compensation of such errors.
Static versus Dynamic User Interfaces
On the one hand, one important usability quality attribute is
memorizability. The ease to remember helps users to speed
up the process of interacting with the user interface [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ][
        <xref ref-type="bibr" rid="ref6">6</xref>
        ].
Since humans have a very visual memory, the way a certain
user interface is structured is essential for finding items
faster. After a while, users form a coherent model of the
user interface and are able to recall how to execute their
workflow. If the system (and therefore the user interface)
changes frequently, the user will not be able to form such a
model [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ][
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. On the other hand, there are user interface
heuristics demanding that the user interface matches the
real world [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. In order to provide control over devices in
dynamic environments – such as the SmartFactoryKL – it is
extremely vital to match the user interface to the real world
in order to remain functional.
      </p>
      <p>These simple rules about how to develop a user interface
appear to be contradictory for future information systems in
our application domain. Hence, there is a need for an
adaptation strategy that does not violate usability quality
attributes leading to usage errors.</p>
      <p>Usage Errors
In general, for each kind of usage error, there is a basic
cause (see Figure 1). Using the right compensation
technique – such as adaptation of the user interface – the
users can be actively supported in preventing usage errors.
In the first case, there are slips. Here, the user had the
correct intention but executed the task in the wrong way.
Most often this is caused by poor physical skills, or by the
user interface just being just inadequate for use (e.g.,
buttons too small). In the second case – which is more
interesting in our example – there are errors. Errors are
characterized by the user having the wrong intention while
executing the task. This is caused by a misunderstanding of
the user interface (e.g., if the user interface is offering
control over devices that are not available physically).</p>
    </sec>
    <sec id="sec-2">
      <title>Usage Error</title>
    </sec>
    <sec id="sec-3">
      <title>Cause</title>
      <p>Slips
Error</p>
    </sec>
    <sec id="sec-4">
      <title>Compensation</title>
      <p>Adapt to
Environment
Adapt to User</p>
      <p>Misunderstanding</p>
      <p>Skills</p>
      <p>Compensation
Depending on the type of usage error, there are different
ways to compensate in order to minimize the effect. Slips,
which are caused by poor skills of the user, can be
prevented by adapting the user interface to the user. In case
of our application domain – intelligent production
environments – we are dealing with predefined user roles
and user groups and are therefore able to tailor the user
interface to the needs of these user groups.</p>
      <p>In dynamic environments, errors can be prevented by
adhering to design heuristics as mentioned earlier. The
system has to represent the current configuration of the user
interface, while supporting the development of a mental
model. Hence, a method of adaptation needs to be chosen
that contributes to these heuristics.</p>
      <p>Types of Adaptation
There are different methods of how an adaptation of the
user interface can be executed. These methods differ in
their way of execution as well as in their degree of intrusion
into the users’ workflow. In case of the UCD, a simple
adaptation scenario would be the appearance or
disappearance of devices in the device selection list. In the
following, we will refer to this example while giving details
about the individual methods.</p>
      <p>The first method – which was implemented initially and led
to the investigation described in this paper – is ad-hoc
adaptation. Here, devices are added or removed from a
device list according to the physical status of the respective
devices. Unless a regular user permanently observes the
device list, he or she will not notice any change.
Furthermore, this will be distracting for the user, because
the structure of the user interface changes without
notification.</p>
      <p>
        Providing more information about the system state leads to
the second adaptation method – notification. Now, the user
interface provides information about the change and
therefore supports the user in adapting his or her mental
model. In case of the device list example, we implemented
this method by applying the so-called instant-messenger
metaphor [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. This means that new or defective devices will
be emphasized graphically, which provides information for
the user to understand the current state of the system.
However, the user may just overlook the notifications if he
or she is distracted, and then the system cannot provide
further support.
      </p>
      <p>Thus, we implemented a third adaptation strategy, which
aims at confirmation by the user. Here, the user has to
actively confirm the change to the user interface. Referring
to the device list of the example above, this strategy was
implemented in terms of a dialog box asking for
confirmation from the user that he or she has actually
noticed the adaptation of the system. Thus, the system can
be almost sure that the user is aware of the adaptation and is
supported in the presumably most adequate way. A
negative side-effect of this strategy is that the confirmation
dialog may distract the user during his/her regular
workflow.</p>
      <p>Compensation
Each of the adaptation strategies differs as to how much it
contributes to the compensation of possible usage errors.
Ad-hoc adaptation ensures consistency between the
controllable environment and the corresponding user
interface in order to prevent usage errors with respect to
outdated user interfaces. But this approach provides no
active support to the user at all.</p>
      <p>Besides consistency with the current configuration of the
environment, notification provides limited feedback to the
user (e.g., by visually emphasizing new devices). Due to the
fact that this communication with the user is unidirectional,
such notifications can be easily overlooked by the user.
Confirmation provides all the functionality of the first two
approaches on the one hand and demands confirmation by
the user on the other hand. Thus, the user interface is aware
of the fact that the user has recognized the new
configuration and can therefore proceed with the regular
functionality.</p>
      <p>Hypothesis
According to the diverse properties of these strategies, we
wanted to investigate which is the most adequate one in the
case of our model-driven approach and therefore we
formulated hypotheses that we are going to verify or falsify
initially in a preliminary study described below. The
hypotheses are tailored to the specific set-up of the
controlled experiment.</p>
      <p>H1. Effectiveness – completion rate
We assume that, on average, at least 85,6% of the test tasks
can be completed without help.</p>
      <p>Explanation: This hypothesis assumes that test persons can
deal with the user interfaces and have understood their tasks
and therefore can complete at least 6 out of the 7 tasks.
H2. Effectiveness – assistance
100% of the given tasks can be completed (with help – if
needed).</p>
      <p>Explanation: The user interface ensures consistency
between environment and visualization independent of the
adaptation strategy. Therefore, it should be possible to
complete each task.</p>
      <p>H3. Efficiency – strategy performance
Confirmation outperforms notification, which outperforms
ad-hoc adaptation.</p>
      <p>Explanation: On the basis of the different attributes
elaborated earlier, we assume this ranking according to the
performance of the different strategies.</p>
      <p>
        EVALUATION – PILOT STUDY
To evaluate these hypotheses, we decided to conduct a
controlled experiment. We implemented three instances of
our model-driven process [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ][
        <xref ref-type="bibr" rid="ref3">3</xref>
        ][
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], including the
corresponding adaptation strategies. The test persons had to
complete seven tasks on the user interface, while the
simulated production environment always reconfigured
between task 2 and task 3. The idea was that the adaptation
should only affect task 4, which had to be executed in a
different way (as a result of the adaptation) than indicated at
first. The other tasks served as an indication that the test
persons perform in a similar way. We conducted a pilot
study with several computer science students. All six test
persons were between 21 and 34 years old.
      </p>
      <p>After being asked for personal statistical information, the
test persons got a thorough introduction to the production
industry domain. They were provided with a detailed
explanation of the simulated production environment as
well as of our Universal Control Device. After execution of
task 2, we initiated the reconfiguration of the simulation
and, depending on the strategy used (of which the test
persons were not aware) the user interface adapted itself,
notified the user, or demanded confirmation. The strategies
were distributed equally between the tests. Due to the
adaptation of the environment, the user should not be able
to complete task 4 in the way the task description called for.
One of three redundant pumps was removed from the
system. Here, the user should conclude that (as displayed in
the documentation of the simulated environment) there are
various ways to complete this task and ask the moderator if
this is possible. The test was completed with a survey about
the subjective properties of the user interface.</p>
      <p>Results
Figure 2 shows the results of the performance of the single
tasks. As we assumed before conducting the experiment, all
tasks (the control tasks) except task 4 were performed
similarly. Referring to the standard deviation, which is an
average of 16 seconds in case of the control tasks and 38
seconds in case of task 4, the difference in performance can
be easily identified. Thus, we conclude that the results of
this preliminary experiment are representative.</p>
      <p>When executing task 4, the test persons recognized the
redundancy of the three pumps and asked if they could use
another pump, which was intended.</p>
      <p>Discussion of the Results
All test persons were able to complete all tasks (with help
in case of task 4), which confirms hypothesis H1. Since all
of them needed help when executing task 4 and only during
task 4, the estimated 85,6% of hypothesis H2 was almost
exactly confirmed.</p>
      <p>For ah-hoc adaptation, the execution of task 4 took an
average of 117 seconds, for notification 125 seconds, and
for confirmation 89 seconds. Hence, hypothesis H3 cannot
be entirely confirmed, as ad-hoc adaptation outperformed
notification, but still confirmation outperformed both of the
other strategies.</p>
      <p>Threats to validity
Because all the test persons were only computer science
students, this may have had an effect on the result. But on
the other hand, those students were already familiar with
our previous work (without knowing the content of the
experiment), which could also be a good simulation of
domain knowledge. Nevertheless, the experiment needs to
be conducted (and will be) using production industry
domain experts. The most important threat to validity to
mention is the fact that this was only the pilot study for the
described experiment. This means that the sample was too
small and therefore has no real statistical evidence, but it
serves as a first indication as to whether an investigation
according our idea would make sense.</p>
      <p>CONCLUSION
When dealing with user interfaces in highly dynamic
environments, such as intelligent production environments,
there are special requirements. According to a shown
dissonance in user interface design, when being applied in
these environments, we have shown there is a special need
for compensating usage errors. This can be achieved by
systematically integrating adaptation strategies into the
model-driven development process. Since multiple
strategies exist, which provide different user experience, the
performance with respect to our demonstrator was
evaluated in a pilot study of a controlled experiment. First
results show that there are differences in the performance
and therefore some of our hypotheses could be verified.
ACKNOWLEDGMENTS
Our work as well as the GaBi project is funded in part by
the German Research Foundation (DFG).</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Weiser</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <article-title>The computer for the 21st century</article-title>
          .
          <source>Scientific American</source>
          ,
          <volume>265</volume>
          ,
          <issue>3</issue>
          (
          <year>1991</year>
          ),
          <fpage>94</fpage>
          -
          <lpage>104</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Breiner</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Görlich</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Maschino</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Meixner</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          <article-title>Towards automatically interfacing application services integrated in an automated model based user interface generation process</article-title>
          ,
          <source>Proc. of the 4th International Workshop on Model-Driven Development of Advanced User Interfaces (MDDAUI)</source>
          ,
          <source>CEUR Workshop Proceedings</source>
          Vol-
          <volume>439</volume>
          (
          <year>2009</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Breiner</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Görlich</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Maschino</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Meixner</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Zühlke</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          <article-title>Run-Time Adaptation of a Universal User Interface for Ambient Intelligent Production Environments</article-title>
          .
          <source>Proc. of the 13th International Conference on Human-Computer Interaction (HCII-09)</source>
          , LNCS Vol.
          <volume>5613</volume>
          (
          <year>2009</year>
          ),
          <fpage>663</fpage>
          -
          <lpage>672</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Breiner</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Görlich</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Maschino</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Meixner</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          <article-title>Automatische Generierung voll funktionsfähiger mobiler Bediensoftware aus Benutzungs- und Funktionsmodellen</article-title>
          .
          <source>Proc. of Informatik</source>
          , LNI Vol. P-
          <volume>154</volume>
          (
          <year>2009</year>
          ),
          <fpage>2210</fpage>
          -
          <lpage>2215</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Gould</surname>
            ,
            <given-names>J. D.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Lewis</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          <year>1985</year>
          .
          <article-title>Designing for usability: key principles and what designers think</article-title>
          .
          <source>Communications of the ACM</source>
          ,
          <volume>28</volume>
          ,
          <issue>3</issue>
          (
          <year>1985</year>
          ),
          <fpage>300</fpage>
          -
          <lpage>311</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Nielsen</surname>
          </string-name>
          , J. Ten Usability Heuristics. www.useit.com/papers/heuristic/heuristic_list.html.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Norcio</surname>
            ,
            <given-names>A. F.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Stanley</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Adaptive</surname>
          </string-name>
          Human - Computer
          <string-name>
            <surname>Interfaces</surname>
          </string-name>
          .
          <source>NRL Report 9148</source>
          , Naval Research Laboratory (
          <year>1988</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8. Mitchell, J. and
          <string-name>
            <surname>Shneiderman</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          <article-title>Dynamic versus static menus: an exploratory comparison</article-title>
          .
          <source>SIGCHI Bulletin</source>
          ,
          <volume>20</volume>
          ,
          <issue>4</issue>
          (
          <year>1989</year>
          ),
          <fpage>33</fpage>
          -
          <lpage>37</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Lee</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Johnson</surname>
            <given-names>T.</given-names>
          </string-name>
          <article-title>URCousin: Universal Remote Control User Interface</article-title>
          .
          <source>Proc. of the Human Interface Technologies Conference</source>
          (
          <year>2006</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Zuehlke</surname>
          </string-name>
          , D.:
          <article-title>SmartFactory - From Vision to Reality in Factory Technologies</article-title>
          .
          <source>Proc. of the 17th International Federation of Automatic Control (IFAC) World Congress</source>
          (
          <year>2008</year>
          ),
          <fpage>82</fpage>
          -
          <lpage>89</lpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>