This link has been bookmarked by 122 people . It was first bookmarked on 03 Aug 2006, by Manfred.
-
22 Apr 22
-
28 Oct 20
-
16 Jul 17
-
07 May 17
-
08 Jan 17
-
08 Jul 16
-
24 Mar 16
-
Note that conceptual structure is not the same as navigational structure.
-
The objective of the information architecture diagram is not to provide a full-blown navigational specification;
-
As with navigation, details of interface should not appear in the diagram
-
what the discrete steps are within these tasks.
-
the diagram should emphasize how the user flows through defined tasks,
-
When describing interaction design
-
f you find yourself drawing buttons and fields, you're probably loading the diagram down with excess detail.
-
When describing information architecture,
-
the diagram should emphasize conceptual structure and organization of content
-
- The system presents the user with paths.
- The user moves along these paths through actions.
- These actions then cause the system to generate results.
-
where a user action generates multiple, simultaneous results
-
such as spawning a pop-up window at the same time a page is loaded in the main window, or displaying a page while a file is being downloaded).
-
(such as appearing in a pop-up window, or having some unique design treatment
-
identify a group of pages that share one or more common attributes
-
iterative area -- a stack of rounded-corner rectangles -- instead.
-
connectors and arrows don't actually point to the areas themselves. The area elements serve only to enclose the pages.
-
Such a reusable sequence is called a flow
-
The association of an attribute with a particular value is called a condition
-
every path is presented to every user under every circumstance,
-
each path always leads to the same result.
-
the system decides which paths or results are presented to the user based upon evaluating one or more conditions.
-
a decision point, and as in traditional flow charts, it is represented by a diamond.
-
a path may or may not be presented to the user depending upon whether one or more conditions are met.
-
if the condition is met, the path is made available. If not, no path exists.
-
For example, there may be a page containing sensitive information that only company employees should have access to. The condition in this case would be the user type (employee)
-
In the decision point example, only one path (or navigational element) was presented to the user; where that path took the user was dependent upon certain conditions.
-
only one path (or navigational element) was presented to the user; where that path took the user was dependent upon certain conditions.
-
The conditional branch indicates that the system is deciding which path will be presented to the user. The paths from page A to pages B, C, and D are mutually exclusive;
-
with the selector, the various downstream paths are not mutually exclusive
-
conditional areas are associated with a result, which is generated in the event that the condition(s) are not fulfilled.
-
-
26 Feb 16
-
18 Jan 16
-
05 Feb 15
-
28 Jan 15
-
09 Aug 14
-
01 Aug 14
-
27 Jul 14
-
16 Dec 13
-
15 Nov 13
-
20 Sep 13
-
13 Apr 13
-
19 Mar 13
-
06 Mar 13
-
22 Feb 13
-
19 Feb 13
-
04 Jan 13
-
15 Nov 12
-
02 Oct 12
-
30 Sep 12
-
04 Sep 12
-
30 Jul 12
-
28 Jul 12
-
10 Jul 12
-
29 Jun 12
-
30 May 12
-
12 Jul 11
-
12 Apr 10
-
18 Mar 10
-
15 Sep 09
-
26 Aug 09
-
13 Aug 09
-
04 Aug 09
-
22 Jun 09
-
08 Oct 08
-
06 Aug 08
Angus HongDiagrams are an essential tool for communicating information architecture and interaction design in Web development teams. This document discusses the considerations in development of such diagrams, outlines a basic symbology for diagramming information a
onlinebook visualization usability interaction reference semantics softwarearchitecture
-
05 May 08
-
10 Jan 08
-
20 Nov 07
-
26 Sep 07
-
23 Aug 06
-
03 Aug 06
-
02 Jun 06
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.