TUTO R IALS
Monday, June 8, 8:30am–12:00pm (Half-day Morning)
3.75
PDUs
Per Half-day
Tutorial
MF Get the Requirements Right—the First Time
Tim Lister, Atlantic Systems Guild, Inc.
One group—customers, users, and business—need a software system to help them work more efficiently or make more money, but they
don’t know how to build it. Another group—software developers and testers—know how to build the system, but they don’t know what
it is supposed to do. Bridging this gap is where requirements—the work products describing the system accurately and concisely while
at the same time not missing important customer and user needs—are essential. To get the requirements right the first time, you need
strategy, tactics, and a practical process for discovering the real requirements—which may not turn out to be what the users think they
need. Tim Lister presents a strategy to get accurate and explicit requirements, tactics to efficiently develop these requirements, and a process to keep
everything glued together when tackling a large, complex job. Take back an 85-page, annotated requirements specification template to help get your
requirements right—the first time.
MG Measurement and Metrics for Test Managers
Rick Craig, Software Quality Engineering
To be most effective, test managers must develop and use metrics to help direct the testing effort and make informed recommendations
about the software’s release readiness and associated risks. Because one important testing activity is to “measure” the quality of the
software, test managers must measure the results of both the development and testing processes. Collecting, analyzing, and using
metrics are complicated because many developers and testers are concerned that the metrics will be used against them. Join Rick Craig
as he addresses common metrics—measures of product quality, defect removal efficiency, defect density, defect arrival rate, and testing
status. Learn the guidelines for developing a test measurement program, rules of thumb for collecting data, and ways to avoid “metrics dysfunction.” Rick
identifies several metrics paradigms and discusses the pros and cons of each.
MH Configuration Management: Robust Processes for Fast Delivery
Bob Aiello, CM Best Practices Consulting
Robust configuration management (CM) practices are critical for creating continuous builds to support agile’s integration and testing
demands, and for rapidly packaging, releasing, and deploying applications into production. Classic CM—identifying system components,
controlling changes, reporting the system’s configuration, and auditing—won’t do the trick anym