|
|
DAST: The Diagnostic Approach to Software Testing Every test manager knows the pain of testing in a chaotic environment. The DAST (Diagnostic Approach to Software Testing) process allows you to cut through the chaos by implementing a strategic way to test products and releases, even when you don't have good product requirements or documentation. Founded on the premise of asking systematic questions to build test cases, Hung Nguyen takes participants through the process, which ultimately leads to valid requirements, specifications, and test cases.
|
Hung Nguyen, LogiGear Corporation
|
|
|
Enjoying the Perks of Model-Based Testing Software testing demands the use of some model to guide such test tasks as selecting test inputs, validating
the adequacy of tests, and gaining insight into test effectiveness. Most testers gradually build a mental
model of the system under test, which would enable them to further understand and better test its many
functions. Explicit models, being formal and precise representations of a tester’s perception of a program,
are excellent shareable, reusable vehicles of communication between and among testers and other teams
and of automation for many tasks that are normally tedious and labor-intensive.
|
Ibrahim K. El-Far, Florida Institute of Technology
|
|
|
Software Code Inspection for Defect Prevention Thousands of hours are spent testing, but most software professionals find that traditional testing simply isn't enough to ensure code quality. This presentation gives software professionals a complementary approach: software inspection. Learn how software inspection differs from traditional testing, and gain an understanding of principal inspection techniques.
|
Jasper Kamperman, Reasoning
|
|
|
Is Quality Negotiable? Experiences of an eXtreme Programming Tester If you want a higher quality product in an eXtreme Programming (XP) project, you must be prepared to pay a higher price. We make decisions and compromises based on quality versus cost every day. Extreme programming teams are driven to do their best work, but customers have the right to specify and pay for only the level of quality they require. This presentation explores ways to resolve these two potentially conflicting points of view.
|
Lisa Crispin, BoldTech Systems
|
|
|
STARWEST 2001: Bug Hunting: Going on a Software Safari This presentation is about bugs: where they hide, how you find them, and how you tell other people they exist so they can be fixed. Explore the habitats of the most common types of software bugs. Learn how to make bugs more likely to appear and discover ways to present information about the bugs you find to ensure they get fixed. Drawing on real-world examples of bug reports, Elisabeth Hendrickson reveals tips and techniques for capturing the wiliest and most squirmy critters crawling around in your software.
|
Elisabeth Hendrickson, Quality Tree Software
|
|
|
Introduction to Usability Testing What is usability? Why is it important? If these questions wake you in the middle of the night, then this presentation is for you. Cheryl Nesta discusses the relevance of usability testing within the broad framework of quality assurance and appropriate expectations based on its uses and applicability. Explore methodology, process flow, goal identification, and definition. Real-world examples create a hands-on introductory experience.
|
Cheryl L. Nesta, Vanteon
|
|
|
The Global Challenge: Quality Assurance for Worldwide Markets Many software applications are hosted in worldwide data centers, simultaneously launched with multiple language user interfaces, and continuously upgraded in rolling release cycles. Yet few software development organizations have a clear strategy for testing internationalized (I18N) products. Join presenter Steve Nemzer for an insider's view into the fascinating cultural, technical, and linguistic challenges faced by today's internationalization engineers.
|
Steve Nemzer, VeriTest
|
|
|
STAREAST 2001: The Power of Retrospectives to Improve Testing Testing is a tough job! Most test professionals learn the hard way what works and what doesn't. Retrospectives are focused, facilitated reviews of a defined piece of work. Learn how software project retrospectives are used as a test process improvement technique to capture the essence of a work, provide closure, and establish a springboard for active improvement in an organization.
|
Esther Derby, Esther Derby Associates, Inc
|
|
|
A Common Sense Approach to Statistical Process Control As maturing software organizations begin using statistical process control (SPC) techniques to stabilize processes and manage quality, it's imperative that their SPC implementation approach be carefully considered, especially since it involves the use of statistical analysis techniques that are unfamiliar to most people. This presentation describes an approach to implementing SPC that maximizes project personnel involvement through creative delegation, provides for the timely utilization of the data, and keeps management well informed but not overburdened.
|
Steven H. Lett, The David Consulting Group
|
|
|
Problem Resolution Cycle Time Optimization No matter how well we plan and execute software development, defects are generated and can escape to the customers. Failure to quickly resolve software problems leads to negative consequences for our customers and increases internal business costs. A quick deterministic
method to prioritize problems and implement their solution helps to reduce cycle time and costs. Achieving this goal requires several steps. The first is to determine a model that links problem resolution performance to institutional variables and problem characteristics. Statistical Design of Experiments (DOE) is a tool that provides data requirements for estimating the impacts of these variables on problem resolution. Once data has been gathered the results of statistical analysis can be input into a mathematical optimization model to guide the organization.
This paper describes such an analysis.
|
Don Porter, Motorola
|
