Call for Papers, Presentations and Tutorials

The International Conference on
Practical Software Quality Techniques
PSQT 2003 East

The International Conference on
Practical Software Testing Techniques
PSTT 2003 East

June 9 - 13, 2003, Washington D.C. Area

Proposals for full day tutorials are invited and must be submitted according to
guidelines that can be found at or may be requested via
e-mail to the Chairman of the Conference, Dr. Magdy Hanna at Please do not use the guidelines below for tutorial

Proposals for papers and/or presentations reflecting real experiences with
practical software quality techniques or practical software testing techniques
are invited for both conferences. We would like to hear from you if you have
expertise or experiences in any software quality, testing technique, or tool.
This is a great opportunity to share your experience with other software
professionals and get their feedback in this practice-oriented conference.
Topics of interest include:

* Testing Technology, Testing Process and Test Automation
* Inspections, Reviews, and Walkthroughs
* Software Process Assessment and Improvement
* Web and e-Commerce Related Quality and Testing Issues
* Quality Management Issues
* Measurements and Benchmarking
* ISO 9000 Certification
* Configuration Management and Version Control
* Change Tracking
* Project Management
* Risk Assessment
* Requirement Management
* Automated Tools Dealing with any of these areas.
Proposals dealing with other topics will also be considered.

Important dates:
February 3, 2003: Proposals for papers and presentations are due
March 3, 2003: Notification of acceptance/rejection will be mailed out
April 28, 2003: Copies of presentations and papers are due

The acceptance of a proposal does NOT guarantee acceptance of the presentation
or paper. Presentations and papers must address all issues proposed in the
proposal to be accepted.

All accepted papers and presentations are awarded a free admission to the
PSQT/PSTT 2003 EAST two-day conference where they are presented and a copy of
the conference proceedings. In addition, the best paper or presentation as
judged by the conference delegates will be invited as a featured presentation in
the following conference.


All submissions must be sent via e-mail to the Program Chair, Jamie Mitchell at as follows:

One file in MS Word or RTF format containing all items under submission
rules below
One file in MS Word or RTF format containing the paper if available
One file in PowerPoint containing the presentation if available

Do not include any part of your submission in the body of the message.

Submission Rules:

(Any submission that does not follow exactly these rules will not be considered
by the program committee)

Proposals must include ALL items below:
1. Presentation title
2. Indicate whether the proposal is for a presentation only or for a paper and a
presentation. Papers are not accepted unless they will be presented.
3. Presenter's name, title, company/organization name
4. Mailing address, telephone number, fax number, and E-mail address
5. Detailed biography indicating specific experiences with the subject of the
6. A narrative description of the concepts covered by the presentation
7. A detailed outline of the presentation. This outline is needed for inclusion
in the conference proceedings and the web site. Submitting the actual
presentation slides or a paper as in item 10 or converting power point
presentation to outline DOES NOT substitute for the item.
8. Five to six bullets corresponding to the learning objectives of the
9. Indicate whether the material was presented before and name and date of the
10. If presentation slides or a paper on the topic is available attach a copy.
This will provide more information to the selection process.

Proposals and presentations must meet the following guidelines
1. Do not include any company specific terms or acronyms unless defined
2. Must focus on what can be learned
3. Must not propose any introductory or text-book type material
4. The focus must be on specific experiences rather than vague advice
5. Must not promote any service or products