Top Banner
A better way to define software requirements & test cases powersto ry For PowerPoint Toronto ALM User Group
16
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Toronto alm v1

A better way to define software

requirements & test cases

powerstory

For PowerPoint

Toronto ALM User Group

Page 2: Toronto alm v1

First some questions…

RolesBAs ?UI/UX?Developer?Scrum Master?Product Manager?

Requirements ManagementUse TFS ?Use another tool?

Test Case ManagementUse TFSUse another tool?

Page 3: Toronto alm v1

main flow1. -----------2. ---------3. ---------------

alternate flows3.1 ------------------- 3.1.1 ---------- 3.1.2 -------------

3.2 --------------- 3.2.1 -----------

Use Cases

UI Wireframes

A

B

D E

F

Test CasesTest Case 11. -----------2. ---------3. ---------------

Test Case 21. -----------2. ---------3.1 ------------------- 3.1.1 ---------- 3.1.2 -------------

Test Case 31. -----------2. ---------3.2 --------------- 3.2.1 -----------

C

A B C

D E

F

A B

A B

UI Storyboards

Traditional requirements & Test specifications

Page 4: Toronto alm v1
Page 5: Toronto alm v1

Use Cases

UI WireframesUI Storyboards

User Stories

inconsistencies

Test Cases

…in other words

…often duplicate requirements,such as “user steps and system response

flow”

confusion

…also suffer from “translation errors” from one deliverable to the next.

wasted budget

rework

Page 6: Toronto alm v1

Use Cases

UI WireframesUI Storyboards

User Stories Test Cases

What if we took these specifications..

…combine some of them into

single integrated deliverable, that

removes the duplication and

translation errors

Use Case Storyboard

…and automatically

generated your Test

CasesTest Case

Generation..with TFS

Integration

Page 7: Toronto alm v1

powerstory

For PowerPoint

..that is what powerstory does

Page 8: Toronto alm v1

powerstory

For PowerPoint

So what is a Use Case Storyboard

UI Mockup / WireframeUse CaseEditormain flow

Alternate flows

Associate each “use case step” with a UI Mockup / wireframe

UI Control

s Library

Drag and Drop to create your UI

Mockup

based on PowerPoint

Page 9: Toronto alm v1

Communicate better through requirements simulation

Steps Navigator / Editor

Page 10: Toronto alm v1

…or using navigation links & titles

Optionally have navigation links

automatically inserted on the slides

Optionally have slide titles synced with step

text

Page 11: Toronto alm v1

Generate Test Cases into MS Team Foundation Server

Page 12: Toronto alm v1

Automatic Traceability within Team Foundation Server

Page 13: Toronto alm v1

Generate Test Cases into MS Excel – import to HP QC

Page 14: Toronto alm v1

Generate Test Cases into MS Word

Page 15: Toronto alm v1

powerstory

For PowerPoint

Saves you significant project time and budget,

by…

A better way to define software requirements & test cases!

…communicating requirements more clearly

…generating test cases automatically

…removing requirements duplication and translation errors

Page 16: Toronto alm v1

demos

Use Case StoryboardsSteps EditorUI Control LibraryAdd your own UI ControlsShare UI ControlsSimulationView OptionsPowerPoint templates for reuse

Test Case Gen For Word and Excel

TFS IntegrationStart with TFS workitemAttach PPT file to a workitem Link to shared file – eg. skydriveTest Case Generation into TFS