CHI-ANNOUNCEMENTS Archives

ACM SIGCHI General Interest Announcements (Mailing List)

CHI-ANNOUNCEMENTS@LISTSERV.ACM.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Magdy S. Hanna, Ph.D." <[log in to unmask]>
Reply To:
Magdy S. Hanna, Ph.D.
Date:
Wed, 28 Apr 1999 08:47:18 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (408 lines)
International Conference on Practical Software Quality Techniques
(PSQT '99 South)
San Antonio, TX, June 7-11, 1999.

Complete program and registration information.

Dear Colleague,

I would very much appreciate disseminating this information to other
associates and colleagues as you see appropriate

If you do not wish to receive any more information on these
educational opportunities, please reply with "remove" in the
subject line.

Thank you in advance.

Magdy S. Hanna, Ph.D.
PSQT Conference Chair

------------------------------------------------
More details are available at  www.softdim.com
------------------------------------------------


Keynotes and Featured Presentations:
===================================

Tuesday, 8:30 -- 9:45

Keynote: Disciplined Software Teams, Watts Humphrey

The Software Engineering Institute has developed the Team Software
Process (TSP)SM to help engineering teams more effectively develop
software-intensive products. This talk reviews the current problems
with software development and shows how the TSP addresses them. For
example, software developed by experienced software groups generally
has many defects found in system testing. Such testing is expensive,
time consuming, and not entirely effective. Thus many software
organizations follow system test with many months of early user
testing before making products available for general use.
The TSP addresses these problems with a radically different software
development ethic. By removing defects early, engineers can produce
programs with few if any defects to be removed in system test or by
the users. In addition to producing high-quality products, these
practices have been shown to save many months of testing.
The TSP has been used with pure software teams and with mixed teams
of 2 to 20 hardware and software engineers. TSP has also been used
for both new development and enhancement and with both commercial and
imbedded real-time systems. A number of organizations are using the
TSP and this talk describes some of their experiences. Finally, the
talk briefly reviews the TSP introduction strategy and approach.
TSP introduction starts by training the engineers in the Personal
Software Process (PSP)SM.


Tuesday, 10:15 -- 11:30
Read My Lips:  No New Models!     Dr. Karl E.Wiegers

It seems that everyone who wishes to make a mark in the software world
feels the need to invent a new model or methodology. Such models provide
useful frameworks for structuring our thinking and practices in various
subdomains of software development and management. However, I contend
that we donít need any more new, improved models for software
engineering at the moment. Instead, we need a majority of developers to
consistently and effectively apply the practices that we already know
work! The problem is not inadequate models.



Wednesday, 8:15 -- 9:30
Troubled Software Projects: War Stories and Lessons Learned   Bob Glass

Some software projects fails spectacularly. In this talk, the speaker
will discuss two of them - the debacle of the Denver airport baggage
handling system, and the wreckage of the Westpac Bank information system
in Australia. The talk will focus on an insiderís view of the two projects,
as retold from the speakerís book Software Runaways, but will add some fresh
and recent insights into what really went wrong. Other software projects
struggle mightily before succeeding. The speaker will conclude by discussing
one of those, a project more representative of what really happens in
industry projects. Terrible schedule pressures nearly scuttle the project
before the organization in question is able to turn things around. The talk
will discuss what was done to make than happen, and how it
all turned out.


Wednesday, 9:45 -- 11:00
Good Enough Software Testing    James Bach

In intellectual enterprises, Good Enough is an abstract concept and a
challenging goal at least for those of us who want to be *absolutely
certain* we are doing a good enough job. One thing we do to evaluate the
goodness of software is to test it. But how do we know that our testing
is itself good enough? We need methods for evaluating the goodness of
testing. We need methods that donít necessarily require exotic metrics
or process improvements. We need methods that can be practiced under the
harsh conditions of a typical software project. In this talk I will
propose a set of requirements that any good enough test process should
meet, and some practical ways of assessing a test project against them.
This is part of a work in progress at Reliable Software Technologies to
produce a comprehensive heuristic testing methodology.


The 1999 Software Quality Summit: Wednesday, 3:30 -- 4:45
=========================================================
Bob Glass, James Bach, Karl Wiegers, and Herb Krasner
What Does It Take to Get Software Developers to Adopt Better Practices?


One-day in-depth tutorials:
===========================

Tutorials marked with (CSTP) count as one day towards the requirements
for the Certified Software Test Professional.  Detialis are available at
www.softdim.com/iist

Monday, June 7, 1999, 8:30 - 4:30 p.m.

A1: Software Test Automation Techniques: A Disciplined Approach  (CSTP),
                        Jamie Mitchell
A2: A Practical Approach to the Capability Maturity Model for Software, Version 1.1,
                        William J. Deibler II, Robert C. Bamford
A3: Introduction to Writing Testable Requirements  (CSTP), Richard Bender
A4: Becoming an Effective Test Manager  (CSTP), Randall W. Rice, CQA, CSTE
A5: Creating a Software Engineering Culture, Karl E. Wiegers
A6: Effective Methods and Techniques for Defining, Analyzing, and Reporting Software
        Measurements, Scott Goldfarb

Thursday, June 10, 1999, 8:30 - 4:30 p.m.

B1: Software Test Planning and Design: The Essentials  (CSTP), Dr. Magdy Hanna
B2: Developing and Implementing Software Test Plans  (CSTP), Johanna Rothman
B3: Software Project Risk Management: A Quick start Workshop  (CSTP), Dr. Joyce Statz
B4: A Practical Application of ISO 9001 to Software Development,
                William J. Deibler II, Robert C. Bamford
B5: Exploring the Secrets of Successful User Acceptance Testing  (CSTP).
                Randall W. Rice, CQA, CSTE
B6: Improving Software Quality with Reviews and Inspections  (CSTP), Dr. Karl E. Wiegers

Friday, June 11, 1999, 8: - 3:30 p.m.

C1: Exploring Software Requirements  (CSTP), Dr. Magdy Hanna
C2: Planning and Controlling Software Projects , Dr. David Jones
C3: Testing Object Oriented Systems: Test Case Design and Implementation  (CSTP), Robert Binder
C4: Testing Internet and Web Applications  (CSTP), Randall W. Rice, CQA, CSTE
C5: A systematic Approach to Identifying and solving Project Problems, Johanna Rothman
C6: Understanding Software Test Automation  (CSTP), Michael Sowers



Track Presentations:
=====================

-----------------------------------------------------
Tuesday, June 8, 1999
Four Breakout Sessions of six (6) presentations each
-----------------------------------------------------

1:00 - 2:00  Tuesday
--------------------
1. Risk Management from a Testing Perspective, Bryan Schultz
2. Bellcore Software Systems: A Quality Journey, Robert J. Thien
3. Principles and Process, Kevin Murphy
4. SEI CMM Level 4 Quantitative Analysis, Al Florence
5. A Practical Approach to Achieving the Goals of the Software
   Quality Assurance KPA, Marie L. Daugherty
6. Using Your Metrics Program to Gain Management Support, Bill Hufschmidt

2:15 - 3:15  Tuesday
--------------------
1. PDCA/Test, William E. Lewis
2. The Effects of Workplace Culture on Software Quality, Dr. Anton Webber
   Michael M. Pickard, and Dr. Shelly L. Marmion
3. The Politics of Change, Steve Gitelis and Barbara Beiersdorf
4. Successful Use of the SW-CMM to Grow a Small Software Organization,
   Suzanne Garcia
5. Using Quality to Drive Product Development Processes, Johanna Rothman
6. Earned Value as a Risk Assessment Tool, Dr. Lawrence E. McGovern, DSc

3:30 - 4:30  Tuesday
--------------------
1. Surviving the Top Ten Challenges of Software Testing, Randall W. Rice
2. Dog Soldiers of Software Quality, Rebecca L. Howard
3. Integrated Software Process Improvement based on IEEE/EIA 12207,
        William Diebler II & Robert C. Bamford
4. SEI/CMM - A Practical Approach: Moving from L1 to L2 Process,
    Geree V. Streum
5. Practical Strategies for Handling Lessons Learned, Dr. Joyce Statz
6. Highlights of Practical Software Measurement, George Brotbeck

4:45 - 5:45  Tuesday
--------------------
1. Taking Control of the Testing Process, Rudy Gamberini
2. 10-piece Toolbox to Get People to Change, Neil Potter and Mary Sakry
3. Documenting Processes, Russell Reed
4. SEI SW CMM Level 5: One Milestone on the Journey To Customer
   Satisfaction, Nada L. Gutowski
5. Configuration Management: Providing Stability,Visibility, And
   Prioritization, Jill Blaxton and Judy Calvert
6. Benchmarking Software Development and Support, Scott Goldfarb

-----------------------------------------------------
Wednesday, June 9, 1999
Two Breakout Sessions of six (6) presentations each
-----------------------------------------------------

1:00 - 2:00  Wednesday
----------------------
1. Effective Test Automation: Getting More from Your Tools, Jamie L. Mitchell
2. A Grass-Roots SPI Effort, Michael M. Pickard, Ph.D. and Anton L. Webber
3. From Geek to Guru: Designing and Delivering Presentations Introducing
   Process Change, Stuart and Wendy Henry
4. Riding the Wild Spaghetti - Addressing the Proliferation of Standards
   for Software Engineering, Robert C. Bamford and William J. Deibler II
5. How to Manage Software Requirements Changes Without Loosing Your
   Customers or Your Mind, John M. Rasinske
6. Software Measurement Won't Sell Itself - Secrets to Involving People in
   Culture Change, Carol A. Dekkers

2:15 - 3:15  Wednesday
----------------------

1. Distributed Test Automation: Planning for Success, Jamie L. Mitchell
2. Software Process Improvement Experiences: Setting and Achieving Measurement Goals,
   Jo Ann Lane & Anthony Jordano
3. High Definition Software Measurement - Benchmarking Techniques for
   Process and Quality Improvement, Mr. Michael C. Mah
4. Experiences of Software Quality Engineering with ISO 9001 Certification
   and the Pursuit of SEI CMM Level 3, Arthur Hanson
5. Peer Reviews - A Practical Guide, William Elliot and Jane Hilton
6. Establishing Successful Metrics and Estimating Programs, Scott Goldfarb



Registration Information:
==========================

Conference Fees:              Paid by 4/30/99  Paid after 4/30/99
One Day Tutorial                                   $345              $395
Two Tutorials                                    $595              $695
Three Tutorials                                  $895              $995
2-Day Conference                         $595              $645
2-Day Conference+ 1 Tutorial         $895              $995
2-Day Conference+ 2 Tutorials        $1,195            $1,295
2-Day Conference+ 3 Tutorials        $1,395            $1,495

When five or more persons from the same company enroll together,
a 10% discount is applied.

You may register for the one, two, or three tutorials without
registering for the two-day conference.


Cancellation Policy:
===================

Written cancellations received before the end of the
business day on May 28, 1999 are subject to a $50
cancellation fee for each person registered. Registrants
who fail to cancel in writing by the end of the business
day on May 28, 1999 are liable for the entire fee and can
only be substituted by other individuals for the same
registration. Last day for substitution is May 28, 1999.

Method of Payment:
=================

A payment in one of the following forms must be received
by April 30, 1999 in order to qualify for the early
registration discount.

1. Check drawn on a bank within the Continental U.S payable
to Software Dimensions.

2. Credit Cards: Visa, Master Card & Discover

3. A Cashier check or money order payable to Software Dimensions.

A purchase order may be be mailed or faxed with the
registration only to guarantee the registration, but is NOT
considered a payment and DOES NOT qualify for the early
registration discount.

ALL REGISTRATION MUST BE PAID BY JUNE 4, 1999.

For any questions, call Software Dimensions at (651)552-0716
or e-mail [log in to unmask] .

             Three ways to register:

              (1) Mail the Registration Form
              to:
              Software Dimensions
              8476 Bechtel Ave
              Inver Grove Heights, MN 55076

              (2) Fax the  Registration Form to:(651) 552-0791

              (3) e-mail complete registration information to:
                [log in to unmask]

              No telephone registrations are accepted.

----------------------------------------------------
PSQT '99 South Registration Form
(Also available at www.softdim.com/psqt/psqt99south)
----------------------------------------------------

Print form, fill it out & mail to:
Software Dimensions,  8476 Bechtel Ave,
Inver Grove Heights, MN 55076

or fax to (651)552-0791


Company Name __________________________________________________

Contact Person _______________________________________________

Title ___________________________

Address____________________________________________

Mail Stop _______________________

City_______________________State_________Zip ______________

Phone__________________________Fax ______________________

e-mail _________________________________

Each registrant may specify only one tutorial for Monday
(A1 thru A6), one for Thursday (B1 thru B6), and one for
Friday (C1 thru C6).

Please include mail number or department number for
each attendee for confirmation purposes.

Name: ____________________    Mail Stop _______ Email __________

Conf (Y/N)  Tutorials (specify #) A(  )  B(  ) C(  )  Cost _______


Name: ____________________    Mail Stop _______ Email __________

Conf (Y/N)  Tutorials (specify #) A(  )  B(  ) C(  )  Cost _______


Name: ____________________    Mail Stop _______ Email __________

Conf (Y/N)  Tutorials (specify #) A(  )  B(  ) C(  )  Cost _______


Name: ____________________    Mail Stop _______ Email __________

Conf (Y/N)  Tutorials (specify #) A(  )  B(  ) C(  )  Cost _______


Name: ____________________    Mail Stop _______ Email __________

Conf (Y/N)  Tutorials (specify #) A(  )  B(  ) C(  )  Cost _______


Name: ____________________    Mail Stop _______ Email __________

Conf (Y/N)  Tutorials (specify #) A(  )  B(  ) C(  )  Cost _______


Name: ____________________    Mail Stop _______ Email __________

Conf (Y/N)  Tutorials (specify #) A(  )  B(  ) C(  )  Cost _______


                                                     Total  ______

If five or more people from the same company are
registering, multiply total by.09and record amount due      ______


A payment in one of the following forms must be received by April 30,
1999 in order to qualify for the early registration discount.


1. Check drawn on a bank within the Continental U.S payable to Software
Dimensions.

2. Credit Cards: Visa, Master Card & Discover

3. A Cashier check or money order payable to Software Dimensions.

ALL REGISTRATION MUST BE PAID BY JUNE 4, 1999.

1  Check Enclosed for $________________

2 Visa/MasterCard/Discover (circle one)

Card#______________________   Exp. Date_____________

Authorized signature:__________________________


A purchase order may be be mailed or faxed with the
registration only to guarantee the registration, but is NOT considered
a payment and DOES NOT qualify for the early registration discount.

Purchase Order #___________________

ATOM RSS1 RSS2