CHAPTER 15
Risk reduction through prototyping
303
With any kind of prototyping—paper prototypes, wireframes, electronic prototypes, or
simulations—the business analyst must be careful not get drawn into high-precision user interface
designs prematurely. Prototype evaluators often offer feedback like “Can this text be a little darker
red?”, “Let’s move this box up just a little,” or “I don’t like that font.” Unless the purpose of the
prototype is to perform detailed screen or webpage design, those sorts of comments are just
distractions. The color, font, and box positioning are immaterial if the application doesn’t properly
support the users’ business tasks. Until you’re sure you have a rich understanding of the necessary
functionality, focus the prototyping efforts on refining requirements, not visual designs.
Do'stlaringiz bilan baham: |