SIGIA-L Mail Archives: Re: [Sigia-l] Site maps for web apps, vs for content sites?
Re: [Sigia-l] Site maps for web apps, vs for content sites?
In my previous job I was responsible for creating and maintaining screenflows
and wireframes for web applications. I think the largest application I
contained a little over 400 pages. These are all individual, unique pages and
all had their own wireframe. I thought that was pretty big.
The way we handled large projects like that is using both sitemaps and
screenflows. For the landing pages we used sitemaps, showing which forms were
available from which pages. Once you zoom in on a form, it becomes more of a
screenflow, going from left to right (generally speaking). Of course,
the number of pages just becomes to big to show from left to right, and flows
start to snake over the page. We could have chosen to create new screenflow
pages for these, but we've tried to minimize the number of screenflow pages
(the screenflow document had over 80 pages as it was).
Of course, this becomes very hard to read for the client, which is why we
integrated the screenflows and wireframes into one HTML deliverable. This
allows the client to browse through the sitemap/screenflow, zoom into more
detailed flows and see wireframes and how they relate to eachother.
Before anyone starts saying you should never create 400 wireframes...
served as the main requirements documentation for the developers. So
of the forms were defined on the wireframes. Also, all (introductory and
explanatory) text on the wireframes was to be the final text in the
application, and therefor the wireframes also served as documentation for the
testers. SO, although after two or three forms you definitely see patterns
emerging, all screens had to be wireframed for documentation purposes.
For us, 400 pages in this light was pretty big. Especially if you're dealing
with a client that has multiple project teams for specific functionality, none
of which were able to baseline that functionality at an early stage...
Quoting Todd Warfel <lists_at_toddwarfel.com>:
> Yes, but you're not mapping all 40,000 pages.
> On Feb 11, 2006, at 7:18 AM, Donna Maurer wrote:
> To me, less than 1000 pages is small (less than 200 is teeny) and it doesn't
> get large
> until about 10,000, massive isn't until at least 40,000 (and then they have
> to be messy,
> No wonder I think differently ;) No wonder I can never figure out how you
> all represent
> a site with a diagramatic site map.
> Todd R. Warfel
> Partner, Design & Usability Specialist
> Messagefirst | designing and usability consulting
> Contact Info
> Voice: (607) 339-9640
> Email: todd_at_messagefirst.com
> AIM: twarfel_at_mac.com
> Blog: http://toddwarfel.com
> In theory, theory and practice are the same.
> In practice, they are not.
> When replying, please *trim your post* as much as possible.
> *Plain text, please; NO Attachments
> Searchable Archive at http://www.info-arch.org/lists/sigia-l/
> IA 06 Summit. Mark your calendar. March 23-27, Vancouver, BC.
> Sigia-l mailing list -- post to: Sigia-l_at_asis.org
> Changes to subscription: http://mail.asis.org/mailman/listinfo/sigia-l
When replying, please *trim your post* as much as possible.
*Plain text, please; NO Attachments
Searchable Archive at http://www.info-arch.org/lists/sigia-l/
IA 06 Summit. Mark your calendar. March 23-27, Vancouver, BC. http://www.iasummit.org/
Sigia-l mailing list -- post to: Sigia-l_at_asis.org
Changes to subscription: http://mail.asis.org/mailman/listinfo/sigia-l
This archive was generated by hypermail 2.1.6
: Mon Feb 13 2006 - 09:50:10 EST