[Sigia-l] strategy to mocking wireframes?

[Eric Scheid]

found on the web ...

> The requirements prototype is typically a wireframe mockup of the major pages
> of the application. A mockup is a rough sketch that shows the functionality
> (the interactive features) and the content of the site. Each major object on a
> page is enclosed in a box that includes descriptive information.

so far so good ... but then ...

> Many times you end up with better results if you start to drafting the mockup
> based on use-case scenarios rather than a information content map (users do
> not necessarily browse the site hierarchically, rather they go through cross
> sections of the site structure).

Now that's interesting.

What's your experience with constructing wireframe mockups? How do you know
whether it should be use-case driven or info-map driven? How do you balance
those competing needs for the ambiguous cases? Are the two drivers, usage
vs. info, more often in alignment or in competition?

e.