<?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('Algebraic Semiotics');
?>
<h1>Algebraic Semiotics</h1>

<p>Algebraic semiotics is a formalism for describing signs, systems of signs,
and mappings between <a class="term" href="glossary.php?term=sign_system" title="Look up: sign system" onclick="show_term('sign_system', event.screenX, event.screenY); return false;">sign systems</a>. It is useful not
only for <a class="term" href="glossary.php?term=analytic" title="Look up: analytic" onclick="show_term('analytic', event.screenX, event.screenY); return false;">analysis</a>&#8212;the effort to describing existing
signs, with which classical semiotics is primarily concerned&#8212;but more
important, for <a class="term" href="glossary.php?term=synthetic" title="Look up: synthetic" onclick="show_term('synthetic', event.screenX, event.screenY); return false;">synthesis</a>&#8212;the systematic design of
new signs.</p>

<p>From the standpoint of algebraic semiotics, a user interface is a sign,
albeit an interactive and highly complex one made up of many constituent signs
individually representing concepts that were used by the designers and
hopefully are salient to users. Algebraic semiotics aims to provide designers
with a formal, structured way to compose, decompose, and compare possible (and
actual) interfaces, and hopefully in the end, to help build better ones.</p>

<a name="zoo"></a><h2>The Semiotic Zoo</h2>

<p>To understand how to create a good design, it is useful to know what can
lead to a poor one. This insight is the motivation behind the
<a href="http://www-cse.ucsd.edu/users/goguen/zoo/">UC San Diego Semiotic
Zoo</a>. Take a look now at the Zoo's
<a href="http://www-cse.ucsd.edu/users/goguen/zoo/intro1.html">Semiotic
Introduction</a>.</p>

<p>In the introduction, you may have noticed how algebraic semiotics draws on
classical semiotics for the concepts of <a class="term" href="glossary.php?term=sign" title="Look up: sign" onclick="show_term('sign', event.screenX, event.screenY); return false;">sign</a> and <a class="term" href="glossary.php?term=sign_system" title="Look up: sign system" onclick="show_term('sign_system', event.screenX, event.screenY); return false;">sign system</a>,
though the terms are used in a more precise and specific way. This only hints
at the richness of algebraic semiotic descriptions; there is more to come.</p>

<p>Some important things to remember from the semiotic introduction are the
notions of <a class="term" href="glossary.php?term=source_sign" title="Look up: source sign" onclick="show_term('source_sign', event.screenX, event.screenY); return false;">source sign</a> and <a class="term" href="glossary.php?term=display_sign" title="Look up: display sign" onclick="show_term('display_sign', event.screenX, event.screenY); return false;">display sign</a>, and the inferred
mapping between them. The source sign is the concept the designer had in mind,
and the display sign is the way he or she chose to represent it in the
interface. Algebraic semiotics draws attention to the mapping, called a
<a class="term" href="glossary.php?term=semiotic_morphism" title="Look up: semiotic morphism" onclick="show_term('semiotic_morphism', event.screenX, event.screenY); return false;">semiotic morphism</a>; from this perspective, properties of this mapping
affect how easily the user can understand the underlying design and how to
interpret and use the interface.</p>

<p>Two of the Zoo's exhibits relate to user interface design more directly than
the others: <a href="http://www-cse.ucsd.edu/users/goguen/zoo/unix.html">Unix
Command Notation Stalks a Toy Algebra</a> and
<a href="http://www-cse.ucsd.edu/users/goguen/zoo/stack.html">One Slightly
Confused Applet</a>. Take a look at these exhibits and their accompanying
explanations.</p>

<p>The explanations for the exhibits should give a basic idea what an algebraic
semiotic analysis looks like: considering the <a class="term" href="glossary.php?term=display_sign" title="Look up: display sign" onclick="show_term('display_sign', event.screenX, event.screenY); return false;">display signs</a>, inferring the <a class="term" href="glossary.php?term=source_sign" title="Look up: source sign" onclick="show_term('source_sign', event.screenX, event.screenY); return false;">source signs</a>, identifying
the <a class="term" href="glossary.php?term=semiotic_morphism" title="Look up: semiotic morphism" onclick="show_term('semiotic_morphism', event.screenX, event.screenY); return false;">semiotic morphism</a> that maps from source to display, thinking about
what that morphism preserves, and especially whether it preserves the most
important structure in the <a class="term" href="glossary.php?term=source_space" title="Look up: source space" onclick="show_term('source_space', event.screenX, event.screenY); return false;">source space</a>. These are simple examples, of
course; in a real-life <a class="term" href="glossary.php?term=analytic" title="Look up: analytic" onclick="show_term('analytic', event.screenX, event.screenY); return false;">analysis</a> (or <a class="term" href="glossary.php?term=synthetic" title="Look up: synthetic" onclick="show_term('synthetic', event.screenX, event.screenY); return false;">synthesis</a>, for that matter), it would be important to
spend more time thinking about the goals and social context of the interface
and its users.</p>

<p>The
<a href="http://www-cse.ucsd.edu/users/goguen/zoo/stack-exp.html">Explanation
for a Slightly Confused Applet</a> introduces another concept in algebraic
semiotics: <a class="term" href="glossary.php?term=level" title="Look up: level" onclick="show_term('level', event.screenX, event.screenY); return false;">level</a>. We said before that algebraic semiotics views
interfaces as complex signs made up of other signs; another way to describe this
is to say an interface is a high-level sign composed of lower-level signs such
as windows and buttons.</p>

<p>Take some time to explore the rest of the
<a href="http://www-cse.ucsd.edu/users/goguen/zoo/">Semiotic Zoo</a>;
although the other examples aren't user interface design examples, they are
relatively simple examples of algebraic semiotics in action.</p>

<a name="morphisms"></a><h2>Semiotic morphisms</h2>

<p>The main ideas in algebraic semiotics are precise notions of sign systems and
the mappings between them. The Semiotic Zoo should give a basic grasp of these,
but the document
<a href="http://www-cse.ucsd.edu/users/goguen/papers/sm/smm.html">Semiotic
Morphisms</a> fleshes them out in more detail.</p>

<p>Take special note of one point in the <a href=
"http://www-cse.ucsd.edu/users/goguen/papers/sm/node1.html">introduction</a>
about algebraic semiotics: although its ideas have a precise mathematical
formulation, they can be used informally as well. In user interface design it
will generally be inadvisable&#8212;even <em>infeasible</em>&#8212;to work out
the entire mathematical structure of the source and display systems, let alone
the morphism between them. In practice an informal approach can yield insights
without the unnecessary detail of a fully developed theory; nevertheless, an
understanding of how such a theory would look is useful even in taking an
informal approach. An excellent way to see how the formalism works is to see
it applied to some small examples, which is what the
<a href="http://www-cse.ucsd.edu/users/goguen/papers/sm/smm.html">Semiotic
Morphisms</a> document does.</p>

<p>To describe in more depth the precise notions in algebraic semiotics, the
paper introduces several key terms. <a class="term" href="glossary.php?term=sort" title="Look up: sort" onclick="show_term('sort', event.screenX, event.screenY); return false;">Sorts</a> are categories of
signs; for example, in a user interface, there might be a sort "button" of
which all the buttons are instances. There might be <a class="term" href="glossary.php?term=subsort" title="Look up: subsort" onclick="show_term('subsort', event.screenX, event.screenY); return false;">subsorts</a> of the button sort, such as mode-toggle buttons and action buttons. Signs
of a certain sort are generally made up of signs at lower-level sorts; <a class="term" href="glossary.php?term=constructor" title="Look up: constructor" onclick="show_term('constructor', event.screenX, event.screenY); return false;">constructors</a> specify these relationships. For example, a
button might be constructed from a grey rectangle and an icon or a text label.
<a class="term" href="glossary.php?term=axiom" title="Look up: axiom" onclick="show_term('axiom', event.screenX, event.screenY); return false;">Axioms</a> limit such constructions. There might be an axiom
that says the text label on a button is never longer than a few words.</p>

<p>The notion of <a class="term" href="glossary.php?term=priority" title="Look up: priority" onclick="show_term('priority', event.screenX, event.screenY); return false;">priority</a> is of critical importance when applying
algebraic semiotics to user interface design, primarily because it comes
into play when appraising the <a class="term" href="glossary.php?term=quality" title="Look up: quality" onclick="show_term('quality', event.screenX, event.screenY); return false;">quality</a> of a <a class="term" href="glossary.php?term=semiotic_morphism" title="Look up: semiotic morphism" onclick="show_term('semiotic_morphism', event.screenX, event.screenY); return false;">semiotic morphism</a>.
Priority is an ordering on constructors, generally specifying which signs of a
given sort are more important than others. A morphism that preserves in the <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> the priority in the <a class="term" href="glossary.php?term=source_space" title="Look up: source space" onclick="show_term('source_space', event.screenX, event.screenY); return false;">source space</a> is clearly better than
one that does not; for example, especially urgent or important messages should
be the ones that most demand attention. An interface that allows such messages
to appear subtly in occluded windows is likely to engender much
frustration&#8212;or worse, depending on the nature of the messages and
the purpose of the system.</p>

<a name="reading"></a><h2>Further reading</h2>

<p>Our aim here is only to give a general introduction to classical and
algebraic semiotics as they relate to user interface design. Far more
has been written about algebraic semiotics, much of which is concerned
to some extent with user interface design, since that is one of the
motivating reasons for its inception.</p>

<p>A position paper on
<a href="http://www-cse.ucsd.edu/users/goguen/papers/sm/vzln.html">Information
Visualization and Semiotic Morphisms</a> by Joseph Goguen and Fox Harrell treats
the topic of visual representation, which is of course an integral part of user
interface design, using algebraic semiotics. The examples in section 3 all
involve user interfaces: a code browser that reflects how recently code has been
edited, a tool for exploring a database of movies, and the various
representations file-system structure available in Macintosh's <em>Finder</em>.
The paper also contains a brief but lucid introduction to algebraic semiotics
and its application to design generally.</p>

<p>For the more deeply interested reader, Goguen's
"An Introduction to Algebraic Semiotics, with Applications to User Interface
Design" (<a href="http://www-cse.ucsd.edu/users/goguen/pps/as.ps">PS</a>,
<a href="http://www-cse.ucsd.edu/users/goguen/ps/as.pdf">PDF</a>)
provides a thorough treatment of both the theoretical and practical
aspects of algebraic semiotics. It contains detailed explanation of the
mathematical formalism as well as numerous examples. It also introduces
conceptual blending as a special case of semiotic morphisms.</p>

<p>Goguen's more recent paper, "Semiotic Morphisms, Representations and Blending
for User Interface Design"
(<a href="http://www-cse.ucsd.edu/users/goguen/pps/uid.ps">PS</a>)
contains an in-depth analysis of the familiar user-interface elements,
windows and scrollbars. This paper uses the language BOBJ for formal
notation, but it explains the conventions of BOBJ for readers who are
unfamiliar with it.</p>

<!-- frontier

"what makes one such representation better than another
always boils down to values which have a social basis."

The following semiotic method for synthesis is recommended:

 1. determine the highest priority constructors and selectors for the top level
 sort;
 2. design a target sign system to display this information in the required
 medium;
 3. design a morphism to preserve the selected structure and omit the rest;
 4. if more information is desired, then consider other levels with their
    highest priority constructors and selectors.

Quite likely you will want to iterate these steps, interleaved with some user
testing (initially perhaps only with yourself or other design team members).
Keep things as simple as you can, and remember that the semiotic structure of
the source space may be quite different from its implementation structure, and
that the point of an overview of a large dataset is to delete most of the
information while preserving enough to survey the key points; principle F/C is
very relevant here (see below). It is very likely that some experimentation
with the output will be required to achieve good results; user trials,
interviews, etc. are recommended. It may also be a good idea to create more
than one initial design, and then to iterate through these steps for all
designs simultaneously, using the quality orderings to compare them, and feed
the most successful ideas back into the next iteration. Eventually of course
you should eliminate all but one design.

The following four principles summarize some significant contributions that
algebraic semiotics can make to the design process:

 1. Sort preservation: The most important sorts should be preserved, where
    their importance is given by the level ordering.
 2. Constructor preservation: The most important constructors should be
    preserved, where their importance is given by the priority orderings.
 3. Axiom preservation: The most important axioms should be preserved.
 4. F/C: When something must be sacrificed, form has preference over content
    for preservation.

Note that the first three principles correspond exactly to three main elements
of semiotic spaces. These principles can be seen as refining step 3. of the
semiotic method for design described above. Determining which axioms are most
important can be difficult, because it is possible that some consequences of
the given axioms are more important than the axioms themselves; moreover, it is
possible to confuse unimportant properties of the way data in the source space
is presented with important instrinstic properties of what the data means. (The
ordering in principle 1. can be constructed as the lexicographic product of the
"preserves at least as much as" orderings on sorts, indexed by levels; the
ordering for principle 2. is similar, but more complex.)
The following outlines a recommended semiotic method for analysis of an
interface:

 1. identify as much as is relevant of the social context of the interface and
    its system, including the goal of the interface, and the nature of the user
    community;
 2. identify key properties of the source and target sign systems, e.g. the
    major affordances of the source objects;
 3. identify the semiotic morphism involved;
 4. think about what is preserved by the morphism;
 5. consider whether elements of the display are symbolic, indexical, iconic,
    or diagrammatic iconic, and/or
 6. involve significant sensory-motor (image) schemas, and/or
 7. involve some blending.

-->
<?php
/* Print page footer */
print_page_footer();
?>

