An approach I've been using is sort of a bastardized version of "page description diagrams" explained by Dan Brown here: http://www.boxesandarrows.com/view/where_the_wireframes_are_special_deliverable_3 with some elaboration here: http://www.dmxzone.com/showDetail.asp?TypeId=2&NewsId=3991&LinkFile=page2.htm
It helped an approach where, in our case, we had a completely component based application where everything had persistent features on a module basis, but it was fully customizable on the front-end and the application functions would vary within certain parameters. It's not an abstract visual vocabulary, but I found it jumped both the hurdles of client understanding and designer understanding fairly well (I used our salespeople, project managers and graphic designers as guinea pigs) while still communicating to our engineers how things ticked. Scott On Wed, Sep 24, 2008 at 8:56 AM, Will Evans <[EMAIL PROTECTED]> wrote: > Well, yeah (you are the prototype guy!) - but within the constraints of a > diagram, i was wondering if anyone explored and abstract visual vocabulary > for communicating recursive iteration. No prototyping allowed! :-) > > On Wed, Sep 24, 2008 at 7:34 AM, Todd Zaki Warfel <[EMAIL PROTECTED]>wrote: > >> I'd use a prototype. >> >> With a task flow, you'd need to illustrate a series of trees and loops. >> >> On Sep 24, 2008, at 6:34 AM, Will Evans wrote: >> >> How would you do it? >>> >> >> >> Cheers! >> -- * It's very important to know when you're in a pissing match. And it's very important to get out of it as quickly as possible. - Randy Pausch ________________________________________________________________ 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
