<!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>
      <journal-title-group>
        <journal-title>Greenberg, S. &amp; Marwood, D. Real Time
Groupware as a Distributed System: Concurrency
Control and its Effect on the Interface, ACM Press</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>A classification for Supportive User Interfaces derived from Collaborative User Interfaces</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Carsten Wirth</string-name>
          <email>carsten.wirth@dai-labor.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Sahin Albayrak</string-name>
          <email>sahin.albayrak@dai-labor.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>TU-Berlin, DAI-Labor</institution>
          ,
          <addr-line>Sekretariat TEL 14, Ernst-Reuter-Platz 7, 10587 Berlin</addr-line>
        </aff>
      </contrib-group>
      <pub-date>
        <year>1994</year>
      </pub-date>
      <volume>207</volume>
      <abstract>
        <p>In this paper, we describe that the concept of supportive user interface is overlapping with aspects, which can be found in collaborative user interfaces and how this can help to classify and design supportive user interfaces accordingly.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;support</kwd>
        <kwd>collaboration</kwd>
        <kwd>classification</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>A promising approach towards extended user support is
seen in equipping the UI with corresponding supporting
functionality, which is developed and/or provided
simultaneously with the primarily functions. These
Supportive User Interfaces (SUI) can come in manifold
ways which makes comparisons and discussions difficult
because there is missing a classification as well as a clear
definition of SUI by now. In this paper we propose a
classification which is derived from Collaborative User
Interfaces (COUI) since as we will show many parallels
between SUI and COUI can be drawn.
In the following section the concepts of SUI and COUI are
presented along with examples of their manifestations. This
enables to elaborate several parallels of the both UI types in
the section thereafter. As a result a classification for SUI is
proposed and implications on design aspects for SUI are
described afterwards. The paper will finish with a
conclusion and outlook.</p>
      <p>RELATED WORK
In this section an overview of the UI types SUI and COUI
and their manifold manifestations is given. So that the
parallels between SUI and COUI can be elaborated on the
common understanding in the next section.</p>
      <p>
        Supportive User Interfaces
The concept of SUI is to provide the user with support
within complex systems such as ubiquitous systems by
means of making the user able to understand what is
happening in the system and how the system can be
controlled as desired with the numerous interaction
possibilities provided. The SUI can come in manifold ways
like self-explanatory user interfaces [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], process driven
user-guidance environments [
        <xref ref-type="bibr" rid="ref8">10</xref>
        ], extended device control
support [
        <xref ref-type="bibr" rid="ref7">9</xref>
        ], guidance for different modalities [7], support
by utilizing contextual awareness [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], and Meta-UI, which
can control and evaluate the states of the underlying system
[
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] and therefore can enable supportive functionality, and
assistance with visualization of system behavior [13]
amongst others.
      </p>
      <p>
        Collaborative User Interfaces
Collaborative User Interfaces are part of collaborative
environments and applications and are establishing a
human to human collaboration regarding the three aspects
communication, coordination and cooperation, which is
also known as 3C-Model [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. COUI can be found in diverse
application functional classes [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]; e.g. Message Systems,
Multi-User Editors, Group Decision Support Systems,
Electronic Meeting Rooms, Computer Conferencing,
Intelligent Agents, Workflow Management Systems and
more. Depending on the purpose COUI are supporting each
of the 3C differently [
        <xref ref-type="bibr" rid="ref10">12</xref>
        ].
      </p>
      <p>
        PARALLELS OF SUI AND COUI
At first glance SUI and COUI seem to have few similarities
based on their purpose. The purpose of the SUI is to help
the user to understand what is happening and give a better
control while the COUI focuses on supporting the user
while performing shared tasks with other users.. To show
the similarities of both a few examples are described
subsequently. Thereafter a conclusion for the presented
examples will be drawn in the following section.
Adaptation of a Workspace
A shared workspace is a common tool in Collaborative
Environments (CE) [
        <xref ref-type="bibr" rid="ref6">8</xref>
        ][6] but team members normally have
different preferences, different experiences, and often
different training thus making adaptations necessary [
        <xref ref-type="bibr" rid="ref9">11</xref>
        ]. If
a team member is changing the workspace layout in a way
which is affecting all of the team (e.g., removing an
important tool) the change has to be communicated and
explained to be excepted by the team or at least the team
has to be made aware of the change if a more hierarchical
role concept is used. Likewise in a self adapting system
(SAS) which is controlling a workspace environment
adaptations of the workspace (removing a tool because of
resolution changes) have to be communicated and
explained to the user.
      </p>
      <p>
        Simultaneous changes by the user and the system
Typically the work in CE takes place on some kind of
shared business objects [
        <xref ref-type="bibr" rid="ref9">11</xref>
        ] which demands coordination
of activities for conflict prevention or concurrency control
to resolve conflicts between participants simultaneous
operations [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. In a SAS the user is sharing interface objects
with the system. In example if the system decides to
optimize the content of a toolbar at the same time the user is
customizing it, this leads to a conflicting state. Either the
user can get her privileges to change the toolbar revoked on
short-term by the system to prevent conflicts or the system
has to resolve emerging conflicts with a suitable solution. A
simple one could be to overrule the users changes. Both the
SUI and the COUI have to provide the appropriate
coordination and concurrency control mechanism to
minimize user confusion and disturbance along with
suitable application control.
      </p>
      <p>Application Tutoring
In CE colleagues may serve as tutors for inexperienced
colleagues by guiding the first steps with tools provided by
the environment (e.g., mouse traces can be followed,
questions can be asked and are answered by others via chat
etc.) This cooperation towards a goal with a common
interest (in this case the same skill level for optimal
working results) can be transferred to SAS or SUI
respectively. The system and the user are sharing the
common interest that the user can operate the application at
best and therefore has to provide a SUI which enables
cooperation towards this goal between the user and the
system. To achieve this goal the SUI should be able to act
as tutor for the user.</p>
      <p>IMPLICATIONS FOR SUI FROM COUI
As shown by the examples in the section above system
behavior triggered by an agent (whether that agent is
automation or another human) establishes the same
requirements upon the user support. Furthermore the
aspects of communication, coordination and cooperation
(3C), which are used to characterize collaborative
applications can be found in the concept of SUI, with the
difference that for SUI the user is collaborating with the
system instead of a human.</p>
      <p>
        For collaboration environments different classifications
exist. In the context of SUI the 3C Model proposed by
Teufel et al. [
        <xref ref-type="bibr" rid="ref10">12</xref>
        ] can be utilized to classify SUI
respectively by weighting the support of each of the 3C
within the system separately. The system can be classified
by placing it in a triangle where each corner represents one
of these properties as shown in Figure 1 (exemplary
illustrated for [
        <xref ref-type="bibr" rid="ref7">9</xref>
        ][
        <xref ref-type="bibr" rid="ref2">2</xref>
        ][
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] and a fictive Automation Level
Configurator which allows the user to adjust the automation
level of adaptations with guidance to find the optimal
personal configuration).
The advantage of this classification is that both COUI and
SUI become comparable. Furthermore, this can help to find
design issues in SUIs. In a smart home for example the
steering of activities of multiple users which may depend on
shared device resources can be supported by SUI
functionality with the goal to optimize daily routines and to
avoid resource conflicts. This SUI with the focus on Device
Control Support can inherit aspects and mechanisms of
Workflow Management Systems because resource
allocation and scheduling are fundamental issues of them
[
        <xref ref-type="bibr" rid="ref3">3</xref>
        ].
      </p>
      <p>Another benefit from considering collaborative aspects in
SUI while designing interfaces is that parts of the UIs
supportive functionality can be replaced later on by real
collaborative functions if desired. Humans still tend to trust
humans more then machines especially when life or money
is involved. The configuration interface of an automated
heating regulation system in a smart home for example can
be either explained by the system itself or the user seeks the
guidance of a human supervisor by switching to the
collaborative mode. A fundamental issue of SUI amongst
others therefore should be to support the user to get
support, whether this support can be realized by the system
itself, another system or other users.</p>
      <p>CONCLUSION &amp; OUTLOOK
In this paper the parallels between SUI and COUI have
been shown; both share the aspects of communication,
coordination and cooperation and are establishing the same
requirements on the user support. Furthermore SUI can be
classified with the help of the 3C Model likewise COUI.
This classification can help to identify and to focus on
design issues for SUI by considering related COUI
implementations.</p>
      <p>One can assume that a quality level of SUI could be how
close the system is behaving in comparison to a real user
within a similar collaborative environment. The
specification of quality levels has to follow the clear
specification of SUI and is therefore a interesting topic for
future research.
7. Komatani, K.; Ueno, S.; Kawahara, T. &amp; Okuno,
H. G. Flexible guidance generation using user model
in spoken dialogue systems Proceedings of the 41st
Annual Meeting on Association for Computational
Linguistics - Volume 1, Association for
Computational Linguistics, 2003, 256-263</p>
      <p>C.
für
&amp;
die</p>
      <p>Mühlherr, T.</p>
      <p>Gruppenarbeit
13. Wachsmuth, S.; Wrede, S. &amp; Hanheide, M.</p>
      <p>Coordinating interactive vision behaviors for
cognitive assistance Computer Vision and Image
Understanding, 2007, 108, 135 – 149</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Bahr</surname>
            , G.; Balaban,
            <given-names>C.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Milanova</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          &amp;
          <string-name>
            <surname>Choe</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          <string-name>
            <surname>Stephanidis</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          (Ed.)
          <article-title>Nonverbally Smart User Interfaces: Postural and Facial Expression Data in Human Computer Interaction Universal Access in Human-Computer Interaction</article-title>
          . Ambient Interaction, Springer Berlin / Heidelberg,
          <year>2007</year>
          ,
          <volume>4555</volume>
          ,
          <fpage>740</fpage>
          -
          <lpage>749</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Coutaz</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <article-title>Meta-user interfaces for ambient spaces</article-title>
          .
          <source>Proceedings of TAMODIA'06</source>
          ,
          <year>2006</year>
          , Springer,
          <fpage>1</fpage>
          -
          <lpage>15</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Delias</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Doulamis</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Doulamis</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Matsatsinis</surname>
          </string-name>
          , N.; ,
          <source>Optimizing Resource Conflicts in Workflow Management Systems, Knowledge and Data Engineering</source>
          , IEEE Transactions on , vol.
          <volume>23</volume>
          , no.
          <issue>3</issue>
          , pp.
          <fpage>417</fpage>
          -
          <lpage>432</lpage>
          ,
          <year>March</year>
          2011
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Ellis</surname>
            ,
            <given-names>C. A.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Gibbs</surname>
            ,
            <given-names>S. J.</given-names>
          </string-name>
          &amp;
          <string-name>
            <surname>Rein</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          <article-title>Groupware: some issues and experiences Commun</article-title>
          . ACM, ACM,
          <year>1991</year>
          ,
          <volume>34</volume>
          ,
          <fpage>39</fpage>
          -
          <lpage>58</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Garc'ia Frey</surname>
          </string-name>
          , A.;
          <string-name>
            <surname>Calvary</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          &amp;
          <string-name>
            <surname>Dupuy-Chesa</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <article-title>Xplain: an editor for building self-explanatory user interfaces by model-driven engineering Proceedings of the 2nd ACM SIGCHI symposium on Engineering interactive computing systems</article-title>
          , ACM,
          <year>2010</year>
          ,
          <fpage>41</fpage>
          -
          <lpage>46</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          8.
          <string-name>
            <surname>Lauwers</surname>
            ,
            <given-names>J. C.</given-names>
          </string-name>
          &amp;
          <string-name>
            <surname>Lantz</surname>
            ,
            <given-names>K. A.</given-names>
          </string-name>
          <article-title>Collaboration awareness in support of collaboration transparency: requirements for the next generation of shared window systems CHI '90: Proceedings of the SIGCHI conference on Human factors in computing systems</article-title>
          , ACM,
          <year>1990</year>
          ,
          <fpage>303</fpage>
          -
          <lpage>311</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          9.
          <string-name>
            <surname>Seifried</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Haller</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Scott</surname>
          </string-name>
          , S. D.;
          <string-name>
            <surname>Perteneder</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Rendl</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Sakamoto</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          &amp;
          <string-name>
            <surname>Inami</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <article-title>CRISTAL: a collaborative home media and device controller based on a multi-touch display</article-title>
          <source>Proceedings of the ACM International Conference on Interactive Tabletops and Surfaces</source>
          , ACM,
          <year>2009</year>
          ,
          <fpage>33</fpage>
          -
          <lpage>40</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          10.
          <string-name>
            <surname>Sliski</surname>
            , T. J.; Billmers,
            <given-names>M. P.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Clarke</surname>
            ,
            <given-names>L. A.</given-names>
          </string-name>
          &amp;
          <string-name>
            <surname>Osterweil</surname>
            ,
            <given-names>L. J.</given-names>
          </string-name>
          <article-title>An architecture for flexible, evolvable process-driven user-guidance environments Proceedings of the 8th European software engineering conference held jointly with 9th ACM SIGSOFT international symposium on Foundations of software engineering</article-title>
          , ACM,
          <year>2001</year>
          ,
          <fpage>33</fpage>
          -
          <lpage>43</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          11.
          <string-name>
            <surname>Teege</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          <article-title>Users as Composers: Parts and Features as a Basis for Tailorability in CSCW Systems Computer Supported Cooperative Work (CSCW</article-title>
          ), Springer Netherlands,
          <year>2000</year>
          ,
          <volume>9</volume>
          ,
          <fpage>101</fpage>
          -
          <lpage>122</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          12.
          <string-name>
            <surname>Teufel</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ; Sauter,
          <string-name>
            <surname>Computerunterstützung</surname>
          </string-name>
          Addison-Wesley,
          <year>1995</year>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>