We're considering a major site redesign, going beyond interface to changing how things behave on the back end. Since good UX starts from the ground up, I'm spending a lot of time pulling taxonomy needs, describing scenarios, determining relationships between categories, etc. In the past when I did this I had a much more hands-on role in developing the database architecture, etc. Now I'm an independent contributor in a non-IT dept, and I'm being asked to develop the redesign requirements from which they will build.
I'm not sure how much data to provide to (a) not do someone else's job for them - don't want to step on any toes! while (b) also assuring they have what they need to do the job. My thought is to provide use-case scenarios and the minimum taxonomic requirements, along with where those to map to existing categories, and let them figure out the specific tables, etc. Please note, this is *not* at the IA/UI stage yet. This is to assure that while the IA/UI work is done, any concurrent (or sooner!) development efforts from IT meet the eventual need. Has anyone else developed this kind of requirements documentation? What did you send? Thank, Alex O'Neal ux manager/knowledge engineer -- The best time to plant a tree is twenty years ago. The next best time is now. ________________________________________________________________ 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
