Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Standard view
Full view
of .
Save to My Library
Look up keyword
Like this
5Activity
P. 1
Use Case Levels of Test: A Four-Step Strategy For Budgeting Time And Innovation in Software Test Design

Use Case Levels of Test: A Four-Step Strategy For Budgeting Time And Innovation in Software Test Design

Ratings: (0)|Views: 113 |Likes:
Published by Richard Denney
Every student in school – from elementary to graduate – is familiar with the angst of taking tests, hearing the dreaded line "Times up, put your pencils down!", followed by the that feeling of regret as you think "If only I hadn't spent so much time on that one question!"

I'd like you to consider that writing tests for software is a bit like taking tests in school. Both are tasks typically done in a finite, allotted amount of time, so it's best to have a strategy for using your time wisely, and knowing what techniques work well (or don't!) on various problem types.

Innovation and ways of working smarter often arise from the “cross-pollination” of ideas from multiple disciplines of software engineering. This book presents a four-step strategy to budgeting time and innovative test design based on the idea of use case levels of test combined with high bang for the buck ideas from software testing, Quality Function Deployment (QFD), software reliability’s operational profiles, Structured Analysis and Design’s C.R.U.D. matrix, and formal methods like model-based specification, Programming in Logic (Prolog) and discrete math for testers.

The goal of this “cross-pollination” is to provide you the tester with a strategy such that when you hear "Times up, put your pencils down!", you can relax knowing you have used your time for writing tests for your system or application wisely.
Every student in school – from elementary to graduate – is familiar with the angst of taking tests, hearing the dreaded line "Times up, put your pencils down!", followed by the that feeling of regret as you think "If only I hadn't spent so much time on that one question!"

I'd like you to consider that writing tests for software is a bit like taking tests in school. Both are tasks typically done in a finite, allotted amount of time, so it's best to have a strategy for using your time wisely, and knowing what techniques work well (or don't!) on various problem types.

Innovation and ways of working smarter often arise from the “cross-pollination” of ideas from multiple disciplines of software engineering. This book presents a four-step strategy to budgeting time and innovative test design based on the idea of use case levels of test combined with high bang for the buck ideas from software testing, Quality Function Deployment (QFD), software reliability’s operational profiles, Structured Analysis and Design’s C.R.U.D. matrix, and formal methods like model-based specification, Programming in Logic (Prolog) and discrete math for testers.

The goal of this “cross-pollination” is to provide you the tester with a strategy such that when you hear "Times up, put your pencils down!", you can relax knowing you have used your time for writing tests for your system or application wisely.

More info:

Published by: Richard Denney on Jul 01, 2013
Copyright:Traditional Copyright: All rights reserved

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
See more
See less

08/03/2013

 
;
PQ@ 
 
AKQ@ 
 
O@Y@OQ 
 
CI 
 
R@QR 
 K
 
CPZ
$Q 
R@
RZKR@GV ICZ
 J
PBG@RFHG
FD@ KHB
HHCYKRFCH 
 
FH 
CIRWKZ@ 
@Q
B
@QFGH 
 
 
:
ACHR@HRQ 
 

Activity (5)

You've already reviewed this. Edit your review.
1 hundred reads
redfan11 liked this
rasguli liked this
myehia1976 liked this
bhn2you liked this

You're Reading a Free Preview

Download
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->