27342_104

27342_104 - Introduction The Interdisciplinary Design...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
1 Universal Usability Introduction ± The Interdisciplinary Design Science of Human-Computer Interaction (HCI) combines knowledge and methods associated with professionals including: ± Psychologists (incl. Experimental, Educational, and Industrial Psychologists) ± Computer Scientists ± Instructional and Graphic Designers ± Technical Writers ± Human Factors and Ergonomics Experts ± Anthropologists and Sociologists Fig 1.1A System interfaces Courses? Manual? System Hotline? User interfaces Accounting system Technical interfaces Factory Fig 1.1B Quality factors All factors important. Hard to measure, but possible. Easy to make a user interface: Just give access to the database Hard to make a good user interface Quality factors: Correctness Availability Performance Security Ease of use Maintainability . . . Functionality: Necessary features see, edit create, delete Database Usability requirements ± Synonyms for “user-friendly” in Microsoft Word 2002 are easy to use; accessible; comprehensible; intelligible; idiot proof; available; and ready ± But a “friend” also seeks to help and be valuable. A friend is not only understandable, but understands. A friend is reliable and doesn’t hurt. A friend is pleasant to be with. ± These measures are still subjective and vague, so a systematic process is necessary to develop usable systems for specific users in a specific context Usability requirements (cont.) ± The U.S. Military Standard for Human Engineering Design Criteria (1999) states these purposes: ± Achieve required performance by operator, control, and maintenance personnel ± Minimize skill and personnel requirements and training time ± Achieve required reliability of personnel-equipment/software combinations ± Foster design standardization within and among systems ± Should improving the user’s quality of life and the community also be objectives? ± Usability requires project management and careful attention to requirements analysis and testing for clearly defined objectives
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
2 Goals for requirements analysis ± Ascertain the user’s needs ± Determine what tasks and subtasks must be carried out ± Common tasks are easy to identify. ± Include tasks ± performed only occasionally. ± exceptional task for emergency condition. ± Functionality must match need or else users will reject or underutilize the product Goals for requirements analysis ± Ensure reliability ± Actions must function as specified ± Database data displayed must reflect the actual database ± Appease the user's sense of mistrust ± The system should be available as often as possible ± The system must not introduce errors ± Ensure the user's privacy and data security by protecting against unwarranted access, destruction of data, and malicious tampering Goals for requirements analysis ± Promote standardization, integration, consistency, and portability ± Standardization : use pre-existing industry standards where they exist to aid learning and avoid errors (e.g.
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 01/17/2012 for the course GCIS 638 taught by Professor Tang during the Spring '09 term at Gannon.

Page1 / 8

27342_104 - Introduction The Interdisciplinary Design...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online