Agile Analysis with Use Cases: Balancing Utility with Simplicity May Program Guest Speaker: Ted Husted May 7, 2009 ROCHESTER, NY Chapter

Agenda 1. President’s Welcome and Chapter Update 2. Upcoming Programs 3. May Program with Guest Speaker Ted Husted © International Institute of Business Analysis™

1. President’s Welcome and Chapter Update

2. Upcoming Programs

3. May Program with Guest Speaker Ted Husted

Chapter Update 1. Chapter Board of Director Elections 2. Chapter Charter 3. Chapter Membership 4. Chapter's social networks to join 5. Chapter Surveys 6. Volunteer Opportunities Chapter Website: rochesterny.theiiba.org © International Institute of Business Analysis™

1. Chapter Board of Director Elections

2. Chapter Charter

3. Chapter Membership

4. Chapter's social networks to join

5. Chapter Surveys

6. Volunteer Opportunities

Chapter Website: rochesterny.theiiba.org

Upcoming Programs Thursday, 6/4 – Chapter Launch Dinner Celebration and Special Guest Speaker Ernest Hicks on Effective Communication at Sanibel Cottage Thursday, 7/16 – Summer Networking (i.e. – Happy Hour  ) at Pomodoro Grill Thursday, 8/13 – Summer Networking at Pomodoro Grill Thursday, 9/24 – Requirements Management Lunch Program with Guest speaker David Walker from Borland at Sanibel Cottage © International Institute of Business Analysis™

Thursday, 6/4 – Chapter Launch Dinner Celebration and Special Guest Speaker Ernest Hicks on Effective Communication at Sanibel Cottage

Thursday, 7/16 – Summer Networking (i.e. – Happy Hour  ) at Pomodoro Grill

Thursday, 8/13 – Summer Networking at Pomodoro Grill

Thursday, 9/24 – Requirements Management Lunch Program with Guest speaker David Walker from Borland at Sanibel Cottage

Upcoming Programs Thursday, 10/22 – Lunch event with Matt Smith from iRise at Sanibel Cottage Thursday, 11/19 – Lunch event at Sanibel Cottage Thursday, 12/10 – Holiday Party at Sanibel Cottage © International Institute of Business Analysis™

Thursday, 10/22 – Lunch event with Matt Smith from iRise at Sanibel Cottage

Thursday, 11/19 – Lunch event at Sanibel Cottage

Thursday, 12/10 – Holiday Party at Sanibel Cottage

Agile Analysis with Use Cases Balancing Simplicity with Utility Presented by Ted Husted VanDamme Associates, Inc. twitter.com/TedHusted

How is Pong like a Use Case?

How do we play use case? System sends puck toward player. Player moves paddle to meet puck. Puck misses paddle. System increments score for other player. System resets acceleration factor. Round repeats for other player.

System sends puck toward player.

Player moves paddle to meet puck.

Puck misses paddle.

System increments score for other player.

System resets acceleration factor.

Round repeats for other player.

How do we play use case? System sends puck toward player. Player moves paddle to meet puck. Puck misses paddle. System increments score for other player. System resets acceleration factor. Round repeats for other player.

System sends puck toward player.

Player moves paddle to meet puck.

Puck misses paddle.

System increments score for other player.

System resets acceleration factor.

Round repeats for other player.

How do we play use case? System sends puck toward player. Player moves paddle to meet puck. Puck misses paddle. System increments score for other player. System resets acceleration factor. Round repeats for other player.

System sends puck toward player.

Player moves paddle to meet puck.

Puck misses paddle.

System increments score for other player.

System resets acceleration factor.

Round repeats for other player.

How do we play use case? System sends puck toward player. Player moves paddle to meet puck. Puck misses paddle. System increments score for other player. System resets acceleration factor. Round repeats for other player.

System sends puck toward player.

Player moves paddle to meet puck.

Puck misses paddle.

System increments score for other player.

System resets acceleration factor.

Round repeats for other player.

How do we play use case? System sends puck toward player. Player moves paddle to meet puck. Puck misses paddle. System increments score for other player. System resets acceleration factor. Round repeats for other player.

System sends puck toward player.

Player moves paddle to meet puck.

Puck misses paddle.

System increments score for other player.

System resets acceleration factor.

Round repeats for other player.

How do we play use case? System sends puck toward player. Player moves paddle to meet puck. Puck misses paddle. System increments score for other player. System resets acceleration factor. Round repeats for other player.

System sends puck toward player.

Player moves paddle to meet puck.

Puck misses paddle.

System increments score for other player.

System resets acceleration factor.

Round repeats for other player.

How do we play use case? System sends puck toward player. Player moves paddle to meet puck. Puck misses paddle. System increments score for other player. System resets acceleration factor. Round repeats for other player.

System sends puck toward player.

Player moves paddle to meet puck.

Puck misses paddle.

System increments score for other player.

System resets acceleration factor.

Round repeats for other player.

Is that all there is? 2a Puck trajectory is too steep 2b Puck angles for a corner shot 3a Player returns puck 3b Puck intersects center segment 3c Puck intersects outer segment 5a Player wins

2a Puck trajectory is too steep

2b Puck angles for a corner shot

3a Player returns puck

3b Puck intersects center segment

3c Puck intersects outer segment

5a Player wins

Is that all there is? 2a Puck trajectory is too steep 2b Puck angles for a corner shot 3a Player returns puck 3b Puck intersects center segment 3c Puck intersects outer segment 5a Player wins

2a Puck trajectory is too steep

2b Puck angles for a corner shot

3a Player returns puck

3b Puck intersects center segment

3c Puck intersects outer segment

5a Player wins

Is that all there is? 2a Puck trajectory is too steep 2b Puck angles for a corner shot 3a Player returns puck 3b Puck intersects center segment 3c Puck intersects outer segment 5a Player wins

2a Puck trajectory is too steep

2b Puck angles for a corner shot

3a Player returns puck

3b Puck intersects center segment

3c Puck intersects outer segment

5a Player wins

Is that all there is? 2a Puck trajectory is too steep 2b Puck angles for a corner shot 3a Player returns puck 3b Puck intersects center segment 3c Puck intersects outer segment 5a Player wins

2a Puck trajectory is too steep

2b Puck angles for a corner shot

3a Player returns puck

3b Puck intersects center segment

3c Puck intersects outer segment

5a Player wins

Is that all there is? 2a Puck trajectory is too steep 2b Puck angles for a corner shot 3a Player returns puck 3b Puck intersects center segment 3c Puck intersects outer segment 5a Player wins

2a Puck trajectory is too steep

2b Puck angles for a corner shot

3a Player returns puck

3b Puck intersects center segment

3c Puck intersects outer segment

5a Player wins

Is that all there is? 2a Puck trajectory is too steep 2b Puck angles for a corner shot 3a Player returns puck 3b Puck intersects center segment 3c Puck intersects outer segment 5a Player wins

2a Puck trajectory is too steep

2b Puck angles for a corner shot

3a Player returns puck

3b Puck intersects center segment

3c Puck intersects outer segment

5a Player wins

How do we win? 2a Puck trajectory is too steep 2b Puck angles for a corner shot 3a Player returns puck 3b Puck intersects center segment 3c Puck intersects outer segment 5a Player wins

2a Puck trajectory is too steep

2b Puck angles for a corner shot

3a Player returns puck

3b Puck intersects center segment

3c Puck intersects outer segment

5a Player wins

How do we win? 2a Puck trajectory is too steep 2b Puck angles for a corner shot 3a Player returns puck 3b Puck intersects center segment 3c Puck intersects outer segment 5a Player wins 1. Score exceeds the maximum number of points. 2. System presents game over banner. 3. End.

2a Puck trajectory is too steep

2b Puck angles for a corner shot

3a Player returns puck

3b Puck intersects center segment

3c Puck intersects outer segment

5a Player wins

1. Score exceeds the maximum number of points. 2. System presents game over banner. 3. End.

What about diagrams?

How is a user story different?

What’s wrong with this story? Pong is a two-dimensional sports game which simulates table tennis. The player controls an in-game paddle by moving it vertically across the left side of the screen, and can compete against either a computer controlled opponent or another player controlling a second paddle on the opposing side. Players use the paddles to hit a ball back and forth. The aim is for a player to earn more points than the opponent; points are earned when one fails to return the ball to the other.

Pong is a two-dimensional sports game which simulates table tennis.

The player controls an in-game paddle by moving it vertically across the left side of the screen, and can compete against either a computer controlled opponent or another player controlling a second paddle on the opposing side.

Players use the paddles to hit a ball back and forth.

The aim is for a player to earn more points than the opponent; points are earned when one fails to return the ball to the other.

What’s wrong with this story? Pong is a two-dimensional sports game which simulates table tennis. The player controls an in-game paddle by moving it vertically across the left side of the screen, and can compete against either a computer controlled opponent or another player controlling a second paddle on the opposing side. Players use the paddles to hit a ball back and forth. The aim is for a player to earn more points than the opponent; points are earned when one fails to return the ball to the other.

Pong is a two-dimensional sports game which simulates table tennis.

The player controls an in-game paddle by moving it vertically across the left side of the screen, and can compete against either a computer controlled opponent or another player controlling a second paddle on the opposing side.

Players use the paddles to hit a ball back and forth.

The aim is for a player to earn more points than the opponent; points are earned when one fails to return the ball to the other.

What’s wrong with this story? Pong is a two-dimensional sports game which simulates table tennis. The player controls an in-game paddle by moving it vertically across the left side of the screen, and can compete against either a computer controlled opponent or another player controlling a second paddle on the opposing side. Players use the paddles to hit a ball back and forth. The aim is for a player to earn more points than the opponent; points are earned when one fails to return the ball to the other.

Pong is a two-dimensional sports game which simulates table tennis.

The player controls an in-game paddle by moving it vertically across the left side of the screen, and can compete against either a computer controlled opponent or another player controlling a second paddle on the opposing side.

Players use the paddles to hit a ball back and forth.

The aim is for a player to earn more points than the opponent; points are earned when one fails to return the ball to the other.

What’s wrong with this story? Pong is a two-dimensional sports game which simulates table tennis. The player controls an in-game paddle by moving it vertically across the left side of the screen, and can compete against either a computer controlled opponent or another player controlling a second paddle on the opposing side. Players use the paddles to hit a ball back and forth. The aim is for a player to earn more points than the opponent; points are earned when one fails to return the ball to the other.

Pong is a two-dimensional sports game which simulates table tennis.

The player controls an in-game paddle by moving it vertically across the left side of the screen, and can compete against either a computer controlled opponent or another player controlling a second paddle on the opposing side.

Players use the paddles to hit a ball back and forth.

The aim is for a player to earn more points than the opponent; points are earned when one fails to return the ball to the other.

What can go wrong with this story?

Agile Analysis with Use Cases A mainstay of conventional requirements gathering, use cases can ease the transition to agile methodologies. In this practical program, we explore: how to write uses cases how to adapt uses cases to agile projects how to automate acceptance testing with use cases

A mainstay of conventional requirements gathering, use cases can ease the transition to agile methodologies.

In this practical program, we explore:

how to write uses cases

how to adapt uses cases to agile projects

how to automate acceptance testing with use cases

What’s our agenda?

Do you take questions? Slides Available at slideshare.net / rochesterny.theiiba.org

How to write use cases The Why, What, Where, When, Who, and How of use cases

The Why, What, Where, When, Who, and How of use cases

Why? Actors Interact

Why? Change Happens

Why? Systems Adapt

What? Main Scenario

First Draft System sends puck toward player. Player moves paddle to meet puck. Puck intersects paddle … Second Draft System sends puck toward player. Player moves paddle to meet puck. Puck misses paddle. … What? Main Scenario

First Draft

System sends puck toward player.

Player moves paddle to meet puck.

Puck intersects paddle

…

Second Draft

System sends puck toward player.

Player moves paddle to meet puck.

Puck misses paddle.

…

What? Extensions

What? Annotations

What? Annotations

What? Annotations 1a Browser does not provide cookie System redirects to login page and passes original URL through a parameter System authenticates user (UC-4) Return at Step 1

1a Browser does not provide cookie

System redirects to login page and passes original URL through a parameter

System authenticates user (UC-4)

Return at Step 1

What? Annotations 1a Browser does not provide cookie System redirects to login page and passes original URL through a parameter System authenticates user (UC-4) Return at Step 1

1a Browser does not provide cookie

System redirects to login page and passes original URL through a parameter

System authenticates user (UC-4)

Return at Step 1

What? Annotations 1a Browser does not provide cookie System redirects to login page and passes original URL through a parameter https:// www.domain.org/sso/ Signon.aspx ? redirectUrl = default.aspx System authenticates user (UC-4) Return at Step 1

1a Browser does not provide cookie

System redirects to login page and passes original URL through a parameter

https:// www.domain.org/sso/ Signon.aspx ? redirectUrl = default.aspx

System authenticates user (UC-4)

Return at Step 1

What? Annotations Extensions 1a Browser does not provide cookie System redirects to login page and passes original URL through a parameter System authenticates user (UC-4) Return at Step 1 Annotations 1a1 Example URL: https:// www.domain.org/sso/ Signon.aspx ? redirectUrl = default.aspx

Extensions

1a Browser does not provide cookie

System redirects to login page and passes original URL through a parameter

System authenticates user (UC-4)

Return at Step 1

Annotations

1a1 Example URL: https:// www.domain.org/sso/ Signon.aspx ? redirectUrl = default.aspx

Where? Can use cases do it all?

Where? Requirements Outline Vision and Scope Document Use Cases Software Requirements Specification Business Rules

Vision and Scope Document

Use Cases

Software Requirements Specification

Business Rules

Where? Requirements Outline Findings Requirements Use Cases Technical Specification

Findings

Requirements

Use Cases

Technical Specification

When? Requirements Analysis

When? Organize and Allocate

Who? You …

Who? Them …

Who? Us!

How? Use Case Workflow Identify the actors Identify the use cases Identify actor/use case relationships Outline use cases Refine use cases

Identify the actors

Identify the use cases

Identify actor/use case relationships

Outline use cases

Refine use cases

How? Use Case Workflow Identify the actors Identify the use cases Identify actor/use case relationships Outline use cases Refine use cases

Identify the actors

Identify the use cases

Identify actor/use case relationships

Outline use cases

Refine use cases

How? Use Case Workflow Identify the actors Identify the use cases Identify actor/use case relationships Outline use cases Refine use cases

Identify the actors

Identify the use cases

Identify actor/use case relationships

Outline use cases

Refine use cases

How? Use Case Workflow Identify the actors Identify the use cases Identify actor/use case relationships Outline use cases Refine use cases

Identify the actors

Identify the use cases

Identify actor/use case relationships

Outline use cases

Refine use cases

How? Use Case Workflow Identify the actors Identify the use cases Identify actor/use case relationships Outline use cases Refine use cases

Identify the actors

Identify the use cases

Identify actor/use case relationships

Outline use cases

Refine use cases

How? Use Case Workflow Identify the actors Identify the use cases Identify actor/use case relationships Outline use cases Refine use cases

Identify the actors

Identify the use cases

Identify actor/use case relationships

Outline use cases

Refine use cases

How? Use Case Template Name Brief description Actors Main Scenario Extensions Pre-conditions Post-conditions Other stakeholders System/sub-system Special requirements

Name

Brief description

Actors

Main Scenario

Extensions

Pre-conditions

Post-conditions

Other stakeholders

System/sub-system

Special requirements

How? Use Case Template Name Brief description Actors Main Scenario Extensions Pre-conditions Post-conditions Other stakeholders System/sub-system Special requirements

Name

Brief description

Actors

Main Scenario

Extensions

Pre-conditions

Post-conditions

Other stakeholders

System/sub-system

Special requirements

How? Right-size templates Name Brief description Actors Main Scenario Extensions Pre-conditions Post-Conditions Other stakeholders System/sub-system Special requirements

Name

Brief description

Actors

Main Scenario

Extensions

Pre-conditions

Post-Conditions

Other stakeholders

System/sub-system

Special requirements

Adapt?

Adapt? Agile

Adapt? Backlog Name Brief description Actors Main Scenario Extensions Pre-conditions Post-conditions Other stakeholders System/sub-system Special requirements

Name

Brief description

Actors

Main Scenario

Extensions

Pre-conditions

Post-conditions

Other stakeholders

System/sub-system

Special requirements

Adapt? Iteration Planning Name Brief description Actors Main Scenario Extensions Pre-conditions Post-conditions Other stakeholders System/sub-system Special requirements

Name

Brief description

Actors

Main Scenario

Extensions

Pre-conditions

Post-conditions

Other stakeholders

System/sub-system

Special requirements

Agile? Backlog Pruning Name Brief description Actors Main Scenario Extensions Pre-conditions Post-conditions Other stakeholders System/sub-system Special requirements

Name

Brief description

Actors

Main Scenario

Extensions

Pre-conditions

Post-conditions

Other stakeholders

System/sub-system

Special requirements

Agile? Epic Iteration Name Brief description Actors Main Scenario Extensions Pre-conditions Post-conditions Other stakeholders System/sub-system Special requirements

Name

Brief description

Actors

Main Scenario

Extensions

Pre-conditions

Post-conditions

Other stakeholders

System/sub-system

Special requirements

Adapt? Training Materials

Adapt? Quality Assurance

Adapt? Testing Open Signin Page Signin page: http:// domain.org/sso / Enter credentials Username: mg Password: va123123 Process Succeeds System Creates Cookie System Redirects

Open Signin Page

Signin page: http:// domain.org/sso /

Enter credentials

Username: mg

Password: va123123

Process Succeeds

System Creates Cookie

System Redirects

Adapt? Testing Open Signin Page Signin page: http:// domain.org/sso / Enter credentials Username: mg Password: va123123 Process Succeeds System Creates Cookie System Redirects

Open Signin Page

Signin page: http:// domain.org/sso /

Enter credentials

Username: mg

Password: va123123

Process Succeeds

System Creates Cookie

System Redirects

Adapt? Testing Open Signin Page Signin page: http:// domain.org/sso / Enter credentials Username: mg Password: va123123 Process Succeeds System Creates Cookie System Redirects

Open Signin Page

Signin page: http:// domain.org/sso /

Enter credentials

Username: mg

Password: va123123

Process Succeeds

System Creates Cookie

System Redirects

Adapt? Testing Open Signin Page Signin page: http:// domain.org/sso / Enter credentials Username: mg Password: va123123 Process Succeeds System Creates Cookie System Redirects

Open Signin Page

Signin page: http:// domain.org/sso /

Enter credentials

Username: mg

Password: va123123

Process Succeeds

System Creates Cookie

System Redirects

Adapt? Testing Open Signin Page Signin page: http:// domain.org/sso / Enter credentials Username: mg Password: va123123 Process Succeeds System Creates Cookie System Redirects

Open Signin Page

Signin page: http:// domain.org/sso /

Enter credentials

Username: mg

Password: va123123

Process Succeeds

System Creates Cookie

System Redirects

Automate?

Automate? Testing

Automate? Testing

Adapt? Testing http:// seleniumhq.org /

Resources http://www.rose-hulman.edu/class/csse/csse371/csse371-2007-2008/Lectures/usecases.ppt

Any questions? Slides Available at slideshare.net / rochesterny.theiiba.org

About Ted Husted Co-author of JUnit in Action (1 st Edition) Speaker at Ajax Experience, ApacheCon Business Analyst, VanDamme Associates Member, International Institute for Business Analysis (IIBA) Executive VP Elect, Rochester NY IIBA twitter.com/TedHusted

Co-author of JUnit in Action (1 st Edition)

Speaker at Ajax Experience, ApacheCon

Business Analyst, VanDamme Associates

Member, International Institute for Business Analysis (IIBA)

Executive VP Elect, Rochester NY IIBA

twitter.com/TedHusted

Inventor of Pong, Alan Alcorn Disclaimer Alan Alcorn is not Ted’s cousin, but he did invent Pong, though without the help of use cases. Use cases and Pong can both make you cross-eyed

Disclaimer

Alan Alcorn is not Ted’s cousin,

but he did invent Pong,

though without the help of use cases.

Thank you Ted! Next Chapter Meeting: June 4, 2009 with Ernest Hicks “ A speaker you don’t want to miss”

Thank you Ted!

Next Chapter Meeting:

June 4, 2009

with Ernest Hicks

“ A speaker you don’t want to miss”