Using Scenarios to Validate Requirements through the use of Eye-Tracking in Prototyping

Research has shown that eliciting and capturing the correct behavior of systems reduces the number of defects that a system contains. A requirements engineer will model the functions of the system to gain a comprehensive understanding of the system in question. Engineers must verify the model for correctness by either having another engineer review it or build a prototype and validate with a stakeholder. However, research has shown that this form of verification can be ineffective because looking at an existing model can be suggestive and stump the development of new ideas. This paper provides an automated technique that can be used as an unbiased review of use case scenarios. Using the prototype and a scenario, a stakeholder can be guided through the use case scenario demonstrating where they expect to find the next step while their eye movements are tracked. Analysis of the eye tracking data can be used to identify missing requirements such as interaction steps that should have alternative sequences or determining problems with the flow of actions