Agile Use Cases: Balancing Utility with Simplicity - May 2009
Download as PPT, PDF7 likes1,000 views
The document outlines the agenda for a chapter meeting featuring guest speaker Ted Husted, focusing on agile analysis and the use of use cases. It provides updates on chapter activities, upcoming events, and includes a practical exploration of writing and adapting use cases for agile projects. Additionally, it addresses how use cases can streamline requirements gathering and acceptance testing.
Agile Use Cases: Balancing Utility with Simplicity - May 2009
- 1. Agile Analysis with Use Cases: Balancing Utility with Simplicity May Program Guest Speaker: Ted Husted May 7, 2009 ROCHESTER, NY Chapter
- 2. Agenda 1. President’s Welcome and Chapter Update 2. Upcoming Programs 3. May Program with Guest Speaker Ted Husted © International Institute of Business Analysis™
- 3. 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™
- 4. 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™
- 5. 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™
- 6. Agile Analysis with Use Cases Balancing Simplicity with Utility Presented by Ted Husted VanDamme Associates, Inc. twitter.com/TedHusted
- 7. How is Pong like a Use Case?
- 8. 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.
- 9. 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.
- 10. 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.
- 11. 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.
- 12. 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.
- 13. 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.
- 14. 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.
- 15. 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
- 16. 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
- 17. 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
- 18. 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
- 19. 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
- 20. 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
- 21. 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
- 22. 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.
- 24. How is a user story different?
- 25. 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.
- 26. 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.
- 27. 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.
- 28. 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.
- 29. What can go wrong with this story?
- 30. 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
- 32. Do you take questions? Slides Available at slideshare.net / rochesterny.theiiba.org
- 33. How to write use cases The Why, What, Where, When, Who, and How of use cases
- 38. 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
- 39. What? Extensions
- 42. 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
- 43. 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
- 44. 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
- 45. 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
- 46. Where? Can use cases do it all?
- 47. Where? Requirements Outline Vision and Scope Document Use Cases Software Requirements Specification Business Rules
- 48. Where? Requirements Outline Findings Requirements Use Cases Technical Specification
- 50. When? Organize and Allocate
- 51. Who? You …
- 52. Who? Them …
- 53. Who? Us!
- 54. How? Use Case Workflow Identify the actors Identify the use cases Identify actor/use case relationships Outline use cases Refine use cases
- 55. How? Use Case Workflow Identify the actors Identify the use cases Identify actor/use case relationships Outline use cases Refine use cases
- 56. How? Use Case Workflow Identify the actors Identify the use cases Identify actor/use case relationships Outline use cases Refine use cases
- 57. How? Use Case Workflow Identify the actors Identify the use cases Identify actor/use case relationships Outline use cases Refine use cases
- 58. How? Use Case Workflow Identify the actors Identify the use cases Identify actor/use case relationships Outline use cases Refine use cases
- 59. How? Use Case Workflow Identify the actors Identify the use cases Identify actor/use case relationships Outline use cases Refine use cases
- 60. How? Use Case Template Name Brief description Actors Main Scenario Extensions Pre-conditions Post-conditions Other stakeholders System/sub-system Special requirements
- 61. How? Use Case Template Name Brief description Actors Main Scenario Extensions Pre-conditions Post-conditions Other stakeholders System/sub-system Special requirements
- 62. How? Right-size templates Name Brief description Actors Main Scenario Extensions Pre-conditions Post-Conditions Other stakeholders System/sub-system Special requirements
- 63. Adapt?
- 64. Adapt? Agile
- 65. Adapt? Backlog Name Brief description Actors Main Scenario Extensions Pre-conditions Post-conditions Other stakeholders System/sub-system Special requirements
- 66. Adapt? Iteration Planning Name Brief description Actors Main Scenario Extensions Pre-conditions Post-conditions Other stakeholders System/sub-system Special requirements
- 67. Agile? Backlog Pruning Name Brief description Actors Main Scenario Extensions Pre-conditions Post-conditions Other stakeholders System/sub-system Special requirements
- 68. Agile? Epic Iteration Name Brief description Actors Main Scenario Extensions Pre-conditions Post-conditions Other stakeholders System/sub-system Special requirements
- 71. Adapt? Testing Open Signin Page Signin page: http:// domain.org/sso / Enter credentials Username: mg Password: va123123 Process Succeeds System Creates Cookie System Redirects
- 72. Adapt? Testing Open Signin Page Signin page: http:// domain.org/sso / Enter credentials Username: mg Password: va123123 Process Succeeds System Creates Cookie System Redirects
- 73. Adapt? Testing Open Signin Page Signin page: http:// domain.org/sso / Enter credentials Username: mg Password: va123123 Process Succeeds System Creates Cookie System Redirects
- 74. Adapt? Testing Open Signin Page Signin page: http:// domain.org/sso / Enter credentials Username: mg Password: va123123 Process Succeeds System Creates Cookie System Redirects
- 75. Adapt? Testing Open Signin Page Signin page: http:// domain.org/sso / Enter credentials Username: mg Password: va123123 Process Succeeds System Creates Cookie System Redirects
- 76. Automate?
- 79. Adapt? Testing http:// seleniumhq.org /
- 81. Any questions? Slides Available at slideshare.net / rochesterny.theiiba.org
- 82. 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
- 83. 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
- 84. Thank you Ted! Next Chapter Meeting: June 4, 2009 with Ernest Hicks “ A speaker you don’t want to miss”
Editor's Notes
- #2: June 9, 2009 © International Institute of Business Analysis