Home | About InfoDesign | Jobs | Resources | Organizations | InfoDesign Archive | Books | Firms | People
RESOURCES OVERVIEWInfo Design / Arch Deliverable Schemas |
Peter J. Bogaards - July 13, 2004
Current practice shows that much discussion is devoted to concepts, theories, methods, and techniques of User Experience Design in general and Information Design/Information Architecture (ID/A) in specific. Unfortunately, these discussions have not been productive enough so far vis-a-vis a deep understanding of ID/A activities and their results. A focus on the documents ID/As deliver and the building blocks ('elements') they consist of seems necessary.
This document contains a set of ID/A deliverables (a.k.a. documents), which have been derived from various internal and external sources. Be aware, that this is a rather premature attempt to provide more consensus within the ID/A community on the structure, content, and presentation of the documents.
Modeling (ID/A) documents, their flexibility, scalability, and extensibility will increase and will contribute to the integration process of interdisciplinary projects.
[1-n] one-to-many; CW: Christina Wodtke; DC.Dublin Core; m: mandatory; o: optional; syn: synonym;
Conceptual Model (CW)
Content Map
Content Inventory (CW)
Functional Requirements
Decision Table (CW)
Task Analysis (CW)
Page Schematic
Preliminary Style Guide
Site Map
Use Case
Use Scenario
User Experience Outline
User Flow (CW)
User Personae
User Profile
Sources
Definition: "The conceptual model is the message the designer sends to the user about how the product works" - CW [syn: User Model, Concept Map, Concept Model]
Background: The conceptual model is intended to reflect users' understanding of the problem domain, often in the form of conceptual objects and the relationships between them.
Elements: DC.Title (m), DC.Creator (m), DC.Contributor (o), DC.Date.Created (m), DC.Date.Modified (m), DC.Language (m), DC.Subject (m), DC.Description.TableofContents (m), DC.Description.Abstract (o), DC.Relation.References (m),
TypographicalConventions (m), KeyToSymbols (m), ChangeLog (m), GeneralOverview (m), PageNumber (o) [1-n], Glossary (o), Index (o)
LevelOneConcept (m) [1-n], LevelTwoConcept (o) [1-n], LevelThreeConcept (o) [1-n], Relationship (m) [1-n], ModelDiagram (m)
References: InfoDesign - Google - Journal of Conceptual Modeling
Definition: A Content Map is a document which categorizes the features of a site into meaningful groups based on how the user will think about the features. [syn: Content Mapping, Information Mapping]
Elements: DC.Title (m), DC.Creator (m), DC.Contributor (o), DC.Date.Created (m), DC.Date.Modified (m), DC.Language (m), DC.Subject (m), DC.Description.TableofContents (m), DC.Description.Abstract (o), DC.Relation.References (m)
TypographicalConventions (m), KeyToSymbols (m), ChangeLog (m), GeneralOverview (m), PageNumber (o) [1-n], Glossary (o), Index (o)
...
References: InfoDesign - Google - Concept Mapping Resource Guide
Definition: "A complete list of all the content that the information space holds and will hold" - CW
Elements: DC.Title (m), DC.Creator (m), DC.Contributor (o), DC.Date.Created (m), DC.Date.Modified (m), DC.Language (m), DC.Subject (m), DC.Description.TableofContents (m), DC.Description.Abstract (o), DC.Relation.References (m)
TypographicalConventions (m), KeyToSymbols (m), ChangeLog (m), GeneralOverview (m), PageNumber (o) [1-n], Glossary (o), Index (o)
LevelOneCategory (m) [1-n], LevelTwoCategory (o) [1-n], LevelThreeCategory (o) [1-n], TopicDC.Title (m) [1-n], Rationale (o)
Definition: The Functional Requirements is a document which captures all elements of the intended user experience. [syn: Feature Inventory, Functional Specifications]
Elements: DC.Title (m), DC.Creator (m), DC.Contributor (o), DC.Date.Created (m), DC.Date.Modified (m), DC.Language (m), DC.Subject (m), DC.Description.TableofContents (m), DC.Description.Abstract (o), DC.Relation.References (m)
TypographicalConventions (m), KeyToSymbols (m), ChangeLog (m), GeneralOverview (m), PageNumber (o) [1-n], Glossary (o), Index (o)
PurposeAndScope (m), Use Case (m) [1-n], TechRequirement (o) [1-n], ApplicableBizRules (m), SiteGoal (m) [1-n], SiteUse (m) [1-n], AnnotatedInterfaceScreen(s), FlowDiagram (m), ErrorHandling (m), AnnotatedPageTemplate (o), AnnotatedGlobalNavigation (o), TechConstraints (o), Maintenance (o), ExpectedChanges (o), LegalOrganizationalIssue (o) [1-n]
References: InfoDesign - Google
Definition: "A Decision Table is the precise documentation of the interaction design."
Elements: DC.Title (m), DC.Creator (m), DC.Contributor (o), DC.Date.Created (m), DC.Date.Modified (m), DC.Language (m), DC.Subject (m), DC.Description.TableofContents (m), DC.Description.Abstract (o), DC.Relation.References (m)
TypographicalConventions (m), KeyToSymbols (m), ChangeLog (m), GeneralOverview (m), PageNumber (o) [1-n], Glossary (o), Index (o)
...
Definition: "A Task Analysis is a discrete step-by-step analysis of how users accomplish their desired tasks." (CW)
Elements: DC.Title (m), DC.Creator (m), DC.Contributor (o), DC.Date.Created (m), DC.Date.Modified (m), DC.Language (m), DC.Subject (m), DC.Description.TableofContents (m), DC.Description.Abstract (o), DC.Relation.References (m)
TypographicalConventions (m), KeyToSymbols (m), ChangeLog (m), GeneralOverview (m), PageNumber (o) [1-n], Glossary (o), Index (o)
TaskAnalysisDiagram (m)
References: InfoDesign - Google
Definition: A Page Schematic is an element of the Functional Requirements document and contains a black and white design intended to convey emphasis, organization, and priority of information. [syn: Wireframe, Page Architecture]
Elements: DC.Title (m), DC.Creator (m), DC.Contributor (o), DC.Date.Created (m), DC.Date.Modified (m), DC.Language (m), DC.Subject (m), DC.Description.TableofContents (m), DC.Description.Abstract (o), DC.Relation.References (m)
TypographicalConventions (m), KeyToSymbols (m), ChangeLog (m), GeneralOverview (m), PageNumber (o) [1-n], Glossary (o), Index (o)
...
References: InfoDesign - Google
Definition: A Preliminary Style Guide is ...
Elements: DC.Title (m), DC.Creator (m), DC.Contributor (o), DC.Date.Created (m), DC.Date.Modified (m), DC.Language (m), DC.Subject (m), DC.Description.TableofContents (m), DC.Description.Abstract (o), DC.Relation.References (m)
TypographicalConventions (m), KeyToSymbols (m), ChangeLog (m), GeneralOverview (m), PageNumber (o) [1-n], Glossary (o), Index (o)
...
References: InfoDesign
Definition: "A Site Map is a diagram in which the various pages or page types throughout the site and the user paths to and from them." (CW) [syn: Site Architecture]
Elements: DC.Title (m), DC.Creator (m), DC.Contributor (o), DC.Date.Created (m), DC.Date.Modified (m), DC.Language (m), DC.Subject (m), DC.Description.TableofContents (m), DC.Description.Abstract (o), DC.Relation.References (m)
TypographicalConventions (m), KeyToSymbols (m), ChangeLog (m), GeneralOverview (m), PageNumber (o) [1-n], Glossary (o), Index (o)
...
References: InfoDesign - Google - DynamicDiagrams - Atlas of Cyberspace
Definition: A Use Case is ...
Elements: DC.Title (m), DC.Creator (m), DC.Contributor (o), DC.Date.Created (m), DC.Date.Modified (m), DC.Language (m), DC.Subject (m), DC.Description.TableofContents (m), DC.Description.Abstract (o), DC.Relation.References (m)
TypographicalConventions (m), KeyToSymbols (m), ChangeLog (m), GeneralOverview (m), PageNumber (o) [1-n], Glossary (o), Index (o)
UseCaseName (m), Scope (m), Level (m), PrimaryActor (m), ActorAction (m) [1-n], SystemResponse (m) [1-n]
References: InfoDesign - Google - Constatine & Lockwood
Definition: A Use Scenario is a document which defines a goal-oriented set of interactions between external actors and the solution object under construction. [syn: Stories of Use]
Elements: DC.Title (m), DC.Creator (m), DC.Contributor (o), DC.Date.Created (m), DC.Date.Modified (m), DC.Language (m), DC.Subject (m), DC.Description.TableofContents (m), DC.Description.Abstract (o), DC.Relation.References (m)
TypographicalConventions (m), KeyToSymbols (m), ChangeLog (m), GeneralOverview (m), PageNumber (o) [1-n], Glossary (o), Index (o)
...
References: InfoDesign - Google
Definition: A User Experience Outline ...
Elements: DC.Title (m), DC.Creator (m), DC.Contributor (o), DC.Date.Created (m), DC.Date.Modified (m), DC.Language (m), DC.Subject (m), DC.Description.TableofContents (m), DC.Description.Abstract (o), DC.Relation.References (m)
TypographicalConventions (m), KeyToSymbols (m), ChangeLog (m), GeneralOverview (m), PageNumber (o) [1-n], Glossary (o), Index (o)
...
References: InfoDesign
Definition: "A User Flow is a simple diagrammatical document that follows a user down a path of activity" (CW)
Elements: DC.Title (m), DC.Creator (m), DC.Contributor (o), DC.Date.Created (m), DC.Date.Modified (m), DC.Language (m), DC.Subject (m), DC.Description.TableofContents (m), DC.Description.Abstract (o), DC.Relation.References (m)
TypographicalConventions (m), KeyToSymbols (m), ChangeLog (m), GeneralOverview (m), PageNumber (o) [1-n], Glossary (o), Index (o)
Box (m) [1-n], Arrow (m) [1-n], BoxDC.Title (m) [1-n], BoxOption (o) [1-n], Rationale (o)
References: InfoDesign - Google
Definition: A User Persona is a document which contains one or more representations of target users based on user research data.
Background: "A User Persona is a user archetype you can use to help guide decisions about product features, navigation, interactions, and even visual design." - Kim Goodwin
Elements: DC.Title (m), DC.Creator (m), DC.Contributor (o), DC.Date.Created (m), DC.Date.Modified (m), DC.Language (m), DC.Subject (m), DC.Description.TableofContents (m), DC.Description.Abstract (o), DC.Relation.References (m)
TypographicalConventions (m), KeyToSymbols (m), ChangeLog (m), GeneralOverview (m), PageNumber (o) [1-n], Glossary (o), Index (o)
Name (m), Picture (m), Age (m), Income (m), Goal (m) [1-n], Choice (m) [1-n], Issue (m) [1-n], BehaviorPattern (m) [1-n], Skill (m) [1-n], Attitude (m) [1-n], Environment (o)
References: InfoDesign - Google - Perfecting Your Personas - Personas: Matching a Design to the Users' Goals
Definition: A User Profile is a document which identifies the needs, goals, and values of a target user group. [syn: User Analysis]
Elements: DC.Title (m), DC.Creator (m), DC.Contributor (o), DC.Date.Created (m), DC.Date.Modified (m), DC.Language (m), DC.Subject (m), DC.Description.TableofContents (m), DC.Description.Abstract (o), DC.Relation.References (m)
TypographicalConventions (m), KeyToSymbols (m), ChangeLog (m), GeneralOverview (m), PageNumber (o) [1-n], Glossary (o), Index (o)
TargetAudience (m) [1-n], TargetAudienceNeeds (m) [1-n], DesiredOutcomes (m) [1-n],
References: InfoDesign - Google
For problems and/or comments on this document, please contact Peter J. Bogaards (pjb@bogieland.com)