TrainingConferencesAbout UsContact UsAdvertiseSQE.comRSS Feed

StickyMinds.com: brain food for building better software

Log In
 Clarify Your Search Criteria

Tips on Using Our Search Feature(s)
 
StickyMinds.com Home
ResourcesTopicsCommunityPowerPassBlogs
Home  >  Detail: Test Design: Developing Test Cases from Use Cases




Jul/Aug 1999  (Vol. 1, Issue 4)
 Jul/Aug 1999 (Vol. 1, Issue 4)
Feature: Testing

Test Design: Developing Test Cases from Use Cases
By Ross Collard

Email This ContentGet a Short Link to This ContentAdd This Content to Your Favorites

Summary:
A use case is a sequence of actions performed by a system, which combined together produce a result of value to a system user. Use cases describe the "process flows" through a system based on its actual likely use, so the test cases derived from use cases are most useful in uncovering defects in the process flows during real-world use of the system. Here is an example of how a use case is used to derive and prioritize test cases.

 



Access the entire STQE and Better Software magazine archive of over 250 articles by supercharging your membership with a PowerPass!
Learn more about PowerPass.
 
 
About the Author Ross Collard is a consultant who currently is working on software testing and quality assurance projects for AT&T, Cisco, GE, Lucent, and the State of California. He teaches software testing for UC Berkeley. Ross has an MS in computer science from the California Institute of Technology and an MBA from Stanford. 



 
Ads By Google
What's This?
 
 



Home   |   Resources   |   Topics   |   Community   |   PowerPass



© 2010 StickyMinds.com. All rights reserved.
StickyMinds.com is a division of Software Quality Engineering.
Privacy Policy    Terms & Conditions    Link to StickyMinds.com    Feedback


Infosys

TechExcel, Inc.




STAREAST 


Better Software Conference