Brian Dys

Author: Brian Dys

  • Introduction to Information Architecture

    Introduction to Information Architecture 1

    How spaces and structures are designed in the information level.

    Purpose

    To empower designers in working in the Interaction Design stage.

    Outline

    • Intro
      • Information Architecture
        • Information, Data, Content
        • Definition
    • Main
      • Ontology
        • Definition
        • Framework
          • Nouns and Verbs
          • Controlled Vocabulary
      • Taxonomy
        • Definition
        • Facets
        • Types of Relationships
        • Diagrams
      • Choreography
        • Definition
        • Placemaking
    Glash Half Empty or Full?

    Content

    • Things that are present

    Data

    • Facts, Observations, Questions

    Information

    • Interpretations
    • Information is not Content

    Information Architecture

    The arrangement of the parts to make sense of the whole.

    Ontology

    The language that we use and the meaning that we intend.

    Nouns and Verbs

    Where to look for Nouns?

    • People – who are involved?
    • Features – what are the distinguishing aspects of the thing?
    • Paths – what do people look to accomplish?

    Controlled Vocabulary

    Parts of a Controlled Vocabulary

    • Approved Terms
    • Definition
    • Approved Synonyms
    • History of Term
    • Words We Don’t Say
    • Relationship Between Terms

    Exercise: Ontology Framework

    Digital Drop Game

    Taxonomy

    Definition

    • Classification, organization of things
    • Structure is a rhetorical tool
    • Taxonomy should depend on intentions (e.g., we want people to call us, we want people to refer other people)

    Facets

    In order to begin organizing, use facets:

    • Personality – what is it about?
    • Matter – what is it made or or not made of?
    • Energy – what are the related activities?
    • Space – where does it exist?
    • Time – when does it exist?

    Types of Relationships

    These are the common taxonomic patterns:

    • Equivalence – is the same as
    • Hierarchy – is a part of; is a type of
    • Sequential – is a predecessor or; is a successor of
    • Associative – is related to; is used with (not necessarily within the same family)

    5 Ways to Organize things:

    • Location
    • Alphabetical
    • Time
    • Category
    • Hierarchy

    Diagrams

    • Block Diagram (wire framing)
    • Association Diagram (mind mapping)
    • Swim Lane (shows different responsibilities within the same process)

    Choreography

    Definition

    • Steps user can or can not take across contexts and channels
    • Setting the rules for realizing intentions
    • Different UX in desktop and mobile
    • User access based on role
    • Different UX for novice user and expert user

    How does the language (ontology) change based on the context and channel?

    How does the structure (taxonomy) change based on the context and channel?

    Placemaking

    • Communicating intentions to users in a holistic manner
    • Considering the ecosystem to objects

    Deciding meaningful differences of taxonomy and ontology across contexts and channels

    The ability to zoom in and out of an experience to ensure you are serving your users

    IA is collaborative.

    IA is not a process, it is a result.

  • A new take on choreography!

  • List or Group?

    In finding the best term for separating a collection of items, which to use—list or group?

    Brain dump:

    List implies linearity, structure.

    Group implies randomness.

    —

    In generalizing the semantics of all items in a collection—in an HTML document—go for group.

    <ul class="list group">…</ul>

<div class="group">…</div>

<dl class="list group">…</dl>

    —

    It is important to note that the all HTML elements in the examples could express hierarchy by nesting other elements—but it is in the collection of items that list or group provides semantics.

    To recap:

    Use list for collection of items that implies order (yes, even for <ul>).

    Use group for collection of items that does not imply order.

  • It is, after all, a hypertext document.

  • Design Skills

    Information Architecture & Interaction Design

    • Human–Computer Interaction
    • Cognitive Psychology
    • Ubiquitous Computing
    • Urban Informatics
    • Urban Computing
    • Human Factors and Ergonomics
    • Social Computing
    • User Experience and Experience Design
    • Visual Representation
    • Industrial Design
    • Bifocal Display
    • Contextual Design
    • Mobile Computing
    • End–User Development
    • Philosophy of Interaction
    • Affective Computing
    • Requirements Engineering
    • Context–Aware Computing
    • Usability Evaluation
    • Activity Theory
    • Disruptive Innovation
    • Open User Innovation
    • Visual Aesthetics
    • Tactile Interaction
    • Somaesthetics
    • Card Sorting
    • Wearable Computing
    • Social–Technical System Design
    • Semiotics
    • Aesthetic Computing
    • Computer Supported Cooperative Work
    • Phenomenology
    • Formal Methods
    • Personas
    • Ethnography
    • 3D User Interfaces
    • Action Research
    • Experimental Methods in Human–Computer Interaction
    • Data Visualization for Human Perception
    • Human–Robot Interaction
    • User Interface Design Adaptation
    • Emotion and Website Design
    • Human–Data Interaction
    • Design for All
    • Research through Design
    • Affordances
    • Semi–Structured Qualitative Studies

    References

    The Encyclopedia of Human-Computer Interaction, 2nd Ed.

  • Infographic: The Case for Universal Design

    https://www.section508.gov/blog/infographic-the-case-for-universal-design

  • const and let—learning web development.

  • IBM Plex fonts in the open!

  • Information Architecture Resources

    http://web.archive.org/web/20070416110618/http://www.cmsreview.com:80/IA/glossary.html

    http://web.archive.org/web/20060831192727/http://www.cmscalendar.com:80/ia-glossary.html?term=Taxonomy

    http://web.archive.org/web/20070408112138/http://www.bobgoodman.net:80/main/glossary.html

    http://web.archive.org/web/20070220214703/http://www.theusabilitycompany.com:80/resources/glossary.html

    http://web.archive.org/web/20070417104203/http://www.iawiki.net/action=browse&id=GlossaryOfTerms&oldid=IAGlossary

    http://web.archive.org/web/20070415101307/http://www.jnd.org:80/dn.mss/affordance_conventi.html

    http://web.archive.org/web/20070427045700/http://www.usabilityfirst.com:80/glossary/main.cgi

    http://web.archive.org/web/20070501121141/http://www.iawiki.net:80/DeliverablesAndArtifacts

    https://docs.google.com/spreadsheets/d/1h2hyR1S9v_Pgv64jmNexebAIIXGQqdB58mI6TDSDzng/edit#gid=0

    https://docs.google.com/spreadsheets/d/1dQMHXzwG9q3eqX8hdVKKjDCIQux7pjZM9um4lEB3yss/edit#gid=0

    https://www.ischool.utexas.edu/~i385e/readings/Warner-aTaxonomyPrimer.html

  • Breadth and Depth

    We need to incorporate the possibility of moving up the employment level by breadth—encompassing the other disciplines and depth—by fulfilling the Work Efficiency Responsibility needed for the next level.

    We need to fill-in the details—criteria also—for moving across and moving up. How can these be measurable?