Info-Tech's bundle of The Top 50 IT Templates are valuable tools designed to help you bank your most precious asset – time. Their ready-to-use format means that you can download and edit these tools whenever you need them to suit your specific IT and business needs.
Usability Goals and Requirements Purpose This template provides a worksheet for use on projects to set usability goals and measurable usability requirements. The worksheet should be kept along with the overall Requirements Specification for the project. Test planning and execution will need to include test conditions and cases to prove the usability requirements are met by the solution. Worksheet Setting usability goals and defining measurable usability requirements can be done for an entire automated solution or for components of the solution. For example, the goals and requirements are often different for functions associated with primary users vs. secondary users. A good starting place is a use case model that defines the actors to the system and the functions associated with each actor. Consider the priority of each business function to be provided. This worksheet can be used per functional area of the solution. Focus the cost and effort of determining usability requirements (and design and testing against the requirements) on the high priority/high business value functions. The worksheet below lists the common industry usability goals. More high-level goals can be added by adding rows to the table. Examples and suggestions provided in the Measurable Requirements column need to be replaced by the specific requirements for the project. Use the Priority column to indicate which goals are of higher importance than the others. This can be done by indicating low-high, using A/B/C or actual numbered priorities. Focus effort on determining measurable usability requirements on the top three to five priority goals. Use the Ranking column in a number of ways: As a method of communicating with user representatives to get their perspective on each goal. As a thinking process for the requirements/business analyst to help determine the numbers or percentages in the measurable requirements. As input for the designers to help them determine design options. Goal Ranking Priority Measurable Requirements (1= low, 5 = high) Automation Note: While all the goals will impact design, this one is often the easiest A high ranking means that much of the task relationship for the design team to is routine and the user should not be see. bothered with it. Example: rather than having a user specify each name of a series The Delete Prospect function shall of files to print, a system might automate allow for multiple prospects to be specifying files by allowing wildcards in
Pages to are hidden for
"Usability Goals and Requirements"Please download to view full document