Your SlideShare is downloading. ×
PowerStory - a better way to define requirements and test cases
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

PowerStory - a better way to define requirements and test cases

299

Published on

PowerStory - a better way to define requirements and test cases. This presentation gives q quick overview of powerstory and also highlights its integration with Team Foundation Server (TFS)

PowerStory - a better way to define requirements and test cases. This presentation gives q quick overview of powerstory and also highlights its integration with Team Foundation Server (TFS)

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
299
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. powerstorya better way to define requirements and test cases
  • 2. powerstoryBusiness Solutions Business valuechallenges Create “Use Case Storyboards” • Keeps your use cases, uiPoorly defined and communicated mockups and storyboards in syncrequirements wastes time and • Easier for your team to Reduce Rework caused bymoney understand the requirements miss-aligned or Generate Test Cases from “Use Case misunderstood requirementsTraditional approaches require themanual creation of functional test Storyboards”cases • Save significant Time and $ Significant Testing BudgetIt’s too hard to get reviewer Rich integration with Team savings, through automatedfeedback and understanding with Foundation Server test case generationcurrent approaches • Attach to workitem • Automatic traceability betweenUse Cases, UI Mockups and requirements and test cases Based on PowerPoint, makingStoryboards end up it easy to adopt and gaincommunicating conflicting Based on PowerPoint for easy value quicklyrequirements adoption and us
  • 3. Define your Use Case Main Flow and Alternate Flow steps within the powerstory steps editor plugin for powerpoint.powerstory Each use case step is associated with a UI Mockup / wireframe
  • 4. Powerstory allows you to define the flow of the use case storyboardpowerstory MS VS Storyboarding allows you to define the UI Mockups for each use case storyboard step
  • 5. powerstory navigator makes it easy to walk through the main and alternate flows of the use case storyboardpowerstory Optionally have powerstory insert navigation links right on your slides, and sync slide titles with use case step text
  • 6. Generate a Test Case for each unique path through the main flow and alternate flowsExport these test cases to TFS, Word & Excel
  • 7. Automatic traceability between generated test cases and requirements workitems
  • 8. Automatically identifies “actions” and “expected results”UI Mockups from Use Case Storyboard are attached to test stpes
  • 9. Export test cases to WordExport test cases to Excel – good for importing to other test management platforms
  • 10. Attach your Use Case Storyboard to TFS Workitems One click to update workitemattachment with “new version”
  • 11. powerstory

×