This week in ux-clinic: The requirements to design gap
July 24th, 2006
This week in the ux-clinic discussion group:
I work for a large medical software company that attempts to follow a strict engineering process (partly for ISO certification). All logged bugs are supposed to be tied to a requirement (we use ReqPro), but managers aren’t sure what to do with “visual” bugs because visuals aren’t included in the official requirements docs.
So the big question is: What is the best way to fit the visual/UI deliverables into the engineering process?
Specifically:
- How best to deliver visuals? PDF? HTML?
- If designers don’t write the req documents, even if we wanted to, how do we get the designs into the requirements?
- How should visuals relate to the written requirements?
Add a Comment or trackback from your own site.
Subscribe via RSS 
Have “prototyping” as one of the tasks for requirements phase. Get a usability/design expert to prototype the workflow. If that’s deemed too expensive use storyboards and/or paper prototyping.