ASQ - Software Division
In This Issue:
July 2006


Click here to receive the CIO briefing “Maturing Your Quality Practices,” compliments of Compuware.


Click here to see how IQPS implements and improves a company's business management systems, including the manufacturing and software development areas.

A Message From the Chair – David Walker
2006-07 Software Division Council Org Chart
Submit Articles for SQP Journal
World Congress Update
2006 PNSQC Quality - A Competitive Advantage
Synopsis of 2006 FAA National Software Conference
CSQE Update
CSQE Practice Quiz
Another Look at GPSV
Third Party Software Soup
ISO/IEC JTC1/SC7 International Plenary in Bangkok
Regional News / Upcoming Events
See the latest Software Quality Job Postings:


A Message From the Chair
I started my two-year term as Chair of the Software Division on July 1 st , excited and eager to lead an already great organization to bigger and better things. My number one goal as chair is to capitalize on the opportunities we have as a nearly 4000-member organization. I've outlined some of the Division's initiatives later in this article.

My ASQ membership started in October, 1986 when I took an ASQ Software Quality Assurance course. In the 1990's, I assisted with the development of the Certified Software Quality Engineer (CSQE) program. In 1996, I served as a regional councilor in Michigan . In 2001, I served as the regional councilor coordinator, recruiting and coaching our regional councilors worldwide. For the past two years, I have served you as the Chair Elect, strengthening the division's relationships, leading strategic planning, and revitalizing the critical programs and services that the Software Division offers to you, the members.

In January, 2006, the Software Division Strategic Planning Team met in Dallas over a weekend to discuss the direction of the division. This meeting employed the use of a rigorous strategic planning methodology and resulted in the following 11 strategies that we will pursue over the next 5 years:

  1. Improve Organizational Effectiveness
  2. Identify, Support & Maintain Body of Knowledge & Associated Certifications
  3. Outreach: Make connections with/create connections between selected stakeholders (forums, discussions, associations, standards bodies recruiting etc.)
  4. Grow Software Division membership
  5. Transfer of Knowledge: Website & Newsletter- focus on Innovation
  6. Transfer of Knowledge: Conferences & Roundtables - focus on Innovation
  7. Transfer of Knowledge: Make education programs available to members (Webinars, seminars, courses, &academic programs) - focus on Innovation
  8. Transfer of Knowledge: Journals, Software Quality Professional
  9. Transfer of Knowledge: Produce guides/handbooks to enable members to grow as software quality professionals and to help prepare for the CSQE exam
  10. Get involved legislatively in software quality issues (position papers)
  11. Provide opportunities/open doors to members in their careers & in professional growth

We, the ASQ Software Division, will pull together as a professional organization. It is our responsibility to use our networks and organizational strengths to provide opportunities for organizations world wide to develop and nurture software practices. We must continuously recognize and reward those individuals and organizations who support our operations with commitments of time and money. Our volunteers are strong leaders in their organizations and many have been with us for a long time. We also have new volunteers with new energy and ambition. I welcome you to contact us and get involved. Contact me at or the Software Division at

I'm glad you've joined us. Help us take the Software Quality profession forward!

David Walker, Chair

2006-07 Software Division Council Org Chart

Click on the image below to view the complete chart (Microsoft Powerpoint, 49 KB)

ASQ SDC Org Chart Thumbnail

Back to top...


Submit Articles for SQP Journal
Software Quality Professional journal is looking for authors and reviewers. To be appropriate for SQP, articles should give readers a working understanding of how software quality practices are used successfully. Articles should support theory with real-world accounts of how to implement the processes described. To the extent possible, use data to demonstrate conclusions. Typical article lengths are 4,000-6,000 words. All articles go through a peer review process and copyediting prior to publication. Please see the author guidelines for submission format. Articles should align with topics listed in the CSQE Body of Knowledge.

We also accept short articles (<1000 words) as a Quality Nugget at the end of each issue.

Quality principles:

  • Professional conduct.
  • Ethics.


  • Quality management.
  • Processes.
  • Project management.
  • Metrics, measurement and analytical methods.
  • Inspection, testing, verification and validation.
  • Audits.
  • Standards and models
  • Configuration management.

For more information regarding the suitability of a proposed topic, contact the editor.

Seeking Reviewers
SQP is looking for reviewers for articles as well as books and other resources. Guidelines for Resource Reviewers are available. Most reviews are about 700 words long. Article reviews are anonymous while resource reviews are printed with the reviewers name and email - and a short bio is added to the web page version.

Sue Carroll, Editor-in-chief

Back to top...


World Congress Update

The Fourth Congress for Software Quality will be held in the Washington D.C. area in September 2008, combined with the ASQ Software Division conference that year.

The intent is not to have "yet-another-conference conference" but to offer unique and targeted professional growth opportunities for experienced as well as less senior practitioners.

The 2007 Software Division conference can prototype certain aspects of the World Congress, such as specialized workshops for individuals new to the profession and the launch of a mentoring program.

Would you be willing to help?

  • We are soliciting "lessons learned" - both positive and negative - from other conferences, training sessions, and professional activities.
  • Individuals are invited to join a "vision team" that will project novel ways to maximize the benefits of the Congress.
  • Anyone in the greater D.C./Virginia/Maryland area is asked to contribute insights about possible conference locations and local enrichment activities for our international guests.

For more information, or to volunteer to assist, please contact Taz Daughtrey at or 434-237-2723 (voicemail/fax).

2006 PNSQC Quality - A Competitive Advantage
Interested in the 2006 Pacific Software Quality Conference?
Check out the latest info and find out about the special ASQ discount! (PDF, 41 KB)

Synopsis of 2006 FAA National Software Conference
Interested in the events of the FAA National Software Conference?
Read the synopsis
(PDF, 67 KB)

Back to top...


CSQE Update
Background on CSQE
The software division has sponsored the Certified Software Quality Engineer (ASQ-CSQE) exam since 1996. Leadership for the exam was provided primarily by Linda Westfall and Doug Hamilton. As is the case for each of ASQ's exams there is and has been a designated chair for the exam. The CSQE exam chair is appointed by the certification board chair and is responsible for recruiting subcommittee members who help with the exam process as well as workshop recruiting. Via the exam chair, each exam has representation on the certification board. The certification board is responsible for promoting exams as well as for maintaining process consistency across all of ASQ's certifications.

New Exam Chair and Development Plans
Alex Hilgendorf mentioned in a previous newsletter that the CSQE exam chair position is transitioning to me, Kathi Harris. I passed the pilot exam in 1996 and have been participating in workshops regularly since about 1999. For the past two years, I have been the workshop recruiter, working closely with Alex. I really enjoy the entire exam development process and have learned a lot from the Certification staff. Our test developer, Mary Rehm, is excellent, and I'm looking forward to working with her for the next two years.

I am pleased that the other two members of the CSQE subcommittee will be continuing to work with me. They are Christine Brown-Strysik and Karen Bishop-Stone.

The rewrite of the Body of Knowledge for CSQE is scheduled to begin after July 2007. If you have topics that you'd like to suggest we include in the initial job survey, please send that information to me,, for consideration.

To support the creation and maintenance of certification tests, ASQ hosts several workshops each year. Participants of the workshops offer their expertise for two days in exchange for travel, lodging, and food expenses as well as 2 certification credits per workshop. Workshops types include BOK updates (once each 5 years), Exam Reviews (2 per year), Item Writing and or Item Review workshops (as needed). Workshop committees consist of around a dozen CSQE-certified people. To maintain the integrity of the test material we try to include around 6 people that have never attended that particular type of workshop. Our next workshop will be an exam review, September 22-23, 2006 , in Milwaukee . If you're interested in participating in that workshop or in becoming a workshop recruiter, let me know.

The next round of national and international certification tests will be administered on December 2, 2006 with an application deadline of October 6, 2006 . I am also working with PNSQC to offer a special administration at that conference in October. Please check the Certification website for more information on that administration, including the date, if you are interested.

CSQE Practice Quiz
Ready for the CSQE Exam? Try this practice quiz (PDF, 51 KB)

Back to top...


Another Look at GPSV
By David Walker, Chair - ASQ Software Division

This column has listed various WEB links to important FDA guidance documents regarding software validation. About a year ago, a link was provided to the "General Principles of Software Validation" (GPSV) white paper, published by the CDRH (Center for Devices and Radiological Health in 2005. This is a must read if you are developing software for use in a medical device.

Another good, related read is the summary of the public comment filed in the federal register on January 11, 2002. It is a 7 page record of the dialog between 36 organizations of industry and the FDA regarding specific topics covered in the 1997 version of GPSV.

This dialog allows us to see more clearly the expectations of the FDA as manifested in the GPSV guidance document. For example, one comment claimed that the use of a requirements traceability matrix for very large projects was overly burdensome. The FDA's responds that the larger the project, the greater the need for the traceability matrix.

Here is the link to this GPSV Preamble:

Have a great summer!

Back to top...

Third Party Software Soup (Software of Unknown Pedigree)
By W. L. "Bill" Trest, ASQ SD Regional Councilor Coordinator

Various issues have arisen concerning use of 3rd Party Software in Government Aerospace product applications/ deliverables. Concerns include software in both source and object forms, generated by an entity not specifically a part of a US Government contract, including the prime contractor as well as their supplier(s). Such 3 rd Party Software could include Open Source Software (OSS) as well as 'freeware' or 'shareware', as well as SOUP (Software of Unknown Pedigree), etc. As used, the term software typically means a computer program but may also include various software technical documents and data, including database content.

As specified or provided for in contracts invoking Federal Defense Regulations, the US Government shall most often be provided Unlimited Rights in Data, such as in Computer Software developed in whole or part with Government funds, that is otherwise publicly available or has been released or disclosed by a Government contractor or subcontractor without restriction.

What this means in delivering software products is that Government contractors and their subcontractors must perform reasonable due diligence in honoring copyrights. Typically, such due diligence includes taking reasonable efforts to inspect and/or perform automated 'scanning' of software products for the presence of copyrighted material. If copyrighted material must be included, any rights in data and/or intellectual property must be conveyed or accounted for per defined contractual provisions.

If U.S. Government funding pays for the software, delivered products must also be unencumbered by copyright restrictions. If an existing copyright is infringed, the company, the individuals involved, as well as the US Government could be liable.

(W. L. 'Bill' Trest is Regional Councilor Coordinator for ASQ Software Division as well as a Computer Software Quality Engineer by the Lockheed Martin Aeronautics Company in Fort Worth, Texas . Bill is a member of the Greater Fort Worth Section 1416 of the American Society for Quality ASQ.)

Back to top...


ISO/IEC JTC1/SC7 International Plenary in Bangkok
Some "Outputs" and Directions

This past May, member nations of and liaisons to the joint ISO and IEC system and software engineering standards subcommittee met in Bangkok for their annual plenary gathering. A variety of new standards drafts at various points in their ballot cycle have been released since that Plenary and several study groups are looking into new efforts. The following report summarizes these documents and efforts.

First, the following documents have been released, most of which will be balloted over the next several months (F=final, P=preliminary, D=draft, IS=international standard, TR=technical report, WD=working draft, CD= committee draft):

  • 24768 Working Draft 3 - Guide for life cycle management (not for ballot)
  • 24744 FDIS - Metamodel for Development Methodologies (abstract only)
  • 24774 PDTR - Life Cycle Management, Guidelines for process definition (ballot ends 9-27
  • 27005 CD (1 st ) - Security techniques, Information security risk management (actually from SC27, ballot closed)
  • 25001 FDIS - Software product Quality Requirements and Evaluation (SQuaRE), Planning and management (sent for FDIS processing, ballot expected)
  • 15939 FCD - Measurement process (ballot ends 10-29, minor changes to reflect "system and software," rather than just "software")
  • 25012 CD - SQuaRE, Data Quality Model (voting summary, Canada, Japan, UK and USA disapproved, 9 others approved, 2 abstained and 14 did not vote (almost half))
  • 15288 CD - System Life Cycle Processes (ballot closes 10-10)
  • 15504-6 PDTR - Process Assessment, exemplar system life cycle model (ballot closes 9-29)
  • 12207 CD - Software Life Cycle Process (ballot closes 10-10)
  • 24783 CD - Guidelines for application of ISO 9001 to Systems Life Cycle Processes (ballot closes 10-10)
  • 24773 WD - Certification of Software Engineering Professionals (circulated for comment only prior to actual CD registration ballot, circulation over 9-25)
  • 25030 FCD - SQuaRE, Quality Requirements (voting summary, Canada and US disapproved, 12 others approved, 3 abstained and 13 did not vote (again, almost half))

Other efforts include:

  • Study Group on the need for standards/guidelines related to requirements issues or requirements-related changes to existing standards, especially in the area of help for acquirers to write better requests for proposals (RFPs) and for industry to respond to such requests. Recommendations include a new standard of in-depth guidance for practitioners, a new SC7 standard incorporating IEEE 830 and IEEE 1233, and the need to address software product line (domain-specific) management and engineering.
  • New Work Item (NWI) proposal to revise 25961 on Architectural Descriptions.
  • IT Operations Study Group recommended development of a new IT governance standard, using Australia 's 8015 as a basis, but including material from Cobit (e.g., control principles). The Plenary approved further study on this topic under WG25.
  • The study group on Architecture recommended a new Working Group to address this subject, adopting IEEE 1471 as an ISO/IEC standard.
  • A new Technical Report was proposed to apply ISO 14971 to risk management of medical device software. One concern expressed by SC7 was "the proliferation of risk management standards projects within JTC1, IEC and ISO," so Jim Moore of IEEE was tasked to track the various efforts and "consult with appropriate officer of SC7" as well as "provide timely comments" to the various risk management groups.
  • An NWI for a standard on software testing will be produced, with British and IEEE standards as contributions.
  • A Study Group was established to look into standards on Software and Systems Benchmarking and Measurement.
  • WG12 (Functional Size Measurement) will cease to exist as of next year's Plenary (May 2007) in St. Petersburg .
  • Lack of participation for WG 9 resulted in it being closed with its existing work (16085.2 and 15026) transferred to WG 7.

The IEEE Software and Systems Engineering Standards Committee will meet July 31-August 2 where several of these issues will be discussed and the US SC7 TAG will meet September 18-20 most of these matters will be addressed.

As always, direct any standards-related questions to the Division's Standards Chair, Scott Duncan, at

Back to top...


Find out what's happening in the following regions:

Back to top...

Questions or comments?
Software Division Web Site

Software Division Leadership
David Walker, Chair
Rufis Turpin, Chair-Elect
Robert Stoddard, Secretary
Eva Freund, Treasurer

How can we improve Software Quality Live? Did the May 2006 issue provide helpful information? Click here and let us know!

  • Print this page
  • Save this page

Average Rating


Out of 0 Ratings
Rate this item

View comments
Add comments
Comments FAQ

ASQ News


Follow the
Software Division

Twitter  LinkedIn