Goal, Intention, Action 1. Psychological variables • Goal (person wish) and, • Intention (decision to act) 2. Physical variables (for execution) • Controls 3. Mapping psychological and physical variables 4. HCI is about the physiological, SE usually worry about the physical.
Mapping • How much intelligence should be present? • How to determine the proper level ? ( too specialized vs too primitive) • Whether or not provide feedback? • Is this feedback?
Mapping Tradeoffs • Short-term memory (5 slots, each item decays with a half-life of 1.5s) • Information vs time (confusion vs completeness) • Users do not read • First and second order issues (for whom?) PS. Separate interface from the system
Items to be considered: • Usability requirements Usually related with multiprocessing (real-time) • Standards, UI design (structure): feedback, performance, high-level and low-level details, • Affect and human (subjective) factors: color, pictures, etc.
UI Testing • The Robot class in the Java AWT package is used to generate native system input events for the purposes of test automation, self-running demos, and other applications where control of the mouse and keyboard is needed. • The primary purpose of Robot is to facilitate automated testing of Java platform implementations.
SER594 – Human Computer Interaction Javier Gonzalez-Sanchez [email protected] Spring 2019 Disclaimer. These slides can only be used as study material for the SER594 course at ASU. They cannot be distributed or used for another purpose.