2. Do not rush to specific
Developers always tend to be a solution provider, like to solve the problem and hope to soon see the result of the efforts. Sometimes this tendency to lead to quick results is a mediocre solution. Visual development tools today is to encourage this trend, we condone the screen simply by dragging and dropping pre-defined interface design components to solve the problem. For example, seldom consider the combo box or a drop-down list is the best choice. Do not rush early in the development of specific, developers, and team development process may create a more usable design and make superior user interface design. Do not define the implementation details too early, but should better understand the work required to complete the workflow and better grasp the user's intention after each step. If the development team has been jumping to the stage of implementation of specific programs should pay attention to those ideas in the design process will be placed in a "feedback - that" the cycle.
Some technologies, such as abstract prototype, in a general way can be a sticker on the expression of the necessary user interface elements that can help the development team prior to the entire user interface structure. Abstract prototype technology to ensure the software provides all the necessary components, but also to ensure the logical arrangement of these components, rather than carried out early in graphic design and interface components interface options.
3. To avoid creating a new, not become a slave to fashion
Interface design something new and not always better than the old stuff. If applied properly, the new interface components and interactive design will be a powerful tool and will capture the market advantage. A moment later the field of interface design really advanced methods will be copied word spread and become part of standard design. However, many innovative interface design than the traditional interface components and interaction design usability worse.
Also note that to avoid creating art for the art. I have seen some of the worst software usability is about to become a graphic artist or graphic artists, they lost in the visual effects in the final result is not identification of controls, poor readability of the layout, navigation design can not work. Efficiency and aesthetics are not always mutually exclusive, on the contrary, the best software is the combination of both. While the art can always limited, but you can focus to create effective, high-availability software to meet user needs.
Finally, do not assume that the interface should be designed to mimic a particular model or application of at least one of Microsoft's latest interface components. User interface design their own fashion trends, it is important to maintain status quo. New components and interaction terms (idiom, Alan Cooper's term) created every day. Like a house, car or clothing, software, style changes and progress, but simply look at user interface design can keep up with the current system. In particular, if the use of design software application closely integrated with Microsoft or associated, in many cases, this is a reasonable choice. However, following the lead is not a universal solution. One example is the assessment of my leadership of a Microsoft Excel interface design imitation currency trading system availability. Design allows users to visually analyze the decision-making information is very difficult, leading to unwieldy, inefficient navigation. Currency traders need new trading system is not Microsoft's spreadsheet interface design.
4. Efforts to establish effective interaction
Nobody likes boring, clumsy work. Make sure your software does not increase the work of other people do not feel good. Calculations required to complete a common keystrokes and mouse clicks. Treatment to make simple things simple, speedy completion of the interaction used. Do not deal with important information or key under submerged in multiple windows, or hidden in a "fabled" in the menu. Application of modeling technologies such as navigation maps to help design efficient work flow and to avoid too long or the navigation path leading to deadlock. As long as a piece of paper draw a prototype, user interface design principles such as basic efficiency, consistency and mission task visibility can spend, and on the problem area.
As impressive as Dilbert cartoon to point out that some software developers for the user additional meaningless steps to punish any error committed by the user, allowing users to jump circle the same as the daily work completed. If some members of the group appears to hate the user, so he went to meet clinicians, but not in the "Edit" menu with "Other".
5. Interface for the actual trial work
As a final quality assurance measures for user interface design is: Let each member of the design and development of software to use it for at least half an hour straight, continuous use of an hour more. Using actual data - the actual use of the data users. If because of confidentiality or security reasons can not use the actual work of data, allowing customers or users to create enough "pseudo data" (not just 10-20 record), can accurately reflect the actual complexity of data, potential errors and ambiguity (subtleties). As an independent check, make sure all the data field tested the maximum length, accuracy and over-rate inspection. Often surprisingly accurate in the database defined fields in the user interface is not long enough or the wrong definition. If the definition of data field is 25 characters in length, try to enter the 25 letters. You can see on the screen all the 25 letters? If necessary, the postal number of the input box to deal with foreign letters and numbers mixed encoding it?
Yes, in many companies these issues will boil down to quality assurance and database design department, but, surprisingly, it has been negligent. Therefore, the application user interface experience of trial to test the system itself. Noted that the process of testing a car assembly line as the final inspection - customers will see and experience. If the interface includes a data entry field, enter 50 or 100 records, not just the 1-2 record. If the application work in the uncertain light and noise conditions, the environmental conditions in this trial it. If you need to quickly enter or screen quick response, all members of the development team with a time limit placed on the pressure, and then ask yourself: Every day I want to use this software? I hope these tips can help you or a development team to answer: "Yes."
Recommended links:
Rebate good use of this double-edged sword
Premier Network Monitoring
Advertising weakness, public relations victory
Red Hat, JBoss founder and prospects may leave doubt
Levels adjustment channel TO marry
PDM, from said do (next)
Button icon button icons came here to get ready
Printing Machinery "pioneers", "English Education" story
Supply Chain Management And It Technology
Guide Teaching And Training Tools
DIVX to Zune
Recommend Source Editors
DV to AVI
ASF to MPEG
Best File Sharing Or Peer to Peer
No comments:
Post a Comment