1. 1

2. 2 Human Factors in Software Engineering (HCI - Human Computer Interactions Alias MMI, Automation Boundary

3. 3 HCI Requirements HCI Specifications Standards MIL-H-46855BAFSC-DH 1-3 MIL-STD-1472MIL-HDBK-759A Factors Noise, Lighting, Temperature, Humidity, Air Flow Vibration, G-Forces, Motion, Reduced Oxygen, Air Pressure

4. 4 While we have defined use cases, objects and their relationships through object diagrams and sequence diagram to define interactions between objects. We are now ready to define and design our screens. Perhaps we need a method of specification of screen navigation.

5. 5 Objectives of GOOD HCI Design Reduce ErrorsIncrease Safety Improve ReliabilityImprove Maintainability Reduce Training RequirementsReduce Personnel Requirements Improve Working EnvironmentReduce Fatigue and Stress Increase Comfort Reduce Boredom Increase User AcceptanceReduce loss of time Increase Efficiency Improve Inf Sys Performance

6. 6 Five Step Process Step 1System Function Allocation Which processes require HCI - “Use Cases” Step 2Operational Timelines Step-by-Step description of human interaction with computer Step 3Operational Task Analysis Analyzing tasks (Start times, Step Names, Description, Cues for starting) Information needed by user, evaluations and decisions, actions required Duration and frequency, concurrent tasks, communication and coordination)

7. 7 Five Step Process Step 4HCI Design System Failures (error messages, logging), Help Packages, Response Times Characteristics, Guidelines and Standards Step 5HCI Testing Tests results of operational timeline and HCI design

8. 8 Five Step Process Step 1System Function Allocation Which processes require HCI - “Use Cases” Using the Use Case Diagrams, define the 0..n cases which need HCI designs. Some may not require HCI designs, only screen designs Some may need more than one HCI designs Allocate System Functions Use Cases + Custodials Operator Functions

9. 9 Step 2Operational Timelines Step-by-Step description of human interaction with computer Good Technique for documenting is the sequence diagram with interacting screens Define Operational Timelines Operator Functions Operational Timelines

10. 10 Operator: Keys in Customer ID (6 digits) Locate Customer Balance Record Display Screen 68739 Operator: Confirms balance verbally Locate Customer Detail Record Display Screen 68751 Operator: Determine Additional needed Access and display additional information on Screens 39534-73 Step 2Operational Timelines

11. 11 Customer ID Screen Main Menu Screen Balance Scr 68739 Record Scr 68751 Scrs 39534-73 Step 2Operational Timelines

12. 12 Step 3Operational Task Analysis Analyzing tasks (Start times, (under what conditions do you start) Step Names, Description, (narrative of task - user guide) Cues for starting, Information needed by user, (data operator needs) evaluations and decisions, (what decisions need to be made by the user) failure responses help available

13. 13 Step 3Operational Task Analysis actions required (what is the action, how often does it have to be done- frequency, how long does it take - duration, feedback given to user, body movements required by this action, physical workspace required, location of workplace, additional equipment needed, experience required, concurrent tasks if any, staffing description or limitations, communication and coordination required)

14. 14 Step 4HCI Design System Failures (error messages, logging), Help Packages, Response Times Characteristics, Guidelines and Standards - MTBF

15. 15 Step 5HCI Testing Tests results of operational timeline and HCI design Does it work Does it work correctly Is if efficient