 |
|||||
 |
 |
 |
 |
 |
 |
 |
|
| Introduction | |
| Developing an information hierarchy | |
| Establishing a controlled vocabulary | |
| Testing the hierarchy and labels | |
| Designing transactional flows | |
| Flow charting tools and methods | |
| References | |
|
|
|
|
|
|
|
|
Flow charting tools and methods An information architect must have at his or her command a visual vocabulary to communicate the design of information hierarchies and transactional flows. At a minimum this means mastering a flow-charting application such as Visio. An example of a visual vocabulary specifically for information architects has been created by Jesse James Garrett. This includes a specialized set of objects that can be imported into Visio. More information is available at his web site: http://www.jjg.net/ia/visvocab/ Keep in mind that the purpose of a visual vocabulary is to communicate your design to other development team members. It’s important, therefore, that your diagrams be very clear and contain a legend that explains the meaning of all symbols used. |