1. Create a list of scenarios for use of the system (i.e., use cases)

Use brainstorming

a) Concentrate on the "must do" scenarios: Core behaviors of the system, touch central features of system

    ATM example: customer withdraws cash

b) Next, develop conditional "can do if" scenarios

    Routine tasks to be carried out under certain conditions

c) Finally, record "might do" scenarios ("abuse cases") to test flexibility

    Exceptions -- unusual, complex, difficult to handle cases     Help uncover poor collaborations and clarify system scope     (a stress test)

    ATM example: withdrawal with insufficient funds

2. Assign the roles of classes to team members

Each member has one or more classes

distribute CRC cards collaborators to different persons use domain experts for classes if possible rotate assignments from session to session

3. Rehearse the scenario

Execute the scenario with team members announcing what affected classes are doing

Stick to the scenario

Limit the session time ( <= X )

Use conscious, deliberate problem-solving activities 1. Warm up Prepare every session for effective group work by breaking down inhibitions Use games, puzzles, brainteasers, mock brainstorming on "fun" topic. Use "go-around" review of activities since last session (use if organizational culture discourages above) 2.Enactment Act out each scenario 3. Assessment Build lists of problems encountered Evaluate problems found

 

6. Perform final scenario