|
|
Don't Just Find Bugs: Influencing the Defect Fixing Process In many projects, finding defects is easy but getting them fixed quickly and correctly can be a big problem. As a test professional armed with test plans and automated tools, you can detect and report reams of bugs. But in the end, product quality is not judged by the problems found, but by the problems fixed. Until a time when robots fix defects, testers must convince programmers to research and fix problems. How do you make certain that the important defects you find are corrected properly? How do you get and keep the attention of management to sell them on the fixes you think are essential? In this presentation, Margaret Ramsey discusses the people issues in reporting and selling your defects to both management and developers.
|
Margaret Ramsey, Software Process Innovators
|
|
|
Bug Reports That Make Sense Reporting a problem isn't enough. The more information you can provide the developer, the sooner the problem can be identified and fixed. Learn what developers need in a bug report, and how to create a good report versus a bad one. Explore the classification and severity of bugs and the importance of retesting before reporting.
|
Mary Decker, Aldebaron Financial Solutions
|
|
|
Bug Tracking in Chaos Whether you call them bugs, defects, issues, or Test Incident Reports (TIRs), a tight schedule with unrealistic project goals requires you to record, track, and report on software problems quickly and accurately. Based on experience with projects operating in chaos, Marc Rene presents some real-world examples of how TIR data was collected, tracked, and presented to management for a quick and concise status of a project.
|
Marc Rene, GTECH Corporation
|
|
|
Beyond the Bug Battles It is too easy to fall into fruitless battles over bugs. In many cases, the dispute really comes down to the fact that customers and developers have different ideas regarding what counts as a defect. Testers, on the other hand, are often stuck in the middle. The solution isn't to decide who's right but to find a way to acknowledge the different perspectives. In this presentation, learn two methods for increasing mutual understanding-helping testers and developers work together to create software of which they can be proud.
|
Bret Pettichord, Tivoli Systems
|
|
|
Improve Your Estimating Process--Beginning with a Proof of Concept Estimating is like the weather; everyone talks about it, but no one does anything about it. This presentation provides the techniques required to execute a Proof of Concept estimating model, allowing an organization to trial run the tools, techniques, and methods required to estimate projects more accurately and earlier in the lifecycle. Learn the key elements of this approach, and obtain templates to employ in your organization.
|
David Herron, The David Consulting Group, Inc.
|
|
|
Performance Evaluation and Measurement of Enterprise Applications Today's large-scale enterprise applications are all Web-enabled and complex in nature. Many users experience performance problems from day one. Performance evaluation and measurement via extensive testing is the only practical way to raise and address all issues prior to a successful deployment. Learn how to tackle performance and capacity issues with the appropriate testing strategy and scalable infrastructure/architecture.
|
Rakesh Radhakrishnan, Sun Microsystems
|
|
|
Our Experience Using Orthogonal Defect Classification Orthogonal Defect Classification (ODC) is a method of classifying and analyzing software defects. Using real-life experience, Barbara Hirsh discusses how Motorola successfully implemented ODC within their organization resulting in a framework for building a pervasive and cohesive defect prevention program. Learn the benefits of using ODC from the perspective of the developer, the tester, and the post-release analyst.
|
Barbara Hirsh, Motorola
|
|
|
Simple Software Defect Categorization for Defect Prevention Based on her experience with software development organizations at all five levels of the Capability Maturity Model (CMM), Barbara Kolkhorst outlines simple methods for documenting and categorizing defects and how to proceed with analysis for defect prevention. Learn how these simple methods can be implemented within your organization resulting in the prevention of significant numbers of software defects.
|
Barbara Kolkhorst, IBM
|
|
|
Critical Components of Asset Management Examine how Information Technology (IT) asset management methodologies can reduce your organization's IT budget between five and thirty-five percent. Kathy Shoop discusses the critical components to deploy, the challenges of implementing such a program, and the limitations of asset management tools such as spreadsheets and in-house development efforts. Discover the best practices for implementing an asset management initiative in your organization that will result in immediate cost savings.
|
Kathy Shoop, Janus Technologies, Inc.
|
|
|
A Comparison of IBM's and Hewlett Packard's Defect Classification In this presentation, Jon Huber examines metrics obtained from categorizing the same set of defects using both IBM's Orthogonal Defect Classification and Hewlett Packard's Origins, Types, and Modes. Learn the pros and cons of each model, and how to apply the strengths from both models to create a method beneficial to software development and testing.
|
Jon Huber, Hewlett Packard
|
