IEEE Software Engineering Standards Committee (SESC)
Management Board
11 August 2003
Participants
David Schultz, Chair
Kathy Land,
Secretary
Paul Croll
Ted Byrne
Jim Moore
Claire Lohr
Mary Beth Chrissis
(SEI Liaison)
982.1
[Schneidewind] Submitted for IEEE ballot, May 7, 2003. PDF version provided for balloting June 12,
2003. As of July 22, balloting status
is: 17 approve, 3 negative, 4
abstentions.
1016 [Byrne] Meeting held on July 25 to finalize
draft 3.0. This will be the last review
prior to ballot. Draft 3.0 is expected
to be circulated in October with comment resolution completed by January.
1058 [Land]
Revision complete and comments from the initial circulation to SESC
ExCom will be made available to ExCom members.
1061
[Schneidewind] Reaffirmation. Pete
Baxter is initiating the recirculation.
All but two negative balloters have changed their votes to
"affirm." Pete is trying to
contact them.
1062 WG for revision has not yet been
formed. J. Jarzombek will prepare a
PAR; he is seeking guidance from SESC on when to start up this effort.
1175 [Duncan] Work is ongoing on 1175.3. Balloting is not expected before 2004. The
PARs for 1175.2 and 1175.4 have been extended until December 31 2005.
1219
[Croll] Tom Pigoski, the ISO/IEC chair of 14764, has agreed to serve as ISO/IEC
co-chair for a coordinated revision of 1219 and 14764. Paul Croll will serve as IEEE co-chair. PAR has been submitted (Sept agenda); WG
will form when initial draft is complete.
1320.1,
1320.2 [Byrne] Ted has initiated the reaffirmations.
1362 [Byrne] This will be eventually be
harmonized with the new 1233/830. We
don't plan to submit a PAR any time soon, so we need to request an extension.
1490 [Land] IEEE adoption of the PMBOK -- 2000
edition. High priority. PAR was approved by NesCom on 8/15/02. First ballot closed February 19, 2003;
10-day reballot completed in June 2003; next step is RevCom submission.
1517 [Shillato] This is an extension of 12207.0
to address software reuse.
We
need to initiate reaffirmation in 2003.
Bob Shillato tried, without success, to contact Carma McClure so that
she could help with the reaffirmation.
Jim Moore is trying to locate contact information for Carma.
1648
[Byrne/Duncan] Agile Standards Development -- PAR received at NesCom for
resolution at the September 11 Standards Board meeting.
2001 [Moore] Responsibility was transferred to
SESC in November 2002. IEEE 2001-2002
was approved on January 31, 2003. It
replaces 2001-1999. We intend to
fast-track this document to SC7.
12207
set [Croll] Paul Croll is contacting
Jim Sturges, of EIA, to initiate a joint IEEE/EIA revision effort for
12207.0. We need, though, to initiate a
joint IEEE/EIA reaffirmation of the entire 12207 set.
16085 Revision of IEEE 1540; coordinated revision
with ISO/IEC 16085. We are adopting the
ISO/IEC number. Standards Board approved the PAR on June 12, 2003.
For a
complete summary of standards activities refer to the attached standards matrix.
Angela
Ortiz is currently on maternity leave; she will return the 15th of
September. Gregory James is acting as a
temporary replacement; g.james@ieee.org
or (723) 562-3809.
Jim
Moore stated that many of the supporting clerical activities that have been
performed recently by SA liaison should not have been accomplished and these
are the responsibility of the MB reps.
830/1233
Consolidation [Croll/Bryne/Moore]
Ted Byrne is working on a document that combines these standards. This document will be used to measure the level of acceptance among members of the ExCom for project continuance. Paul to send Ted a copy of SEI CMMI for information purposes.
1074
John Napier is the WG Chair. A SESC Project Review is scheduled for June, 2004. Further information is available at project web site, http://sa-eng.com/1074. A meeting was held June 19-21 in Richland, WA. At this meeting there was a disagreement regarding how consensus is to be reached within the WG. There are rules in the Computer Society P&P for working groups and John will be advised to review these rules for resolution of the issues that they are facing with 1074.
Standards
Revisions
1008, 1028, 1044,
1045 (Baxter), 1061 (reaff in progress), 1062 (Jarzombek), 1288, 1233 (w/ 830),
1420.
Suggestion to
post these on the web site and ask the standards community two questions:
Is this standard still current and is the content still valid?
1362-1998
We don’t plan to submit a PAR any time soon, so we need to request an extension.
1462-1998
IEEE adoption of revised version of ISO/IEC 14102 - we need to request an
extension.
1465-1998
IEEE adoption of revised version of ISO/IEC 12119 - we need to request an
extension.
1471-2000
Action required in 2004; revise for consistency with forthcoming IEEE adoption
of 15288. Paul made the suggestion that
we contact Mark Maier and Basil Sherlund regarding their opinion regarding a
revision.
1517-1999
Reaffirm and contribute it to ISO for a revision of ISO/IEC 12207, to address
software reuse. We’re trying to locate
contact information for Carma McClure so that we can invite her to participate
in the reaffirmation.
14143.1-2000
Action required in 2004; feed IEEE changes back to SC7 for their revision. Following the ISO revision SESC will
initiate adoption
Interpretations Procedure (#22) –ProCom is preparing material for the next
update of the operations manual, which will be ready in January.
Work
Planning Procedure (#23) - Paul is reviewing Ted’s proposed text.
Archiving
Procedure (#24) – Balloting has been completed; the approved procedure is now
available on the SESC web page.
Ted Byrne – 1016 (active), 1320.1, .2 (both to be reaffirmed), 1362 (on hold pending 830/1233 merge), 1648; 830/1233 document.
Paul Croll – 12207.0, .1,.2 (contacting EIA to initiate joint revision); also chair of 1219 (starting up)
Scott Duncan – 828 (active), 1648, 1012 (active), 1175.2-5; also proposed chair of P1648.
Kathy Land – 610.12 (SC7 has the lead), 1058 (active), 1490 (active), 1644 (starting up), 14143 (2004).
Claire Lohr – 1045 (active), 1220 (active), 1471 (2004), chair of 829.
Jim Moore – 2001 (SC7), 16085 (SC7).
Norm Schneidewind – 1062 (starting up), 1233 (merge with 830 and 1362, need WG chair), chair of 982.1, 1061 (reaffirmation), and 1633 (AIAA R-013) - refer to the P-1633/AIAA R-013 Status Report.
Dave Schultz – 830, 1074 (active), 1219/14764, 1462, 1465
Bob Shillato – 829 (active), 982.1 (active), 1044, 1517 (reaffirmation)
All of the ‘top five’ items submitted were directed more toward SESC itself than the MB, and have been moved to the ExCom agenda, item #9.
Officially the MB is responsible for overseeing the activities of the working groups that are formed to develop, revise, or affirm IEEE software engineering standards.
IEEE Software Engineering Standards Committee (SESC)
Executive Committee
12 - 14 August 2003
Location:
Sheraton Yankee Clipper Hotel, Fort Lauderdale, FL
Purpose of the Meeting:
Address specific SESC management issues
Review progress of ongoing projects
Review
action items
Participants
Paul Croll, Chair
Kathy Land, Secretary
David Schultz
Jim Moore
Ted Byrne
Claire Lohr
Yvette Tanious
Mary Beth Chrissis
P. Croll conducted a review of the current SESC ExCom and MB organizations.
D.
Schultz provided a brief recap of the items discussed during the MB meeting
held 11 August. For a detailed review
of the MB activities please refer to the MB meeting minutes and standards
listing.
This was
developed to provide succinct detailed guidance to WG chairs. This has been balloted and approved and is
now available on the SESC website: http://standards.computer.org/sesc/.
The IEEE currently indemnifies WG members against liability. In order to accomplish the indemnification the IEEE must have a roster of each WG. These rosters have been received for several of the active working groups, however many of the rosters remain to be submitted. Please refer to the standards matrix for a list of the working group rosters and their roster submission status.
T. Byrne had the suggestion that as standards are submitted for publication that the members listed as contributors be covered by indemnification. P. Croll discussed the advantage to SESC of having a current list of the members for each working group. This should be a requirement as part of the start up and maintenance of an active working group. The suggestion was made that this be included in the guide to working groups. This would be a great source for user outreach activities.
D.
Schultz provided a review of items currently under ballot. For a complete list of these items please
refer to the standards
matrix.
SESC
Balloting Pool issues [all]
D.
Schultz discussed possible procedures for maintaining the integrity of the
balloting pool. Do we want to be
responsible for the integrity of the balloting pool?
Currently
the way you join SESC is through the Technical Council on Software Engineering
(TCSE): http://www.tcse.org/. When you
join TCSE you check that you are interested in participating with the
development of software engineering standards.
That list gets reconciled against the IEEE list that overwrites the TCSE
information.
D.
Schultz summarized the process for standards preparation for balloting. WG Chairs are responsible for adhering to
the IEEE SA Style Guide.
(http://standards.ieee.org/resources/index.html#guides) Discussion ensued regarding the creation of
a checklist procedure that would provide some additional structure and guidance
for WG chairs.
Each
ExeCom member has been asked to review the Guide
for Working Groups and compare this guide against the procedures
established on the SA web site.
J. Moore
presented his Report to IEEE CS SESC: Report of
IEEE CS/SC7 Liaison to the SESC ExeCom.
The SESC
ExeCom approved the coordination procedure.
Jim will send this procedure for formal addition to SESC procedures.
D.
Schultz made a motion to move forward with the adoption of 15288. Paul Croll provided the second. The motion was approved to adopt 15288. The next step is for J. Moore to create a
PAR for adoption.
J. Moore
suggested that Perry deWeese act as
co-editor for the 12207/15288 harmonization supporting Alain Faisander, the
editor.
J. Moore
provided a review of the Resolution of Instructions
to IEEE CS liaison to ISO. K. Land made a motion to approve
the revision of this document, D. Schultz made a motion to second. The motion was passed by unanimous consent.
SESC Web Page [ Henley ]
Recent
additions to the web site include:
Posted
the new Guide for Working Groups
Posted
the new procedure #24 on Archives
Posted
the call for participation in WOSA 2003
Posted
the Minutes from meeting #99
Updated
date for standards status on the Mgt Bd page
Mr.
Moldavsky added to the org chart
Roger
Fujii’s name corrected on org chart
The
current content is satisfactory to members of the ExeCom.
M. Henley
was given an action item to determine the types of policies and procedures
needed to support the operation and maintenance of the SESC web site.
The members of the ExeCom have been assigned an action item to provide feedback to M. Henley by the next telecon regarding their preferred content for the protected user area.
Mark has
provided feedback to P. Croll stating that we have the current capability to
launch web based surveys. Any type of
survey capability would be launched from the User’s Group page.
Waiting on materials for second newsletter/email.
K. Land will consolidate the WG rosters and provide the mailing list to C. Lohr for addition to the User Outreach mailing list.
The next logical step for user outreach will be to formulate and launch a web-based survey from the User’s Group section of the web site.
Discussions about what should be targeted in the upcoming STC ’04. The deadline for input to Paul Croll is August 29, 2003.
Claire Lohr is acting as Chair for a panel at the ASQ conference, Oct. 2003. The title for the panel is ‘ Current Trends in Traditional and Non-Traditional Standards‘ comprised of Herb Krasner, Claire Lohr, Scott Duncan, and James Bach.
The following has been accepted for the Fast Abstracts track of ISSRE 2003, Denver, CO, 17-20 Nov.,
“Marrying Software Fault Injection Technology Results with Software Reliability Growth Models”, Jeffrey Voas, Cigital, Norman Schneidewind, Naval Postgraduate School.
The Road Map to Software
Engineering – James Moore
Software Project
Management Planning – Mark Christensen
Software Quality
Assurance – John Horch
Software Requirements –
Linda Schafer
Software Testing – Bill
Hetzel
Software Verification
and Validation – Roger Fujii
Software Reviews,
Inspection & Audits – Richard Thayer
Software Configuration
Management – Don Schafer
Software Maintenance –
Paul Croll
There are two
additionally proposed titles –
Software Risk Management
Software Life Cycles
For additional information
regarding the book series please refer to the attachedbook series status report presentation.
The SE Portal project
is an alternative way to provide services to IEEE membership.
Mission Statement: SEEK (Software Engineering Expert Knowledge)
will be the most trusted, noncommercial, and objective source of software
engineering knowledge.
Committee members
defined 4 Categories of Users:
Practitioner
Researcher
Educator
Student
J. Moore led a
discussion regarding the SE Portal development. He solicited comments and suggestions for feedback to the members
of the SEP committee.
New Standards/Standards Harmonization
Agile
Programming [ Byrne/Duncan ]
A draft of the
IEEE Recommended Practice for Establishing and Managing Software Development
Efforts Using Agile Methods (P1648)
Overview – This
Recommended Practice describes a set of procedures that a software development
client should use when interacting with a software developer who uses the
so-called ‘Agile’ development methodology.
Scope – This
Recommended Practice describes a process that a software development client
should adopt and use in contracting with and working with an ‘Agile’ software
developer. It is intended that both the
technical and project management personnel should apply these recommendations
to be aware of and control the three aspects of software development: development status of specific features,
progress through the development cycle, and expenditure of contract funds.
Software
Naming Convention [ Tanious ]
Yvette A Tanious, Project Engineer, Naval Sea
Systems Command/04M53, TaniousYA@NAVSEA.NAVY.MIL
The Navy has
identified consistent issues resulting from a lack of available standards
supporting software-naming conventions.
This problem is not limited to this branch of the DoD, rather it is a
problem which is pervasive throughout industry. Yvette is the Chair of the WG to develop a standard Software
Naming Convention as a recommended practice to be used for developing
nomenclature for software applications.
The SNC is independent and will not impact the coding or the purpose of
the software itself and it will not control the mechanism of the writing or the
development of Software codes or programs.
For additional
information please refer to Yvette’s attached presentation.
Please refer to
the minutes of the SESC Management Board meeting which have been released
previously and are available on the SESC website (http://standards.computer.org/sesc/).
The SESC Risk Management standard has been fast tracked into the ISO process. The PAR for the risk management project has been approved. The desire is to take the existing draft and go to CD registration very soon.
Please refer to the CASE Tools Standarization Status charts contained in J. Moore's Report of IEEE CS/SC7 Liaison to the SESC ExeCom presented earlier in the meeting.
FP-17 is
awaiting review from Mark Henley. P.
Croll expressed concern regarding the need to describe maintenance items
associated with items posted on the web site.
The ExeCom was directed to consider this matter.
P. Croll
directed the ExeCom to send any relevant material that could be archived to D.
Lawrence.
CMMI Process Mapping [ Croll/Jarzombek ]
P. Croll provided the
group with a demonstration of Quagmap and a mapping issues CMMI Mapping Issues summary. Quagmap supports mapping organizational and projects’ process
documents to each other and to various compliance frameworks.
K. Land suggested a
two-level approach to the mapping process with one focus being a high-level
mapping and detailed gap analysis. Discussion regarding the mapping approach
ensued and J. Moore suggested a third approach that would be to provide the
user community with a way to use IEEE standards for process definition. K. Land suggested the creation of a
high-level one-page slide for web-site deployment that shows how IEEE Standards
support the process areas of the CMMI (staged).
T. Byrne suggested that
the group take the existing CMM/12207 mapping and map this to our standards
set. J. Moore countered that this would
provide too much detail and should map from the primary processes of 12207 to
the software CMM.
The group agreed that
the mapping priorities should be:
1st priority
– provide a high-level mapping from the software CMM and CMMI (staged) by
Process Areas to IEEE Standards by name.
K. Land and P. Croll to provide initial draft to SESC ExeCom.
2nd priority
– how to do process definition based upon framework of process references
3rd priority - detailed mapping from the CMMI to IEEE
Standards by Clause
P. Croll discussed some
of the framework issues that he has been considering:
There is a limit of 255
characters in the framework note and the description field within the Quagmap
Tool.
T. Byrne has created a
tool that will provide the standard major subclauses in a Quagmap ready
framework.
Need to determine the
level of granularity; specific practice to clause is the eventual target.
CM of input files.
Mapping issues were also
discussed:
Directionality
– IEEE Standard to CMMI or CMMI to IEEE Standard
Knowledge
requirements for mappers
Mapping
Note space limitations and level of detail (who created, creation date, contact
information)
Mapper
screening and selection criteria
Peer
review of Frameworks and Mappings
SESC
oversight
M.B. Chrissis suggest
that SESC put out a data call to find out if anyone in SESC community has
previously accomplished a CMM/IEEE Standards mapping.
Instructions
to mappers
Schedule
management
P. Croll stated that we
should be sure to include schedule objectives in the volunteer licensing
agreement.
File consolidation and reconciliation
Web site transfer
Publicity
Change tracking and alert responsibilities
Update responsibilities
Continuing Quality Management
D. Schultz brought up
the idea of mapping to 9000-3, which currently shows 12207 traceability. This mapping should be much easier to
accomplish.
SESC
Product Line: Standards and Information Products [ All ]
The committee determined
that this is not to be pursued due to the existence of the 12207 amendments
containing the reference processes.
P. Croll solicited any ideas for training materials, flyers, brochures, etc from members of the ExeCom. Paul presented the currently available ‘Best Practice Information Aids Flyer’ as an example.
MB Chrissis suggested developing a flyer that discusses all the current SESC activities.
C. Lohr was asked to review the online training course for CSDP. The materials did reference the standards but the material presented was terrible. K. Land to determine CSDP project status and report back to SESC.
D. Schultz presented the following issues for discussion:
How can we help WG chairs and members understand what
they're committing to when they lead or join a WG?
How can we/do we want to actively search for new standards
to write? (e.g., wireless software)
How can we review and simplify our SESC policies and procedures. (Attempt to ascertain usage rate by WGs)
How can we search for new WG chairs?
Should we create a database or
spreadsheet with names and contact information for past WG chairs?
How can we publicize the value of
standards and the standards process? (There is a need to project
enthusiasm and passion for what we are doing in order to attract users to our
standards.)
K. Land suggested that
these issues should be addressed in a sustainable way. P. Croll suggested that the available
vice-chair of planning position be offered to P. Voldner using the questions
listed above as a place to focus the planning activities.
Please refer to the
attached action item listing. Notify K. Land of any changes in AI status.
September 17th, 12:30 Eastern
The next meeting is co-located with the SAB meeting, and will be held in Savannah, GA sometime during the week of Feb 24th – 28th, 2004.