IEEE
Software Engineering Standards Committee (SESC)
Management Board
19 February 2003
Location
Bahia Resort
San Diego, CA
David Schultz - Chair
Kathy Land - Secretary
Ted Byrne
Paul Croll
Scott Duncan
Jennifer Longman
Bob Shillato
Claire Lohr
Agenda attached.
Standards projects currently underway – Schultz
610.12 [Croll] IEEE has agreed to provide this to SC7 without any restrictions for content. IEEE CS is working an adoption agreement with SC7 for an IEEE royalty free adoption of the final SC7 standard.
828 [Duncan/Croll] S. Duncan sent PAR to P. Croll for review on new form last week. NesCom does not currently have an electronic copy. The PAR content focuses on the development of a CM Plan rather than CM Process so the PAR needs to be re-drafted.
982.1 [Shillato/Schneidewind] Draft document has been submitted to A. Ortiz for edit/ballot. The ballot group has been formed.
1012 [Duncan/Croll] PAR has been submitted and on the March RevCom agenda.
1045 [Lohr/Croll] Par is ready for submission.
1058 [Land] Concerns with Thayer not producing a Project Plan. He is scheduled to speak to the ExCom as a whole.
1061 [Schneidewind] Pete Baxter is managing the recirculation. He has reviewed all comments, and has sent a letter to each negative balloter. All but two have responded.
1074 [Shillato] Compliance with SWEBOK, 1220, and 12207 being pursued. Chair is being encouraged to schedule at least 3 face-to-face meetings.
1220 [Lohr] PAR is in place. The working group is formed and moving forward. This is a systems engineering standard, SESC goal to harmonize this with 15288 (systems engineering lifecycle). INCOSE official liaison is in participating in the working group. Establishing a liaison relationship with EIA as well.
1320.1, 1320.2 [Croll] It was consensus of the Board that the MB should be proactive rather than wait for these to come up on the RevCom agenda. These should be submitted for reaffirmation.
1490 – [Land] Adoption of PMBOK 2000, currently in balloting.
830/1233/1362 consolidation discussion deferred to ExCom meeting
Initiating revision of all the standards that were recently reaffirmed (strong guidance from RevCom):
1008, 1028, 1044, 1045 (Pete Baxter), 1061 (reaff in process), 1062, 1228, 1233 ( with 830), 1420 (.1, .1a, .1b)
Ted Byrne is now on RevCom.
982.1 – Very close to balloting. This should be sufficient evidence of action for RevCom.
1175.2/.3/.4 –Activity for .2, .3, .4 should be accomplished in parallel
1175.5 – Carl Singer’s plan is to wait on this, but Carl needs to show some evidence of activity by the end of the year to RevCom.
1219 Need to synchronize joint development with revision of ISO/IEC 14764-maintenance standard. IEEE has 1219, ISO/IEC 14764. Idea proposed to either coordinate or combine these standards so that they are in line. Previous ISO/IEC working group chair has retired. We could adopt the revised ISO standard, or decide to have both and proceed with 1219 revision. P. Croll is writing an IEEE book on maintenance, and offered to serve as WG chair for a revision. This standard should also be aligned with the SWEBOK.
1362 Need to initiate a PAR to combine this with 1233/830; then get an extension. Discussion deferred to ExCom.
1462 is the IEEE adoption of revised version of ISO/IEC 14102. Need to request an extension and ISO revision status from J. Moore.
1465 is the IEEE adoption of revised version of ISO/IEC 12119. Need to request an extension and ISO revision status from J. Moore.
1517 is an "extension" of IEEE 12207.0 to address software reuse. Need clarification from Jim Moore.
Discussion of revisions to the SESC Guide for Standards Working Groups
- Dave has a list of suggested changes, which will be distributed to the MB members for comment and review.
- Claire has agreed to contribute some observations from the 829 effort about distance standards development
- Input from 1074 work may also be relevant
Patent Policy – SESC ExCom needs to write a procedure/policy in support of the implementation of this policy and its audit. The patent policy requires that a defined statement (attached) be read by all members of each standards working group during each convened meeting.
New Business
B.Shillato – asked
the IEEE editor (J. Longman) if IEEE style guide is a requirement and how fixed
the document structure (the multiple levels of numbering) has to be. She
replied that there is some leeway and this is based on a case-by-case basis.
IEEE Software
Engineering Standards Committee (SESC)
Executive Committee
20-21 February 2003
Location
Bahia Resort, San Diego CA
ExCom Members
Present –
Paul Croll – Chair
Kathy Land – Secretary
Ted Byrne
Scott Duncan
Mark Henley
Joe Jarzombek
Claire Lohr
Jim Moore
Dave Schultz
Bob Shillato
Roger Fujii
ExCom Members Telecon –
Allen Nikora
Jack Cole
Guests –
Jennifer Longman
Richard Thayer
Call
to Order and Approval of Agenda (P. Croll)
Agenda attached.
G47 Representative Dennis Ahern has been invited to participate as a
member of the ExCom to act as liaison between G47 and SESC. Plan to adopt the ISO amendment to
12207.0. He also represents GEIA.
There are opportunities for the participation at the ExCom level of
selected working group chairs. If there
are candidates for this type of opportunity please inform the Chair so that
their appointment can be considered.
Series began with the goal that the books produced would replace the standards guides. Books intend to get information out to users quickly. There were problems initially with book series funding.
The proposed initial 11 books are listed below:
Road Map to Software Engineering, A Standards Based Guide – Jim Moore
Software Project Management Planning, A Standards Based Guide – Mark Christensen
Software Quality Assurance, A Standards Based Guide – John Horch
Software Requirements, A Standards Based Guide – Linda Schafer
Software Testing, A Standards Based Guide – Bill Hetzel
Software Configuration Management, A Standards Based Guide – Don Schafer
Software Verification Validation, A Standards Based Guide
Software Lifecycle Processes, A Standards Based Guide – Jim Moore
Software Reuse, A Standards Based Guide – (publish) Carma McClure
Software Reviews and Audits, A Standards Based Guide – Richard Thayer
Software Maintenance, A Standards Based Guide – Paul Croll
The goal is to write a series of books in alignment and in support of 12207. These books will also be used as preparation material for the CSDP exam. The creation of a seminar series based on the books is also being explored. A digital library of items used as references in the books will be established; this will help protect against the loss of many valuable references that are becoming harder and harder to find. The books are to be written to a standard format requirement so that all books will have the same ‘reference’ feel. Electronic, on-line book materials will be hyperlinked together to provide lifecycle continuity.
The following is the Mission Statement of the Book Committee:
Provide products that promote the sale and development of IEEE Computer Society software engineering standards.
Establish an effective process to provide the correct product, at the right time and price, to the customer. This effective work process includes volunteers in vital roles (product development) and results in a revitalized CS Press.
Provide the computer science professional with standards related products and services to enable software developers with the knowledge and tools to produce software in compliance with 12207 and IEEE software standards.
Please refer to the complete Management Board (MB) meeting minutes for a complete report on MB issues.
1058 – D. Thayer
D. Thayer expressed an initial deadline estimate of the production of a final draft by the end of the year.
SESC ExCom explained the movement of standards from product to process. This would require the conversion of 1058 from product to process and 12207 compliance. D. Thayer said this would be a major rewrite. J. Moore said that ISO (ISO/IEC TR 16326 SWE- Project Management) has a PM standard that has accomplished this and that he can provide this to Thayer as a resource.
D. Thayer will provide a firm estimate to K. Land after review of the ISO standard mentioned below.
Please refer to MB meeting minutes.
There is a requirement to maintain a roster of all WG members. All MB reps are to request this from each WG chair and forward to K. Land by March 31, 2003. List should be cumulative because the lists provide legal protection to participants.
The liaison report was previously sent to the ExCom mailing list. Contact J. Moore for additional copies.
Possibilities for targeted new markets include communications and agile processes. The ExCom agreed that if no replacement for N. Schneidewind can be found as lead of this planning group then the group would be disbanded. Allen Nikora has agreed to help but does not have time to lead the group.
FP/SP/OP – Master Planning Policies Review
FP-04 Approved
SP-04 Determine correct version and redistribute
FP-09 Approved
FP-12 Approved
FP-13 Approved
FP-14 Approved, with new maintenance item.
FP-15 Approved, with additional history reference.
FP-16 Approved, with minor modifications
FP-17 M. Henley and K. Land to rewrite and resubmit this policy for review/approval
SP-02 Approved, with additional maintenance item.
The Maintenance section in each document will be updated for approved versions prior to release for web publication.
The members of the ExCom identified the need for an SP/FP dealing with the SESC position on the IEEE CS book series. K. Land and J. Moore to draft this SP/FP.
Policy on interpretation drafted but need to revisit draft due to revision of SA Bylaws. D. Schultz will lead this effort.
Paul has reviewed this procedure and will send comments to T. Byrne and D. Schultz for incorporation in the draft. The draft will be circulated to the ExCom
Discussion
postponed until March telecom.
M. Henley requests the purchase of a software package that will help him administer secure shell updates to the SESC protected web area Recommend the purchase of 2 packages, one for webmaster and one for archivist. The package cost is $115.
Restricted ExCom area is available; details to be sent to ExCom membership via email.
Next goal for web should be to add support for user group section.
The stakeholders advisory group is to target key consumers, or possible consumers, of SESC products. The SAG should be relatively small (15-25 individuals). The SESC users group is for the more general software engineering population. There is also a communication and outreach piece that will be used to support both endeavors.
The first series of SESC outreach newsletters will contain discussion on the following:
Working group needs/requests
What is new with the web site (Henley-quarterly)
SESC progress report (book series)
Request for contributions
Who is SESC (every issue)
Giveaway items, such as the CDROM used in support of the CSDP program
Opportunity to unsubscribe
Need to incorporate email addresses for all current WG chairs.
Publicity – contact Stacy Saul, design web site, create a business card type flyer.
Developing SWE as a profession.
Link from website for subscription request
Check with TCSE for advertising opportunity
Any additional suggestions should be emailed to C. Lohr.
Possible initial stakeholders might include representatives from: Microsoft, Defense SW Collaborators, FDA, Financial (Citibank), Accenture.
Need a charter/mode of operation before this can be pitched to players. What is expected from stakeholders what is their benefit?
Once a year/quarterly – call for information/report of activities
Active work on the Stakeholders Advisory Group has been stopped until outreach activities are finalized and implemented.
Standards track at STC will begin with four presentations on enabling
Capability-Based Transformation with IEEE Best Practices. These will include:
-Strategies and Technologies for CMMI-Compliant Process Engineering
(Croll)
-Strategies fir Achieving Software Dependability (Schneidewind)
-Strategies for Employing Light-Weight (Agile) Development Methods in a
Mission-Critical World – Buyer Beware (Byrne)
-International Systems Standards Harmonization – Technology Support for
Capability Transformation. (Doran)
For the second half of the track, SESC will present, in cooperation with
Defense Acquisition University, Defense Systems Management College, and
National Defense University, a half-day workshop focusing on the relationship
between software engineering and software acquisition and the opportunities for
professional improvement in the two strongly related disciplines.
CMMI Process Mapping
[Croll/Jarzombek]
Map the standards collection to the CMMI (software) to provide support to users in the application of IEEE SE standards in support of software process improvement.
Possibly start with Software Testing and Software Process Definition standards
1074, 1058, 1012
To enter data into mapping tool, you must enter the basic information. There is currently no fair use agreement so must paraphrase below main clause reference.
Data import capability from comma delimited text file, cut and paste from MS Word.
Word versions will be available for the standards.
SESC ExCom will define a process for this mapping that will include the types of volunteers that will be needed.
Paul will send out the FAA iCMM mapping to ExCom.
S. Duncan and K. Land will explore possible technical solutions for bulk document conversion/import into Quagmap.
P. Croll is currently developing the mapping plan.
Copies of this tool were distributed to each member of the ExCom present at the meeting.
SESC Executive Committee meeting: Call to Order and continuation of the agenda [Croll]
Scott Duncan has acquired a review copy of the new book Balancing
Agility and Discipline by Barry Boehm and Richard Turner. He presented a summary of the contents and
proposed that the contents of this book could be used as reference material for
a new Agile Programming Standard.
A distilled summary is that it is better to build up processes by
beginning with a small, defined set and adding additional processes when
needed.
Email S. Duncan if you are interested in acquiring a copy of this draft.
T. Byrne will complete the PAR for the Standard in support of agile
methods and forward it to P. Croll for submission to RevCom.
Jack Cole has presented a proposal to the SAB for the formation of an Information Assurance Standards Committee (IASC). SESC will coordinate with this committee to ensure that Software Engineering standards are handled correctly.
The IASC will coordinate with TAB and SAB. This coordination with both the Technical Activities Board and the Standards Activities Board may serve as a model for other committees to follow.
Strategy for Standards Maintenance [All]
Access to Published IEEE Standards [Croll]
Working groups have a
continuing requirement to access IEEE standards electronically. Requests for copies of IEEE SE standards
should be submitted to the SESC Chair.
The Chair will forward this to A. Ortiz for processing. If there is a requirement for MSWord
versions of the standards, this request should be submitted to P. Croll.
There is also a
requirement to access the ISO standards on occasion. Jim Moore is the SC7 liaison and stated that each request is
considered on a case-by-case basis.
Requests for access to ISO standards should be forwarded to Jim Moore.
Foundation Standards [Byrne]
From FP-15
“The standards maintained by SESC are classified into two categories: Foundation and non-Foundation.
Foundation standards are intended to be completely integrated into the SESC collection and to be written in accordance with all SESC policies intended to promote consistency and integration. Most of the SESC standards are Foundation standards.
Non-Foundation standards are so designated on an exceptional basis by the management of SESC. These standards are exempted from specifically listed policies. This might be because they deal with new technology, because they deal with subjects outside the central area of SESC interest, or because they are temporary or transitional in nature.”
This implies that during
each revision cycle the revision process should focus on developing the
standard such that it does not contradict, but supports, 12207 and SWEBOK. The foundation standards set should be
consistent and integrated.
CASE Tools and Internet
Best Practices are examples of non-foundation standards.
T. Byrne was tasked to
draft an initial Foundation Standards Set.
Ted developed an intial list of ‘foundation standards’. J. Moore pointed out the distinction between
the perceived importance of standards and consistency within the standards
collection. J. Moore agreed to put
together a proposed list of foundation standards for ExCom review. When complete this should be forwarded to
the Book Series Committee so that they have a clear picture of the SESC
foundation set.
There are 11 areas of
the SWEBOK. The idea was proposed that
SESC ExCom identify the subset of foundation standards that align with the
SWEBOK and 12207 and that are required for the performance of Software
Engineering.
Current SWEBOK areas:
Software Requirements
Software Design
Software Construction
Software Testing
Software Maintenance
Software Configuration Management
Software Engineering Process
Software Engineering Tools and Methods
Software Quality
12207 areas:
Primary life cycle processes
Acquisition process
Supply process
Development process
Operation process
Maintenance process
Supporting life cycle processes
Documentation process
Configuration management process
Quality assurance process
Verification process
Validation process
Joint review process
Audit process
Problem resolution process
Organizational life cycle processes
Management process
Infrastructure process
Improvement process
Training process
Current Policies and Procedures in support of Standards Consistency:
FP-11 Consistency Principle
SP-02 Reference Process
SP-08 Life Cycle Process Frameworks
M. Henley proposed the idea that we post a mapping of our standards set to 12207 and SWEBOK on the web site. The initial draft of T. Byrne’s mapping will be circulated for ExCom review and comment. He also proposed the idea that we should move away from the idea of defining a ‘critical’ subset of foundation standards and this was agreed upon by all present.
The SWEBOK area of software construction is weakly supported by SESC standards (1063). We should pursue the development of a new standard that identifies the types of things that should be included in the process of software construction.
M. Henley expressed concern that the SESC standards provide only limited guidance regarding the allocation of design to software. This is a possible candidate for a new SESC standard.
P. Croll also mentioned SESC needs a table on the website that maps SESC standards to each other. Using the QuagMap tool should aid in this goal.
The goal of SESC is to move toward the production of process standards rather than product standards. Product support information should be provided as Annex information in a process standard.
It was noted that current development efforts should focus on process rather than plan development.
T. Byrne proposed bundling 4-5 standards together for sale at a discounted price for students. J. Moore suggested that this be in alignment with the CCSE Core Curriculum for Software Engineering.
Internet Best Practices Standard (2001-1999) was developed at the SAB level. This is not currently listed on the IEEE web site as an available standard and this may be due to the fact that the standard is currently in balloting. When balloting is complete the released standard will be 2001-2002.
The published collection is out of date and questions have been raised about the completion of the update. J. Moore stated that the SA wanted to publish in March and they need introductory material. The publication target has been shifted to April. Jim thinks that the publication should be organized around the areas of the SWEBOK possibly with a couple of knowledge areas per volume.
SESC ExCom must agree on which standards should be included and then agree on the allocation of standards to knowledge areas.
S. Duncan inquired about the possibility of releasing the entire collection rather than a paper subset. J. Moore stated that IEEE does not currently have a business model that would support this method of delivery. IEEE does not currently make standards available on CDs due to a concern that they could easily be duplicated.
J. Moore will provide a recommendation of a list of standards for the content of the published collection for paper.
P. Croll and J. Moore will speak to IEEE Pubs to explore the possibility of CD publication. J. Longman will provide pubs contact information to P. Croll.
Jim Moore has provided the binning and this will be circulated for approval and/or comment.
Standards Due to Expire 2004 [Schultz]
2001-1999 – already being updated currently in ballot circulation.
1517 – Carma McClure was working group chair; J. Moore will send her contact info to B. Shillato.
T. Byrne has provided a summary report to the SESC ExCom regarding a discussion between himself, P. Croll, and J. Moore. This also included relevant discussion held in August by the ExCom.
This report is attached and comments on the report and the document outline from the ExCom members are requested.
830/1233 will be combined into one document. T. Byrne has developed an outline; contact him for a copy of what is being proposed for this document. EIA 632and IEEE 1220 will be reviewed for possible contribution to the initial document outline. It was agreed that IEEE 1362 would be considered for inclusion in the future.
American Society for Testing and Materials (ASTM)
This organization has a group of standards that have been withdrawn some of which relate to software engineering. SESC needs to decide if any of these standards should be adopted or if any contain useful information that should be included into existing SESC software engineering standards.
Standard Guide for Developing Computerized Systems – E622
This standard will not be considered; it is another life cycle model and redundant.
Standard Guide for Training Users of Computerized Systems – E625
This standard will be used as a resource for any new IEEE SE training standards development.
Standard Guide for Documenting Computerized Systems – E627
This ASTM standard is redundant with existing IEEE documentation standards.
Standard Guide for Selection and Acquisition of Commercially Available Computerized Systems – E731
Should be used as reference material in the development of any IEEE SESC acquisition standard.
Standard Specification for Software Documentation for a Computerized System – E919
This standard will not be considered for the same reasons as E627.
Standard Terminology Relating to Computerized Systems – E1013
This standard will not be adopted.
Standard Guide for Computerization of Existing Equipment – E1206
This standard will not be adopted, out of scope.
Standard Guide for Procurement of Computer-Integrated Manufacturing Systems – E1283
This standard will not be adopted, too narrow in scope. J. Jarzombek to evaluate for use as reference material in the development of any IEEE SESC acquisition standard.
2002-2003 Maintenance
Strategy and Actions [All]
12207.1 Software Life Cycle Processes – Life Cycle Data
Currently this standard is under a one-year extension. We need to make decision to reaffirm, issue a corrigendum, or completely revise. It is currently in need of revision. The revision effort should focus on the revision of existing tables and the correction of existing errors. There is no requirement to change underlying processes because 12207.0 has not yet been revised. Joint Industrial Standards Working Group created the initial document.
A revision is required and the ExCom will pursue WG chair candidates.
12207.2 Industry Implementation of 12207
If the plan is to create a corrigendum for 12207.0 then should one be completed for 12207.2 for consistency? Decision was made to reaffirm 12207.2
The ExCom agreed to package .0, .1, .2 together for a reaffirmation. J. Longman will send P. Croll a detailed description on the submission process for corrigendum.
1062- IEEE Recommended Practice for Software Acquisition [Jarzombek]
The DoD will lead this due to the congressional approval of the Defense Authorization Bill. Currently staffing OSD for requirements established by the approval of this Bill.
Considerations for
Software Acquisition:
Measuring Performance
and Improvement
Impact on acquirers
and developers
SW Product Maturity
Software TRLs (Technology Readiness
Levels)
Impact on Development Source
Selections (that are not COTS-based)
Develop a new standard
that identifies the types of things that should be included in the process of
software construction.
Develop a new standard
that provides guidance in support of the allocation of design to software.
Develop a new standard
for training process described in 12207 using ASTM E625 as reference
material. Need to form a study group to
determine feasibility and possible WG chair and liaison organizations.
During the course of the
1062 revision, consider the possibility of the development of some type of
software product maturity standard.
(ISO 15939)
Meetings
and Workshops (Croll)
We are scheduled to have a track for STC, 28 April – 1 May 2003. To view conference information visit http://www.stc-online.org/.
Telecon #95, March 12 1:00 pm (EDT); Dial in information: (517) 267-1465, then participant code: 946433.
Telecon #96, April 16 1:00 pm (EDT)
Centennial Meeting (#100); Week of August 11th is being considered as the meeting week, in Ft. Walton Beach, FL.