These standards have been developed by industry leaders through validated research, and are intended to help designers use the best methods to generate findings we can rely on. In the first part of our article we looked at three parts of ISO , including the definition of usability, its dimensions and quality aspects.
We also saw how norms on user guidance, presentation of information, and dialogue techniques can support us in creating usable interactive products. Part two of the article will focus on the areas of ISO that are related to processes for usability engineering, especially in the context of Human Centered Design.
It provides requirements and recommendations for human-centered design principles and activities throughout the life cycle of computer-based interactive systems.
It also helps us to separate out UX from usability. In our last article we focused on usability, but Part defines the user experience. For example, if a user interacts with the same software on Mac and PC in order to reach the same goals, the usability will probably be pretty much the same on both platforms, assuming the user interface and processes remain unchanged , but the user experience might be different. The user group on the Mac might feel better and have a more positive attitude towards using the software than the users on the PC, and thus have a better perceived user experience.
Figure 4: Relationship between Usability and User Experience. The human-centered design process described in Part supports an iterative user-oriented approach, made up of the following phases Figure 5 :. Figure 5: Human-centered design process for interactive systems. Phase 1 : The context of use consists of user characteristics, tasks, and equipment as well as the physical and social environment in which the product is used.
The UX team needs to identify all of these for each target user group, since each user group may have different needs for the product. We can use evaluation methods like interviews or diary studies to understand the context of use.
Based on what we learn about how people may use the system, we can then determine the usage requirements, which brings us to phase two. Phase 2 : The usage requirements are derived from the tasks that the user performs during a contextual scenario. In other words, usage requirements describe which actions a user should be able to perform while interacting with the system; they go hand in hand with the requirements for the system.
In phase 2 we define those requirements for the system, based on what the user needs to do within the context of use. Name the process es , provide an outline of the process es , a short description of the process es , and an explanation of the reason s why use of any of the existing user-centered design standards was impractical. Submit test scenarios used in summative usability testing.
Resource Document. Paragraph g 3 i. Test Lab Verification. Paragraph g 3 ii. Paragraph g 3 iii. Paragraph g 3 iv. Paragraph g 3 iv A. Paragraph g 3 iv B. Paragraph g 3 iv C. The tester verifies that the user tasks employed in the study are prioritized in accordance with the risk associated with user errors NISTIR 3. The tester verifies that the test scenarios included in the NISTIR content report for each of the UCD Required Criteria are inclusive of the tasks or functionality the health IT developer provided for testing to the certification criterion.
Paragraph g 3 iv D. The tester verifies that the specified metrics are captured in the report. Paragraph g 3 iv E. Paragraph g 3 iv F. Measures of satisfaction may include task-based satisfaction measures, post-session satisfaction measures and other industry-standard or literature-recognized satisfaction measures e.
The tester verifies that all major test findings and the identified area s of improvements are reported. The tester verifies that test results provided an analysis of the use, tested performance and error rates in order to identify risk prone errors -- with a potential likelihood of occurrence and adverse consequences NISTIR Paragraph g 3 v.
The heath IT developer supplies the test scenarios used for the summative usability testing conducted on each of the safety-enhanced design criteria specified in g 3 i submitted for testing. The test scenarios used in the summative testing should reflect prioritized use cases based upon a risk analysis.
The tester shall verify that the name and version of the product are the final version release of the product for which certification is being sought. Initial Publication. General clarification added to clarify how gap certification eligible certification criteria are treated under the SED criterion. Approaches such as the user-centered design UCD , which is already a standard within the software industry ISO , provide specifications and guidelines to guarantee user acceptance and quality of eHealth systems.
Methods: The proposed PHR-S was developed using a formal software development process which, in addition to the traditional activities of any software process, included the principles and recommendations of the ISO standard. To gather user information, a survey sample of 1, individuals, eight interviews, and a focus group with seven people were performed. Throughout five iterations, three prototypes were built.
0コメント