ASQ - Software Division

IEEE Software and Systems Standards Committee (S2ESC) Meeting Report

Fort Lauderdale, FL (July 17–19, 2007)

This report covers the IEEE Software and Systems Engineering Standards Committee (S2ESC - Executive Committee and Management Board) meeting from July 17–19 at the Sheraton Yankee Clipper Hotel, Fort Lauderdale, FL.

Standards Status Issues

  • 610.12 (vocabulary) will be extended for 2 years. All its content has been incorporated into ISO/IEC 24765, which combines IEEE, SC7 and PMBoK definitions; however, that SC7 work is still in process and will be balloting for perhaps more than a year. However, the online version of the current state of the definitions is available for searching at
  • 730 (software quality assurance) has had its revision proposal approved. The Working Group Chair, Ron Dean, recently emailed people who had expressed interest in 730, sending them ISO/IEC 12207 and the current 730 version, noting that a Feb 2008 in-person meeting would likely take place.
  • 829 (testing documentation) has had its effort formally extended to Dec. 2008 to allow the already initiated ballot effort to complete and to contribute it to the SC7 effort to create an international testing standards set.
  • 1008 (unit testing) will likely also be extended 2 years as it has also been offered to the SC7 testing standard new work item.
  • 1012 (v&v) has had revision proposal approved.
  • 1016 (software design) has had its effort extended to Dec. 2008, but a WG Chair change is needed and no balloting announcement has yet occurred.
  • 1028 (software reviews) has completed mandatory editorial review and the balloting group invitation has just closed, so balloting should begin before too long.
  • 1044 (software anomaly classification) needs to be revised into a process standard and it needs to be determined if including defect causal analysis is a continuing interest. Dave Zubrow has taken over from David Card as WG Chair.
  • 1045 (software productivity metrics) needs a reaffirmation by the end of the year and may need a WG Chair as current chair has been hard to reach.
  • 1062 (acquisition) needs to have work initiated on it as soon as possible.
  • 1063 (software user documentation) has been submitted for reaffirmation.
  • 1175.1 (case tool interconnection) has been submitted for reaffirmation.
  • 1175.4 (case tool interconnection) will expire by the end of the year.
  • 1175.5 (case tool interconnection) has no real chance to complete by the end of the year and has already been extended once, so could expire by the end of the year.
  • 1228 (software safety plans) needs to be extended 2 years because material from it is in a joint IEEE/SC7 project (ISO/IEC-IEEE15026). It will be withdrawn when that work is completed.
  • 1362 (concept of operations documents) needs recirculation of the reaffirmation to be initiated as there were negative comments requesting text changes.
  • 1362 (concept of operations documents) may need to be included in the scope of the effort to combine existing IEEE system and software requirements standards. SC7 would thenm be offered the combined work rather than the three base documents as is. (It was noted that nothing exists in 12207 and 15288 -- nor in 15289, therefore -- to require/expect a ConOps document.)
  • 1420.1 (software reuse library model) needs reaffirmation since there has been no news on the request to consider this standard for stabilization (i.e., left as is without the mandatory 5 year revision/reaffirmation cycle). (The stabilization idea is somewhat new for IEEE standards, so this idea is still being considered at the larger IEEE Standards Association level.)
  • 1471 (architecture of software intensive systems) needs to confirm a WG Chair change (Rich Hilliard) and then needs a work proposal revision to reflect this. The content is being contributed to an SC7 standard effort.
  • 1490 (PMI BoK) needs to be reaffirmed/dropped next year, so we need to check on the PMI’s status on revision of their BoK.
  • 1644 (naming conventions for applications software) may be revived before the work proposal expires, but it will be necessary to devise a plan for completion to request an extension.
  • 1648 (agile customer-supplier relationship) needs to revise the work proposal, ask for an extendsion, and ask for it to be issued, initially, as trial use. A meeting of this Working Group will be held during the week of the Agile 2007 Conference (August 12–17) in Washington, DC.
  • 1723 (service oriented architecture, solution reference architecture) has a work proposal scheduled for review/approval by September.
  • 2001 (web site design) has been reaffirmed until 2011.
  • 12207.0 (software life cycle processes, definitions) has been extended to allow the SC7 12207 revision to complete.
  • 12207.1 (software life cycle processes, information products) will be replaced by ISO/IEC 15289, which should be done by the end of this year.
  • 12207.2 (software life cycle processes, implementation considerations) would be replaced if S2ESC adopts ISO/IEC 24748.
  • 15026 (systems and software assurance) has been accepted as a new project based on the IEEE proposal after the prior SC7 effort had been cancelled due to lack of progress.
  • 16085 (risk management) has been promoted to Final Draft International Standard status in SC7.
  • 16326 (project management) is being progressed through SC7 toward an Final Committee Draft, which will then be submitted for mandatory editorial review on the IEEE side.
  • 20000 (service management specification (.1) and code of practice (.2)) is an adoption of SC7 documents and being chaired by Terry Doran.
  • 25051 (COTS product evaluation) adoption is being considered for how to proceed relative to the existing IEEE adoption of 12119 and the former IEEE 1465.
  • 90003 (guide to applying ISO 9001 to software) needs to have comments resolved, requiring appropriate wording from IEEE for comments against the base document, then a recirculation ballot must be initiated.
  • 1723 (service oriented architecture) has been initiated and its work proposal approved.

Balloter Categories/Descriptions

To ensure “balance” in the balloting groups for IEEE standards, balloters need to identify what “group” they belong to (e.g., user, developer, general interest, government). S2ESC feels it needs to develop a standard (larger) set of categories to ask each WG to use when going to ballot to expand the distribution of ballots and avoid the need to have to ask people to redistribute themselves into other categories for “balance” in the balloting response pool.

DHS Liaison Report

Joe Jarzombek provided a status update on the work of the Department of Homeland Security work groups in software assurance. It largely updated the status of the already existing documents that have been produced by the groups. However, Joe posed an interesting question for quality professionals to ask: “Does your software work correctly, not just in a normal environment, but in an abnormal, hostile one?” Do QA/QC personnel perform V&V in a way that answers this question?

S2ESC Policy/Procedure Review

For many years, S2ESC has had a significant set of policies (and procedure). A revision effort is ongoing to eliminate all but the fundamental policies, combining the content from the other categories (OPs and SPs) in to the FPs.

One new procedural matter discussed was to ensure that Working Group Chairs allow a 30-day minimum IEEE’s mandatory editorial review and then allow time for possible resolution of editorial comments before consensus balloting begins.

Strategic Planning

Several hours of discussion about strategic directions for S2ESC resulted in five “projects” that will be initied to pursue important issues in achieving S2ESC’s vision and mission:

  1. Creation of an orientation package for Working Group chairs to help them know what the key tasks are in running a Working Group.
  2. Consideration of how to get volunteers (and retain them) for balloting and Working Groups.
  3. A (re)statement of the S2ESC vision and mission.
  4. Examination of potential liaisons and partnerships with other (standards/models/methodology) associations and solution providers.
  5. A collection management examination to address collection architecture, expansion to cover all 12207 and 15288 processes, and possible removal of some standards to tighten up the collection.

Next Meeting

The next face-to-face meetings will be held in early or late February, 2008 perhaps on the West Coast.

Those interested in any of the topics mentioned above, or other standards-related issues, can send email to Scott Duncan, the Software Division Standards Chair, at

ASQ News


Follow the
Software Division

Twitter  LinkedIn