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.
However, I realized that not only didn't I keep a master list of UI elements, I'd never actually seen one outside of wire frames. In my previous life as a systems engineer, this type of directory of all database and system fields would have very likely been a piece of the project. So, does anybody on this list create a deliverable of this nature? If so, are there specific conditions under which you would do this? Most of my colleagues just create the wire frames and let them speak for themselves. Thanks Mark Richman Product Designer Intelliverse ________________________________________________________________ *Come to IxDA Interaction08 | Savannah* February 8-10, 2008 in Savannah, GA, USA Register today: http://interaction08.ixda.org/ ________________________________________________________________ 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
