Conference Presentations

A Solid Foundation for Quality Improvement

Many managers look to formal techniques-requirements reviews, code inspection, and testing-to improve the quality of their software. While these techniques are valuable, they only evaluate the state of quality rather than improve it. The key is to create quality software in the first place. This can only be achieved by a change in management style. Jason Bryant proposes a set of simple and effective principles you can employ to produce high quality software. First, you must foster a culture where people are given the freedom, time, and resources to do the job correctly the first time. By embracing user centered and incremental development practices, you will go a long way toward ensuring accurate and timely software delivery. Focus on training your staff to become masters of their craft and invest equally in architecture, new features, and maintenance.

Jason Bryant, Schlumberger Information Solutions
The Complete Developer

With the global availability of talented development people there is a growing trend toward the commoditization of software development. No longer is it enough to simply be a developer with knowledge of specific languages or algorithms in order to maintain your competitive edge in the marketplace. To compete, you must become a complete developer-someone who can, for example, write some code in the morning and in the afternoon update the requirements Wiki with the results of the latest customer review meeting with your marketing team. This talk explores what it takes to be a genuinely valuable complete developer in today’s world of agile development, outsourcing, globalization, and an increasingly complex business environment.

Luke Hohmann, Enthiosys, Inc.
Testing: The Big Picture

If all testers put all their many skills in a pot, surely everyone would come away with something new to try out. Every tester can learn something from other testers. But can a tester learn something from a ski-instructor? There is much to gain by examining and sharing industry best practices, but often much more can be gained by looking at problem solving techniques from beyond the boundaries of the Testing/QA department. Presented as a series of analogies, Brian Bryson covers the critical success factors for organizations challenged with the development and deployment of quality software applications. He takes strategies and lessons from within and beyond the QA industry to provide you with a new perspective on addressing the challenges of quality assurance.

Brian Bryson, IBM Rational Software
Sarbanes and Oxley: Your New Stakeholders

Determining whether legal and contractual issues apply to your development efforts isn't always simple. There may be some obvious factors: a well-regulated industry, service level agreements, and state or federal agency oversight. However, other factors may not be so obvious. The new Sarbanes-Oxley Act is largely legally untested, subjecting your company to unknown legal issues. You have an eCommerce site that stores credit card information. Your portal collects personal information. You produce proprietary software . . . and more. Covering legal, compliance, and audit throughout the QA process lifecycle, Elle Ringham discusses the right questions to ask and what to do with those answers. She provides guidelines for working with stakeholders, attorneys, and auditors. Take away audit templates, metrics to help you, and sample reports you may need to produce.

  • Legal and compliance issues within QA scope
Elle Ringham, Fidelity National Financial
Sarbanes-Oxley Compliance: Burden or Opportunity for QA?

Did they have to create more work for IT? There is no doubt that Sarbanes-Oxley (SOX) and similar compliance regulations have created a significant new workload for IT departments, including many QA/Test groups. Companies that have gone through initial compliance of SOX now must deal with the new challenge of its ongoing maintenance. For QA groups, SOX compliance can be an opportunity to increase their business value in the IT department by leveraging automation tools, new technologies, and improving the processes that support compliance. Rutesh Shah offers observations on how QA/Test teams can help ensure SOX compliance and optimize efforts toward complex compliance procedures. Come and review sample test reports, audit trails, and quality metrics for SOX compliance.

Rutesh Shah, InfoStretch Corporation
Quality Assurance and Testing in an FDA Regulated Environment

How can we reduce costs associated with FDA imposed computer systems validation (CSV) guidelines and improve test coverage at the same time? Experienced in the use of automated testing tools in FDA regulated environments, Eric Toburen shares the challenges of complying with FDA validation guidelines. For many companies, manual CSV is a like a heavy boat anchor that slows projects and increases costs while adding no value other than the perception that the practice avoids an auditor's attention. Find out how automated testing and test management practices can be used to shorten the CSV lifecycle and improve test coverage. After deployment use the automated tests for regression testing to enable the deployment of bug fixes and upgrades minimizing the need for re-evaluation.

Eric Toburen, Genilogix
Testing Windows Registry Entries

Warning: Registry keys may be hazardous to your program's health! Registry key entries in Windows applications-visible or hidden-are often neglected by testers. A registry key entry is a program feature just like any other application function and as such needs to be validated. Michael Stahl describes why registry keys should be accorded special attention during testing and proposes a strategy for mitigating risks posed by incorrect registry key entries. He suggests a test strategy, as well as coding standards for input value and type validation, default values, regeneration, and naming rules. Michael demonstrates the use of correct and incorrect registry keys in common commercial applications.

Michael Stahl, Intel Corporation
Systematic Techniques for Fault Detection and Isolation

Selecting the appropriate testing techniques and test cases improves test efficiency, reduces time to market, and gives you confidence that the system is ready to ship. Using real-world case studies as examples, Madhav Phadke explains the fundamentals of robust test case selection and how code coverage can improve your test results. He discusses ways for testers to support debugging and faster repairs by isolating defects to a specific part of the software. Learn to select test outputs based on "total function evaluation" rather than end customer outputs and ways to use orthogonal arrays for testing combinations of parameters. Take away a list of free or inexpensive tools that can speed up your testing process.

Madhav Phadke, Phadke Associates
How Much Quality is Enough?

Are you striving for more quality than you really need? How would you know? "Good enough" quality does not mean "substandard" or "mediocre" but is actually an optimal and responsible economic principle we use everyday. Managing test lead for Quardev Laboratories, Jon Bach says because quality is expensive, the "good enough" framework provides the criteria to enhance decision-making about when to ship. He discusses the perils of quality-at-all-cost techniques and shares examples of software that features sufficient quality. Find out how testers and test managers can help project stakeholders know whether they are releasing software with too little quality or are unnecessarily striving for too much quality.

Jon Bach, Quardev Laboratories
Negotiating the Defect Minefield for a Successful Product Release

Software success is strongly influenced by how you finish a project. For that, a special set of skills is required. Many projects fail in their endgame during testing, not because of the testing itself but because of the late discovery of defects and functional gaps that show the software as not viable. Join Robert Galen as he focuses on a set of high level practices and techniques that will help improve your management and steering within the endgame. Learn about a release framework with the right testing tempo and key milestones. Define formal release criteria and add flexibility and depth to your defect fix-don't fix decisions. As a manager in the difficult release endgame, your behavior and leadership can make the difference between a successful release and perceived failure. Robert’s guidance will increase the odds of successfully delivering your release.

Robert Galen, Thomson/Dialog


StickyMinds is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.