Example

The following gives a representative example of how a roleplay proceeds. In particular it gives examples of the kinds of errors that crop up.

Report Seat Availability

The scene: The ticket seller (``user'') is using the computer ``system'' to determine whether the seats requested by the Arts Centre patron for a performance are in fact available.

Take 1:

User:

I say which performance I want and the system shows me the performance details.

CUT! -- it's the system's job to say what the system does. This is often just an error made by the role-player, but can also indicate confusion as to where the system boundary is.

Take 2:

User:

I say which performance I want.

System:

I display the performance details and say whether or not the seats are available.

CUT! -- the seats haven't been specified yet.

Take 3

User:

I say which performance I want.

User pauses waiting for a response, then Looks over to the person playing the system, who is still looking at the use case card, and doesn't realise he's being cued.

System?

System:

You're supposed to say what seats you want to know about too. Points at card.

User:

Oh, right

CUT. The roleplay does not allow anyone to hide -- all participants have to engage with what the use case is about.

Take 4:

And so on...