13th International Conference on Software Quality

Software Division of
The American Society for Quality

Home ] Up ] Sponsor & Exhibitor Opportunities ] Special Needs ] Dallas Info ] Hotel/Airline/Rental Car/Driving Directions ] Paper & Tutorial Presenter Information ] Volunteers Opportunities ] ICSQ History.htm ] Contact Us ] About ASQ ]


Monday Tutorials
Tuesday Conference Schedule
Wednesday Conference Schedule
Thursday Tutorials
Post Conference Courses
Call for Papers & Tutorials


Tutorials - Monday, October 6, 2003:

Full Day Tutorial Sessions:

7:00 a.m. - 8:00 a.m.    Continental Breakfast

8:00 a.m. - 5:00 p.m.    Full-Day Tutorials

Noon - 1:00 p.m.            Lunch


TUT01: Quality Consulting for Quality Consultants - Gerald Weinberg

(Register early as class size is limited to 20)

Quality is obtained one person at a time.  Every successful quality professional is also a successful and masterful one-on-one consultant. In this interactive tutorial, you will  obtain new strategies for coping with your most serious quality consulting problems — both internal and external.

Jerry Weinberg, author of The Secrets of Consulting and More Secrets of Consulting, helps you affirm your most successful strategies, while sharing other techniques you may not have thought of.

Learn to be more sensitive to client desires, more aware of safety issues, and more influential in obtaining effective client responses, all leading to higher quality in products, processes, and people.  Real-life consulting cases brought by the participants will be used to illustrate all the principles.

Gerald Weinberg's biography and information about his keynote.


TUT02: In Search of Excellent Requirements - Karl Wiegers

Requirements form the foundation for all the software work that follows. Arriving at a shared vision of the product to be developed is one of the greatest challenges facing the software project team, and customer involvement is among the most critical factors in software quality. The objective of this tutorial is to give attendees a tool kit of practices, reinforced with practice sessions and group discussions, that they can begin applying to improve the quality of the requirements development and requirements management processes in their organization.

Learn about tested methods that can help any organization improve the way it gathers, documents, and analyzes software requirements. Characteristics of excellent requirements statements and requirements specifications are presented and used to evaluate some sample functional requirements. The seminar emphasizes several practical techniques, including:

  • Customer involvement through a “product champion” model

  • The application of use cases for defining user needs and system functions

  • Writing software requirements specifications using a standard template

  • Construction of dialog maps to model user interfaces

  • Using prototypes to clarify and refine user needs

  • Using peer reviews to find errors in requirements

  • Using a requirements traceability matrix to connect requirements to design elements, code, and tests

The basic concepts of requirements management are described, as are practical methods for managing changes to requirements. These techniques can reduce project risk by improving the quality and control of the software requirements, thereby increasing the likelihood of a successfully completed project.

Karl Weigers' biography and information about his keynote.


TUT03: Proactive Testing: Project Manager’s Secret Advantage - Robin F. Goldsmith

Testing often is considered an obstacle to project completion, but savvy project managers know that Proactive Testing™ can help them deliver better software quicker and cheaper.  This interactive tutorial reveals proven testing methods that also cut development time. Developers finish coding sooner and spend less time recoding. Moreover, Proactive Testing™ can prevent many of the showstoppers and late unplanned redesign and rework that ordinarily cause most major project overruns. Learn how developers and users, as well as managers, can turn testing from obstacle to advantage whose benefits they recognize and desire. Exercises enhance learning by allowing participants to practice applying practical techniques to an actual case.


TUT04: Making Process Improvement Work: A Concise Action Guide for Software Managers & Practitioners - Mary Sakry & Neil Potter

This tutorial provides a systematic approach for organizations to improve their software development capability, resulting in higher product quality and reduced costs. It presents a straightforward, systematic approach to planning, implementing, and monitoring an improvement program.

Software process improvement too often reflects a significant disconnect between theory and practice. This tutorial bridges the gap by offering a straightforward, systematic approach to planning, implementing, and monitoring a process improvement program. Project managers and teams will be able to apply the tutorial’s practical ideas immediately to real-life challenges.

You will develop an improvement action plan based on the business goals and problems of your organization. This approach addresses the frustration that many people experience when   improvement programs do not relate to the project work being done.

Learn techniques for deploying new practices across the organization. These techniques address the problems of resistance, unwieldy solutions, and slow deployment.

Also presented are techniques for checking the progress of your improvement program and taking corrective actions based on what you learn. Checking progress is an essential activity to provide the organization with feedback when pursuing business goals and solving problems. The resulting data allow for early problem detection, early correction, and improved visibility to management on improvement progress.

Mary Sakry's biography and information about her invited speaker presentation.

Neil Potter's biography and information about his invited speaker presentation.


TUT05: Risk-Driven Software Testing - Joyce Statz

Software organizations that want to maximize the yield of software testing find that choosing the right testing strategy is hard, and most testing managers are ill-prepared for this. The organization has to learn how to plan testing efforts based on the characteristics of each project and the many ways the software product is to be used. This tutorial is intended for software professionals who are likely to be responsible for defining the strategy and planning of the testing effort and managing it through its life cycle. These roles are usually those of testing managers or project    managers. Topics include:

  • Introduction to managing testing

  • Defining the scope of testing in a software project

  • Testing strategies

  • Developing the testing assets

  • Managing risk

Dr. Joyce Statz is Vice President of Knowledge Management at TeraQuest, where she helps employees and client organizations with process improvement programs.  She coordinates development of product and service offerings which help clients to build and deploy improved processes, develop Project Management Offices, and establish measurement programs.   Joyce is a co-founder of TeraQuest, experienced in consulting and training in areas of risk management, project management, measurement, software life cycles, the Software Engineering Institute (SEI) maturity models, and a broad range of product development processes. 

Joyce has 15 years of experience in the design, implementation, and management of leading-edge software systems at Texas Instruments.  She was a leader in evolving TI’s software development and project management processes, based on SEI maturity models.

Prior to her work at Texas Instruments, she taught computer science at Bowling Green State University, and she is a founder of the Software Quality Institute of The University of Texas at Austin (SQI).  She developed the initial curriculum for their year-long Software


TUT06: Software Quality Function Deployment - Dan Houston

Software practitioners continue to search for tools to enhance software project and product quality. Quality Function Deployment (QFD) is one approach that directly addresses quality in product development. It has been widely used in a number of industries, and has had limited application to software. Its use is increasing as Six Sigma is embraced by more companies because QFDis a cornerstone of design for Six Sigma.  Also, as Six Sigma is applied more to software development, the application of QFD to software will increase.

QFD has been applied to software development in a variety of ways, typically starting with, and sometimes ending with, a product planning chart.  However, quality charts can be used throughout the software development process.

Learn the concepts underlying QFD and quality deployment, and the benefits of QFD as cited by those who have applied it to software development. QFD will be presented as a means of supporting decision making during product development.

Houston will discuss the four main charts that can be used in software development and illustrate their use with a product example. Group exercises will teach attendees the mechanics of creating and using quality charts, as well as planning for QFD by specifying a series of quality charts. Various configurations of quality charts will be provided to illustrate the opportunities for their use in software development.


Tutorial Outline:

What is quality?

Quality function deployment and quality deployment

Background on QFD


            Underlying concepts

What can QFD mean for software?

            Differences from manufactured products

            Benefits for software

            Relationship to requirements

The voice of the customer

            Listening and analyzing

User needs hierarchy

The product planning chart

The mechanics of quality charts

A product planning chart exercise

Other types of quality charts for software

Integrating QFD into your local development process

An exercise on applying QFD to a project

Dan Houston is a Six Sigma Black Belt at Honeywell. He is currently leading a team deploying Software Design for Six Sigma. He spent 11 years in software development while earning a doctorate in Industrial Engineering. His publications include papers on software quality economics, software process simulation, and designed experiments on computer models. He is a member of ASQ, IEEE-CS, and ACM.