[ A Critique of the System's Design: Strengths and Weaknesses of Sitemapping Software ]

Dreamweaver's two models of representation:

-ends up in an endless loop of links.

[ Intro ]

[ A Description of the System: Software for the Creation of Sitemaps ]

[ A Critique of the System¹s Design: Strengths and Weaknesses of Sitemapping Software ]

[ Scenario 1: create a new sitemap ]

[ Scenario 2: add new pages to a sitemap ]

[ Scenario 3: link to an existing page ]

[ Scenario 4: add a folder icon that represents a category, but not an actual page ]

[ Scenario 5: fit the flowchart within the current window the sitemap ]

[ Scenario 6: use the controls for editing ]

[ Scenario 7: collapse or expand a tree ]

[ Scenario 8: FTP files from the sitemap ]

[ Scenario 9: save the sitemap ]

[ Scenario 10: save the sitemap as an external file ]

[ Scenario 11: print the sitemap / flowchart ]

[ Scenario 12: add design notes and comments to pages to aid in collaboration with others ]

[ Scenario 13: show possible links through the hierarchy model ]

[ Scenario 14: match file structure to the hierarchy ]

[ Scenario 15: diagram user paths of interaction within the site, navigation scenarios ]

[ Scenario 16: track multiple user paths of interaction within the hierarchy in real time, and display how long they stay on each page ]

[ Scenario 17: navigate a sitemap in three dimensions ]

[ Scenario 18: overlay site statistics on the flowchart ]

[ A Proposal for a Better Design: A Sitemapping Tool with User Tracking, Statistics Overlay, and 3-D Capablities ]