[IxDA Discuss] Has anyone been asked to create a directory of UI elements?

[Dan Brown]

Mark,
Not sure if this addresses your question... These days, we're making
modular wireframes: creating individual screen components and
assembling wireframes from those "lego bricks". As part of that
process, we usually generate a spreadsheet of all the components we
want to create. This allows us to validate the list before diving in
and wireframing all of them.

One advantage to this modular approach is that we can then quickly and
easily create a document that specifies behaviors/details for each
component -- a component catalog. Imagine that each component is
wireframed separately in individual Visio (or whatever format you use)
files. We simply drop the component into a specification document
instead of a screen template. (We call those "views".)

As for specific conditions, the component catalog is ideal when we
create a wide set of components for use in a variety of circumstances
that are not covered by all the wireframes/templates. That is, the
range of wireframes does not include every possible component. There
are other situations, but that one came to mind...

-- Dan




On 12/12/07, Mark Richman <markjrichman at gmail.com> wrote:
> I was discussing a new project with someone from our Sales group, and
> they asked me how I kept track of fields in case they were dropped
> from the actual implementation for some reason. I said that I kept old
> versions of the wire frames and usually commented any changes
> following the first version.
-- 
| work: eightshapes.com
| book: communicatingdesign.com
| blog: greenonions.com
| talk: +1 (301) 801-4850