Hi Oleg, On 5/30/08, Oleg Krupnov <[EMAIL PROTECTED]> wrote: > > > Sounds like something I've been thinking about myself. Could you please > shed > more light on what your business requirements look like and how you trace > them to the UI elements?
In my organization, we have (among other practices) highly-skilled BAs and UXDs. In situations in which we're dealing with very detailed business requirements (new business processes, detailed technical interactions, etc.), the BA on the project handles and documents all that stuff independently of the UXD. We collaborate, of course, to keep aware of what each other is doing. Axure allows you to customize annotations to fit your needs. On my projects, I always add a field called "Business Requirements." 90% of the time it's just me filling out this annotation with directions to mask the field, character limits, etc. But when there are more detailed requirements, I'll get input from the BA and essentially paste the text they give me into the field. Where appropriate, our documents reference each other, e.g., "For details on this functionality, see the User Interface Design Document" or "For details, see the Software Requirements Specification." I have never found the need to trace specific requirements to specific UI elements. If I did, I'd handle it by including a simplified list of the requirements in the prefix document (that gets added to the beginning of the spec) in which I textually indicate how the requirement is met in the UI. I might also provide links to relevant sections of the spec, but that could only happen after you generate it (which I recommend not doing until you've completed, tested, and revised your prototype). Also, I try to use masters whenever possible. Maybe 75% of each prototype I create is composed of masters. This makes it real easy to change stuff if business requirements change. Otherwise, you'd have to find each instance of an object that references the requirement that has changed. > 4. No facility for quickly importing fake data. If you need to display > > I am just curious where designer folks usually take those data and in what > form. What I do is develop the prototype test plan *BEFORE* I develop the prototype. This way, I know the specific information that participants will be looking for during the test, so I can just put it in at the start. Where I get this data from is usually the client. I ask for example content and integrate that into the prototype. If they've got an existing site, I often just copy and paste from that. I guess for me it's mainly content rather than data... I got a tweet this morning from Dave Malouf with a link to his rant about the suckage of MS Expression Suite in which he laments its inability to integrate data... Dave, can you elaborate on this question? Take care, F. ________________________________________________________________ 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
