Thanks Steve, Your answer is clear except that I don't quite understand how you technically avoid the problem that a child panel wireframe, contained in another drawing document, and copied to the parent wireframe in scenarios 1, 2, 3, can get out of sync when its source is modified? Do you mean (by the "simple representation") that you don't copy but instead show a plain gray box with a reference? In this case, doesn't it affect the visual presentability of the parent wireframe?
Are there other caveats I have overlooked? Oleg. On Fri, May 30, 2008 at 8:00 AM, Steve Baty <[EMAIL PROTECTED]> wrote: > Oleg, > > One thing I try to aim for in my documentation is that each page has the > same density of information. So where I have a screen that includes a lot of > complexity, I would look to break that complexity off into separate pages > with references on the parent. That principle would apply to your scenarios > 1 & 2. And it applies across deliverables for that project. Depending on the > primary audience for the wireframes I'd adjust the 'standard' level of > complexity and then maintain that density consistently. > > For scenario 4 I would use layering within your wireframing tool and place > the more detailed information into layers that are hidden or shown depending > on the audience. > > For scenario 3 I would use the equivalent of a pattern library with the > parent wireframe containing a simple representation with a reference to the > component detailed wireframe. > > Regards > Steve Baty > > 2008/5/30 Oleg Krupnov <[EMAIL PROTECTED]>: >> >> I'm looking for the current best practices of managing complexity of >> wireframes. >> >> What do you do in the following situations? >> >> 1. A page includes multiple panels, each of them is quite complex, with >> many >> details and notes. How to show all child panels and their notes without >> cluttering the parent page's wireframe? >> >> 2. A page includes an interactive panel, i.e. one that has multiple >> states. >> The size of the interactive panel can be small (i.e. a creeping line) or >> large (i.e. a tab page). How to show all panel states best? >> >> 3. A page includes a panel that is reused on different pages (i.e. as >> common >> info block), or multiple times on the same page (e.g. item in a list). How >> to show the reused panels best, avoiding copying/out-of-sync problems? >> >> 4. Different notes and different level of detail should be shown to >> different audiences. How to create different versions of the same >> wireframe >> best? Also what to do if there is not enough room in the sidebar for all >> footnotes? > > ------------------------------------------------ > Steve 'Doc' Baty B.Sc (Maths), M.EC, MBA > Principal Consultant > Meld Consulting > M: +61 417 061 292 > E: [EMAIL PROTECTED] > > UX Statistics: http://uxstats.blogspot.com > > Member, UPA - www.upassoc.org > Member, IA Institute - www.iainstitute.org > Member, IxDA - www.ixda.org > Contributor - UXMatters - www.uxmatters.com ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
