![]() The total set of elements should be kept as small as possible, maintaining a strict one-to-one correlation between concepts and symbols, so that the vocabulary can be learned and applied quickly. Small and self-contained: Because the diagrams are used by a diverse range of audiences with differing levels of knowledge of (or even interest in) diagramming systems used in other areas of technical development, the vocabulary should not require such knowledge or interest.The vocabulary should not favor the use of any particular software tool, but should instead enable architects to work with the tools they are most comfortable using. Tool-independent: The vocabulary should be designed so that specialized software tools are not required in order to construct diagrams. ![]() The elements of the vocabulary should be distinct enough from each other that moderately sloppy drawing cannot compromise the clarity of the diagram. Whiteboard-compatible: The vocabulary should be simple enough that diagrams can be sketched quickly by hand. ![]() Some other key requirements of a visual vocabulary for information architecture and interaction design include: The diagram thereby serves as a touchstone document for the development of more detailed documents specific to the needs of each audience. The sensible approach is to limit the detail in the diagram to that which can be usefully applied by all audiences. The trouble is that the detail each audience requires differs vastly from the detail required by others, and the bulk of this detail is irrelevant to the needs of other audiences. Information architects and interaction designers use them to develop detailed navigational and interface requirements for each page.Įvery one of these audiences (with the exception of sponsors) needs a great deal of detail to do their jobs.Technologists use them to derive functional requirements.Visual and interface designers use them to derive a count of how many unique page designs must be produced, and to obtain an initial sense of the navigational and interface requirements for these designs.Content producers use them to derive content requirements.Project sponsors and managers use them to obtain a general sense of the scope and form of the project.These descriptions, or diagrams, are used by five primary audiences: The vocabulary described here may be used by an information architect or interaction designer to describe, at a high level, the structure and/or flow of the user experience of a Web site. Numerous improvements to the shape librariesĪ visual vocabulary is a set of symbols used to describe something (usually a system, structure, or process). Modified the conditional branch element's behavior to allow for a null result Modified the cluster element's behavior so that it now appears only downstream from a conditional branch or selector Modified the arrow element to allow multiple arrowheads Posted cheat sheet and PDF shape template 1.1 () New shape libraries for Macromedia FreeHand Information on built-in support in OmnGraffle 2.0 This document discusses the considerations in development of such diagrams, outlines a basic symbology for diagramming information architecture and interaction design concepts, and provides guidelines for the use of these elements. Some restrictions may apply: conditional areasĭiagrams are an essential tool for communicating information architecture and interaction design in Web development teams.Choose one or more: conditional selectors.Pathfinding: conditional connectors and arrows. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |