ISRE: Immersive Scenario-Based Requirements EngineeringBy Allistair Sutcliffe, Brian Gault & Neil Maiden

Introduction (1/3) - domain

Requirements Engineering

VR-RE

ISRE

Introduction (2/3) - purpose

“Its purpose is to identify, classify and analyse usability issues and other problems that may affect the capture and analysis of requirements in virtual environments.”

Lack of haptic feedback

Bad image quality

Clunky controls

Messy interface

No sense of ‘presence’

Introduction (3/3) - context

$350.000.000

$50.000 - $3.000.000

Authors

Alistair Sutcliffe

Professor of systems engineering

Director at centre for HCI design, Manchester

Neil Maiden

Professor of systems engineering

Head at centre for HCI design, London

Brian Gault

?

Related literature

VR-RENorman (‘86)Bowman (‘97)Sutcliffe (‘00)

REKaur (‘97)

Cockburn (‘01)

Virtual prototyping in Engineering

Virtual reality in Psychology/Medicine

ISRE

PDD (1/5) - overview

1. Expert Walkthrough

A. Technology audit

B. Requirements analysis walkthrough

2. Interaction analysis

3. Requirements problem analysis

PDD (2/5) – Expert walkthrough

PDD (3/5) – Requirements analysis Walkthrough Detail

PDD (4/5) – Interaction Analysis

PDD (5/5) – Requirements problem analysis

Example (1/4) – Technology Audit

High scoring interaction features

Low scoring representation features

Example (2/4) – Requirements analysis walkthrough

Log Entry Incident Related Feature

LE-001 Task 1, Approach and orient. Low resolution imaging causes difficulties when attempting to orient in the environment.

RF003

LE-002 Task 3, Manipulate object. Lack of haptic feedback makes it hard to determine when an object is ‘held’

FF001

LE-003 Task 3, Assess feedback. The system makes a slight beeping noise to indicate task completion. Hard to hear over background noise.

FF014

LE-004 Task 4, Manipulate object. Inaccurate controls make it difficult to select object.

IF026

LE-005 Task 5, Locate objects. Counterintuitive command caused delay when attempting to locate the fire extinguisher.

IF027

LE-006 … …

Example (3/4) – interaction analysis

Good old fashioned ‘think aloud’ observation

Note down any problems the user mentions

Note down violations of performance measures

Note down task failures

Note down the difficulties you see but the user doesn’t speak about

Example (4/4) – Requirements problem analysis

Identify, specify, prioritize

Main cause, specific cause, weight