<?php
/*
  Copyright (C) 2003, 2004 Dana Dahlstrom
  (http://www.cs.ucsd.edu/users/ddahlstr/) and Vinu Somayaji
  (http://www.cs.ucsd.edu/users/vsomayaj/).

  This file is part of Semiotics and UID.

  Semiotics and UID is free software; you can redistribute it and/or modify
  it under the terms of the GNU General Public License as published by
  the Free Software Foundation; either version 2 of the License, or
  (at your option) any later version.

  Semiotics and UID is distributed in the hope that it will be useful,
  but WITHOUT ANY WARRANTY; without even the implied warranty of
  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  GNU General Public License for more details.

  You should have received a copy of the GNU General Public License
  along with Semiotics and UID; if not, write to the Free Software
  Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
*/

/* Include common functions */
require('common.php');

/* Print page header */
print_page_header('Introduction');
?>
<h1>Introduction</h1>

<p>A user interface can be described as anything that enables us to perform a
(usually practical) task. In that sense, almost everything can be considered a
user interface: a coffee pot is a user interface that enables us to make coffee,
a door is a user interface that enables us to enter and exit a room, ... even a
sidewalk is a user interface, enabling us to walk from one point to another.</p>

<p>The complexity of a user interface generally increases with the complexity of
the task it is facilitating. It is therefore understandable that the user
interfaces for computer systems&#8212;which offer us the ability to perform a
multitude of complex operations, from managing an MP3 collection to running
scientific simulations&#8212;can be very complex. This makes the job of the user
interface designer very difficult. How does one design an interface to all this
functionality, while at the same time keeping it <em>usable</em>?</p>

<p>Adding to this difficulty is the fact that computers provide a visual
environment, and there is an increasingly visual nature to computer interfaces.
Specifying all the interactions mediated by these <a class="term" href="glossary.php?term=GUI" title="Look up: GUI" onclick="show_term('GUI', event.screenX, event.screenY); return false;">GUIs</a>&#8212;a
necessity for any comprehensive design document&#8212;is a near-to-impossible
feat when compared to doing the same for text-only command-line interfaces (due
to both inadequate theories, and the creativity and complexity inherent in
graphical media). But wait ... it gets worse.</p>

<p>Consider the future trends in computing [<a
href="references.php#ref4">4</a>]:</p>

<ul>
  <li><a class="term" href="glossary.php?term=convergence" title="Look up: convergence" onclick="show_term('convergence', event.screenX, event.screenY); return false;">convergence</a> (the merging of computers and communications);</li>
  <li><a class="term" href="glossary.php?term=ubiquity" title="Look up: ubiquity" onclick="show_term('ubiquity', event.screenX, event.screenY); return false;">ubiquity</a> (computers will be <em>everywhere</em>); and</li>
  <li>the illusion of social intelligence, such as in <a class="term" href="glossary.php?term=affective_computing" title="Look up: affective computing" onclick="show_term('affective_computing', event.screenX, event.screenY); return false;">affective computing</a>
  (computers can sense user emotions, and will appear to have emotions).</li>
</ul>

<p>Eventually, we may get to the point of <a class="term" href="glossary.php?term=autonomic_computing" title="Look up: autonomic computing" onclick="show_term('autonomic_computing', event.screenX, event.screenY); return false;">autonomic computing</a>, when
computers are self-repairing, autonomous,
<a class="term" href="glossary.php?term=transparency" title="Look up: transparency" onclick="show_term('transparency', event.screenX, event.screenY); return false;">transparent</a>, and
<a class="term" href="glossary.php?term=ubiquitous_computing" title="Look up: ubiquitous computing" onclick="show_term('ubiquitous_computing', event.screenX, event.screenY); return false;">ubiquitious</a>. As these trends become part of
our here and now, currently available user interfaces will no longer suffice. If
user interface designers suggest that <a class="term" href="glossary.php?term=GUI" title="Look up: GUI" onclick="show_term('GUI', event.screenX, event.screenY); return false;">GUIs</a> have made their
lives tough, how will they react when virtual or augmented reality interfaces
replace the standard keyboard, mouse, and monitor?</p>

<p><a class="term" href="glossary.php?term=user_interface_design" title="Look up: user interface design" onclick="show_term('user_interface_design', event.screenX, event.screenY); return false;">User interface design</a> (<a class="term" href="glossary.php?term=UID" title="Look up: UID" onclick="show_term('UID', event.screenX, event.screenY); return false;">UID</a>) for
computer systems is not a simple business, but neither can it be swept under the
rug. Even if a system meets all its performance and functional requirements, a
poorly designed user interface can result in its being completely useless. It is
therefore important to consider what makes a user interface "good", and what
issues are involved in designing such an interface.</p>

<a name="goal"></a><h2>The goal of UID</h2>

<p>The ultimate goal of <a class="term" href="glossary.php?term=UID" title="Look up: UID" onclick="show_term('UID', event.screenX, event.screenY); return false;">UID</a> is <a class="term" href="glossary.php?term=transparency" title="Look up: transparency" onclick="show_term('transparency', event.screenX, event.screenY); return false;">transparency</a>. This occurs when the
interface becomes "invisible", and the user can focus on performing the task at
hand. For example, to many computer users, the mouse is a transparent interface
to the pointer on the screen: they can think in terms of moving the <em>pointer
</em>, rather than moving the <em>mouse</em> to move the pointer.</p>

<p>[<a href="references.php#ref6">6</a>] provides five "goals" of <a class="term" href="glossary.php?term=UID" title="Look up: UID" onclick="show_term('UID', event.screenX, event.screenY); return false;">UID</a>,
which can instead be thought of as "gauges" of <a class="term" href="glossary.php?term=transparency" title="Look up: transparency" onclick="show_term('transparency', event.screenX, event.screenY); return false;">transparency</a>. These are:
</p>

<ol>
  <li>time to learn;</li>
  <li>speed of performance;</li>
  <li>rate of error by users;</li>
  <li>retention over time; and</li>
  <li>subjective satisfaction.</li>
</ol>

<p>An interface that performs better as measured by these gauges can be said to
be "more <a class="term" href="glossary.php?term=transparency" title="Look up: transparency" onclick="show_term('transparency', event.screenX, event.screenY); return false;">transparent</a>". (Especially noteworthy among
the gauges is the rate of error by users. Transparency breaks down when the
interface breaks down, and this very commonly occurs when faced with unexpected
user behavior&#8212;an additional incentive for user interface designers to
gracefully handle all error conditions.)</p>

<a name="issues"></a><h2>Issues in UID</h2>

<p>According to [<a href="references.php#ref4">4</a>] there are four levels to
<a class="term" href="glossary.php?term=UID" title="Look up: UID" onclick="show_term('UID', event.screenX, event.screenY); return false;">UID</a> issues:</p>

<ol>
  <li>technology;</li>
  <li><a class="term" href="glossary.php?term=ergonomics" title="Look up: ergonomics" onclick="show_term('ergonomics', event.screenX, event.screenY); return false;">ergonomics</a> (concerns the relationship between people and their
  working environment);</li>
  <li><a class="term" href="glossary.php?term=cognitive_psychology" title="Look up: cognitive psychology" onclick="show_term('cognitive_psychology', event.screenX, event.screenY); return false;">cognitive psychology</a> (concerns how the human mind processes
  information); and</li>
  <li>social, cultural, and organizational issues.</li>
</ol>

<p>Though often ignored in actual <a class="term" href="glossary.php?term=UID" title="Look up: UID" onclick="show_term('UID', event.screenX, event.screenY); return false;">UID</a>, there is now widespread
recognition of the significance of social issues (the first three issues are
well studied and understood, and will not be discussed further here). Social
issues (i.e., user values) are more difficult to incorporate in design (by
definition, they require user involvement), but are as (if not more) important.
Data from "software economics" reveals that about 50% of the cost of error
correction for large projects comes from errors in requirements, and most
serious problems with requirements are grounded in social issues [<a href=
"references.php#ref4">4</a>].</p>

<p>The most obvious way of incorporating social issues in a user interface is
<a class="term" href="glossary.php?term=iterative_design" title="Look up: iterative design" onclick="show_term('iterative_design', event.screenX, event.screenY); return false;">iterative design</a>. This involves designing in stages, with user testing
and evaluation following each stage. Unfortunately, this is time consuming, and
therefore expensive.</p>

<p>A better solution derives from the field of <a class="term" href="glossary.php?term=ethnomethodology" title="Look up: ethnomethodology" onclick="show_term('ethnomethodology', event.screenX, event.screenY); return false;">ethnomethodology</a>, which
among other things, deals with discovering the values of a social group. What if
user interface designers could use the techniques of ethnomethodology to learn
the values of their users? They would still require a way to incorporate those
values in their design. The answer ... <a class="term" href="glossary.php?term=semiotics" title="Look up: semiotics" onclick="show_term('semiotics', event.screenX, event.screenY); return false;">semiotics</a>.</p>

<a name="semiotics"></a><h2>The role of semiotics in UID</h2>

<p><a class="term" href="glossary.php?term=semiotics" title="Look up: semiotics" onclick="show_term('semiotics', event.screenX, event.screenY); return false;">Semiotics</a> is the study of <a class="term" href="glossary.php?term=sign" title="Look up: sign" onclick="show_term('sign', event.screenX, event.screenY); return false;">signs</a>.
Here, signs are not just the simple, physical things commonly called "signs"
(these will be henceforth referred to as "<a class="term" href="glossary.php?term=token" title="Look up: token" onclick="show_term('token', event.screenX, event.screenY); return false;">tokens</a>"). Instead,
a sign is <em>anything</em> that mediates meaning; this can include words,
images, sounds, and even gestures. Signs can be complex combinations of lower
level signs; for example, a book is a complex sign that is a combination of
paragraphs, which in turn are combinations of sentences, and so on. The term
"semiotics" was coined by the nineteenth-century American logician Charles
Sanders <a class="term" href="glossary.php?term=Peirce" title="Look up: Peirce" onclick="show_term('Peirce', event.screenX, event.screenY); return false;">Peirce</a> (pronounced "purse"), who also introduced several of its
basic ideas. Most importantly, a sign's meaning is dependent on context: the
same sign can mean something else to somebody else. Peirce also described a
system of classifying signs by how they convey meaning. The other significant
contributor to semiotics was the Swiss linguist Ferdinand de <a class="term" href="glossary.php?term=Saussure" title="Look up: Saussure" onclick="show_term('Saussure', event.screenX, event.screenY); return false;">Saussure</a>,
whose key insight was that signs come in systems, and should therefore be
studied as such.</p>

<p>A user interface is a complex, structured <a class="term" href="glossary.php?term=sign" title="Look up: sign" onclick="show_term('sign', event.screenX, event.screenY); return false;">sign</a>. The <a class="term" href="glossary.php?term=semiotics" title="Look up: semiotics" onclick="show_term('semiotics', event.screenX, event.screenY); return false;">semiotics</a>
of <a class="term" href="glossary.php?term=Peirce" title="Look up: Peirce" onclick="show_term('Peirce', event.screenX, event.screenY); return false;">Peirce</a> and <a class="term" href="glossary.php?term=Saussure" title="Look up: Saussure" onclick="show_term('Saussure', event.screenX, event.screenY); return false;">Saussure</a>
(<a class="term" href="glossary.php?term=classical_semiotics" title="Look up: classical semiotics" onclick="show_term('classical_semiotics', event.screenX, event.screenY); return false;">"classical" semiotics</a> from this point on)
provides a theory for deducing how a user community might interpret such a sign,
but by itself, is insufficient for <a class="term" href="glossary.php?term=UID" title="Look up: UID" onclick="show_term('UID', event.screenX, event.screenY); return false;">UID</a>. The "D" in UID stands for design,
which refers to the process of creating a configurations of signs that will
enable a user to perform some task. We therefore need a way to not only analyze
signs, but to synthesize them. Another drawback of classical semiotics lies in
its somewhat Platonistic beliefs, suggesting that signs and their meanings can
exist without people (i.e., without the social element). To correctly utilize
semiotics for UID, we require a <a class="term" href="glossary.php?term=synthetic" title="Look up: synthetic" onclick="show_term('synthetic', event.screenX, event.screenY); return false;">synthetic</a>, socially-situated semiotics.
</p>

<p><a class="term" href="glossary.php?term=algebraic_semiotics" title="Look up: algebraic semiotics" onclick="show_term('algebraic_semiotics', event.screenX, event.screenY); return false;">Algebraic semiotics</a> is a new field, drawing
on the most important concepts of <a class="term" href="glossary.php?term=classical_semiotics" title="Look up: classical semiotics" onclick="show_term('classical_semiotics', event.screenX, event.screenY); return false;">classical semiotics</a>, and offering
solutions for its failings. It is a precise formalism of <a class="term" href="glossary.php?term=sign_systems" title="Look up: sign systems" onclick="show_term('sign_systems', event.screenX, event.screenY); return false;">sign systems</a>,
providing a way to analyze <a class="term" href="glossary.php?term=sign" title="Look up: sign" onclick="show_term('sign', event.screenX, event.screenY); return false;">signs</a>, as well as to synthesize
them. Once a task has been investigated with respect to the user community,
algebraic semiotics simply requires that you determine the <a class="term" href="glossary.php?term=source_system" title="Look up: source system" onclick="show_term('source_system', event.screenX, event.screenY); return false;">source system</a>,
and map to a <a class="term" href="glossary.php?term=design_space" title="Look up: design space" onclick="show_term('design_space', event.screenX, event.screenY); return false;">design space</a>. Using <a class="term" href="glossary.php?term=priority" title="Look up: priority" onclick="show_term('priority', event.screenX, event.screenY); return false;">priorities</a> and
orderings with this mapping ensures that the user values are retained. This
formalized process allows the prediction of measurements for the gauges of
<a class="term" href="glossary.php?term=transparency" title="Look up: transparency" onclick="show_term('transparency', event.screenX, event.screenY); return false;">transparency</a> mentioned earlier, and consequently allows determining the
optimal choice from competing designs.</p>

<p>As a form of disclaimer, a thorough understanding of
<a class="term" href="glossary.php?term=classical_semiotics" title="Look up: classical semiotics" onclick="show_term('classical_semiotics', event.screenX, event.screenY); return false;">classical</a> and <a class="term" href="glossary.php?term=algebraic_semiotics" title="Look up: algebraic semiotics" onclick="show_term('algebraic_semiotics', event.screenX, event.screenY); return false;">algebraic semiotics</a> does
not <em>guarantee</em> that you will design a perfect interface. Oftentimes,
there is no "perfect" interface. As the linguist Edwin Sapir liked to say, "All
systems leak." Basically, no formalism is flawless, but there is still use in
writing it down. Some model is better than no model at all, and in this case you
are provided a way of incorporating user values into the design of an interface,
which is otherwise a very difficult task. It's no utopia, but it <em>is</em> a
step forward.</p>

<p>The remaining pages of this site discuss
<a class="term" href="glossary.php?term=classical_semiotics" title="Look up: classical semiotics" onclick="show_term('classical_semiotics', event.screenX, event.screenY); return false;">classical</a> and <a class="term" href="glossary.php?term=algebraic_semiotics" title="Look up: algebraic semiotics" onclick="show_term('algebraic_semiotics', event.screenX, event.screenY); return false;">algebraic semiotics</a> in
more detail. The examples given are primarily related to user interfaces,
particularly those of personal computers and their software. This should not be
construed to mean that classical, or even algebraic, semiotics, is in any way
limited to such applications. Quite to the contrary, semiotic theory emerged
from philosophy and linguistics, and has been most broadly applied to the arts
and social sciences. The explicit use of <a class="term" href="glossary.php?term=semiotics" title="Look up: semiotics" onclick="show_term('semiotics', event.screenX, event.screenY); return false;">semiotics</a> in <a class="term" href="glossary.php?term=UID" title="Look up: UID" onclick="show_term('UID', event.screenX, event.screenY); return false;">UID</a> is a
comparitively recent development and is not yet widespread.</p>
<?php
/* Print page footer */
print_page_footer();
?>




