 |
|||||
 |
 |
 |
 |
 |
 |
 |
|
| Introduction | |
| Developing an information hierarchy | |
| Establishing a controlled vocabulary | |
| Testing the hierarchy and labels | |
| Designing transactional flows | |
| Flow charting tools and methods | |
| References | |
|
|
|
|
|
|
|
|
Designing transactional flows
Note that Figures 2 and 3 are focused on the "what" of the flow—they describe the actions a user takes and what the system does in response. They do not specify the "how"—for example, what types of actions will be grouped together on a page. An information architect may or many not be responsible for defining flows at the "what" stage of a project. In traditional software development environments a business analyst or systems analyst might do this. Figure 4, below, illustrates the next stage of the flow design: a page flow diagram that shows the information architect has grouped together Enter "From" Account, Enter "To" Account, Enter Amount of Transfer together on a single page.
|
|
Methods | Basic Flow | Alternative Flows | Page Flow Diagram |
