|
Testing Your Software's Requirements Many testing organizations focus primarily on software executable code, but that's not the only thing you can test. For instance, did you ever consider testing your software requirements? When you test only code, you face some big disadvantages, not to mention that design defects often aren't even fixable because they demand too much effort, too late in the release cycle. In fact, it's difficult to even report some requirements defects since the developers have already committed to the design strategy. But if you test your requirements early in the game, you can discover defects before they're cast into designs and code, consequently saving your organization potentially huge rework costs.
|
Brian Lawrence, Coyote Valley Software
|
|
Robust Design Method for Software Testing This session presents a robust design method based on the Taguchi Approach. A new and powerful way to improve reliability and productivity, this method has been applied in diverse areas such as network optimization, audio and video compression, error correction, engine control, safety systems, calibration, and operating system optimization. Learn the basics of the robust design method for software testing, and experience the principles through case studies like Unix system performance tuning.
|
Madhav Phadke, Phadke Associates
|
|
Using Metrics to Govern Outsourced Applications Outsourcing arrangements are established on the basis of a contractual partnership, with both parties having a vested interest in the success of the relationship. Success can be viewed differently by the outsourcing provider and customer, however, making the use of objective, quantifying service level metrics instrumental to the success of the contract. Learn how to properly identify and develop service level metrics required to support both business and technical deliverables.
|
Eric Buel, Eric Buel and Associates, Inc.
|
|
Basis Path Testing for Structural and Integration Testing Basis path testing is a structural testing technique that identifies test cases based on the flows or logical paths that can be taken through the software. A basis path is a unique path through the software where no iterations are allowed; they're atomic level paths, and all possible paths through the system are linear combinations of them. Basis path testing uses a Cyclomatic metric that measures the complexity of a source code unit by examining the control flow structure. Basis path testing can also be applied to integration testing when software units/components are integrated together. You'll see how the use of the technique quantifies the integration effort involved as well as the design-level complexity.
|
Theresa Hunt, The Westfall Team
|
|
Calculating the Return on Investment of Testing While revenues, cash flow, and earnings are vital statistics of a company's well-being, they're the by-product of what the company actually offers up as a product or service. Therefore, if the offering doesn't produce ROI for the customer, it doesn't represent a viable business opportunity. In this session, take a look at testing from the perspective that it's a service provided to your company. Since testing impacts not only your company, but also your company's customers, then you, as a tester, must provide and prove ROI to succeed in a business environment. Having the ability to discuss, define, manage, and demonstrate the ROI of testing is an invaluable skill. This session gives you the information and tools you need to define and demonstrate models of testing ROI, then translate them into upper management's terms.
|
James Bampos, VeriTest Inc/Lionbridge Technologies and Eric Patel
|
|
Measuring and Benchmarking IT Performance IT leaders strive to continuously improve their software development and support practices by keeping watch on the industry's best practices. To assist with this task, they turn to the International Software Benchmarking Standards Group (ISBSG) industry performance profile data. Learn how to use this data in establishing performance goals and improving current software development practices.
|
Andy Sanchez, The David Consulting Group, Inc.
|
|
Measuring and Managing Performance in Organizations Don Gray recommends Measuring and Managing Performance in Organizations by Robert D. Austin. The book is not a five-step program toward measurement success; instead, it gives an in-depth look at what makes or breaks measurement systems. The book presents information in an intuitive way; if you understand algebra and simple logic, you will understand what Austin is presenting.
|
|
|
On the Cost of Quality Technical Editor Brian Lawrence explains four types of costs of quality: prevention, appraisal, internal failure, and external failure.
|
|
|
A Cautionary Tale Technical Editor Brian Marick uses a fairy tale format to warn software professionals against using easy-to-acquire numbers in place of human judgment.
|
|
|
Measuring Up You measure because you want to make better-informed decisions. But even simple, harmless-looking measures can be dangerous. For example, they can give you a nice, clear picture of an illusion. Do you want to base your decisions on illusions? Technical Editor Brian Lawrence advises that, before you dive into measuring anything, ask yourself, "Will measuring do more harm than good?"
|
|