Twenty-First Annual Pacific Northwest Software Quality Conference

Spring Workshops

Friday, May 9, 2003
Hilton Portland & Executive Tower
Portland, Oregon
8:30am - 5:00pm

Co-Located with ICSE 2003

The Pacific Northwest Quality Conference's (PNSQC's) mission is to promote the importance and increase the awareness of software quality by providing opportunities for education and information. The Twenty-First Annual Pacific Northwest Software Quality Conference's Spring Workshops are being presented in co-location with ICSE in Portland on Friday, May 9, 2003.

Summaries of PNSQ's Spring Workshops are given below.

Complete information and online registration for these workshops can be found at A $275 registration fee includes a full-day workshop, lunch, and a workbook.

Workshop Summaries

Workshop 1: Reduce Rework and Project Delays by Implementing Peer Reviews (Inspections)

Neil Potter, The Process Group

Rework is expensive, causes delays, and can tarnish a company's image - however many organizations spend 25-75% of their resources on rework. Implementing an inspection process concentrated on finding defects quickly, cost-effectively, and early in the development process can have a great impact. Participants will lear n how to implement and moderate inspections as well as strategies for deploying them successfully.

Workshop 2: Architectures for Automated Testing

Douglas Hoffman, Software Quality Methods, LLC

Software testing can consume up to half the total cost of developing many software products but, despite the huge investment, it is often done inefficiently. Effective software test automation can help reduce that cost. This workshop explores several types of automation design architectures. Participants will be given exposure to the analysis of requirements, cost, risk, software architecture, high-level design, data design, and design for maintainability, as these apply to test automation.

Workshop 3: Test-Driven Development: A Hands-On Introduction

Ward Cunningham, Cunningham & Cunningham, Inc.

The techniques of Test-Driven Development (TDD), as practiced in Extreme Programming and other agile development methods, use tests as much to guide programming as to test the correctness of the result. Test-driven designs are more easily "refactored" making TDD the only programming method that expects programs to get "cleaner" over time. To establish the context for TDD, Extreme Programming will be briefly explained, followed by live demos and lab exercises using simple Java, with emphasis on familiarity with the tools and techniques, not programming.