IEEE Software
Engineering Standards Committee (SESC)
Management Board
12 August 2002
Location
Northrop Grumman Information Technology
1992 Lewis Turner Blvd
Fort Walton Beach, Fl 32547
Agenda attached.
Reallocation
of work.
1219 - Chair has been recruited joint effort with SC7.
1362 - Reaffirmation for this; Ted Byrne has agreed to pick this up.
1462/ 1465 - Reaffirmation of these ISO standards need to decide if want to put these out with core agenda to include ISO changes. Numbering will change to use ISO numbering rather than existing IEEE numbering, need to readopt these standards.
1517 - Bob Shillato has agreed to act as MB rep for this standard.
Projects
currently underway.
1175 - Objection was raised to this being a part 1. 75% approval has been achieved with first ballot. Need second ballot to address negatives.
610 Regrouping, need to find a WG chair.
1058 - On NESCOM continuous processing track. Should hear status within a couple of weeks.
1220 (Lohr) - Chair has been recruited and PAR has been drafted.
1016, 1320 (Byrne) 1016 maybe ballot by March 2003, on track. 1320.1 and 1320.2, should be reaffirmed.
1012 (Duncan) Have list of corrections, issue of whether to make corrections or reaffirm without corrections, and also need to address consistency issues. Can we get a working group going for this? Has a 98 publication date, needs to be completed prior to 2003. Board recommends going ahead and revising this standard with extensions providing sufficient time.
830 (Byrne) - He started the working group early this year, sending out an announcement, got a list of names, sent information to responders regarding expectations. Sent out working group rules. Several individuals who were super eager put forth their own agendas. Ted dissolved the group and requested a project plan and transferred the MB ownership to Dave Schultz. Dave has a draft PAR from John Williams, and draft project plan from Rob Schaaf.
Members of the board agreed that the PAR should not be approved. D. Schultz should send previous PAR to J. Williams and point him to website.
P. Croll - Suggested that systems and software requirements may want to both be addressed during revision; this would involve recruiting a working group chair with both systems and software experience.
D. Schultz -Proposed that the 830 discussions be moved to the ExCom agenda so that committee members could also provide insight on this matter. He also suggested that we add an agenda item to the ExCom for discussion relating to Working Group chair requirements. P. Croll suggested that we be careful requirements which may appear limiting or that promote exclusivity. R. Schaff has put together what appears to a good project plan and one that is within scope. He is new to standards development. This is a high profile group, and should probably be chaired by someone on the Management Board.
Board recommended that first choices for chair should be Dennis Lawrence or Norm Schniedewind with R.Schaaf as Vice-Chair. D. Lawrence has agreed to be chair of 830 with Rob Schaaf as Vice Chair.
Projects
we need to start.
Summarized MB items so far. Only discussion that diverged from that previously recorded is presented below:
1012 (S.Duncan) Get Dennis and Roger talking regarding changes to document and timeframe, reaffirm by next March. Whether it makes sense to reaffirm something we know needs changes, and whether Roger thinks that he could revise with 2-year extension.
Revision will include conformance with CMMI, Roger has some comments for revision, and comments that Dennis has. Dennis recommends that we extend to get short-term revisions then revised fully at a later date.
A.Ortiz Suggested making a request to the IEEE marketing department for call to volunteers if SESC needs volunteers, Karen Macabe. These announcements can be very standards specific.
1219 Jim had suggested joint development with ISO/IEC, Chair is on-board. May need to reaffirm or extend until ISO/IEC vote is returned.
1220 (C.Lohr) Have a new working group chair, Terry Doran.
1233 Have until 12/03 to determine what to do with this one. 15288 will drive 12207 revisions, and then 3-5 years down the road SC7 will start thinking of one umbrella standard for engineering processes. Should we do 15288 adoption, if there are things that we need to add to the standard for use in the US?
1233 - Need a decision by Sep 02 for NesCom,
1320.1 and .2 are mentioned in 1016 but 1016 Chair requested that 1320.1 and .2 stay as are and be reaffirmed. These are not being included in 1016, but extensively referenced by 1016.
1462 and1465 - Numbering will change to use ISO numbering rather than existing IEEE numbering, need to readopt these standards.
Summary
of Standards status (A. Ortiz)
RevCom
September agenda - 610.12, 1028,1044,1062, 1233
November agenda - 1045, 1008, 1228
1420.1 and 1420.1a, approved during June agenda.
12207.1 ask for 2 year extension; Jim M. suggested that this be done with a core agendum and then hopefully get WG7 cooperation. Core agendum is only for technical corrections, and does not open up the entire standard to review. Amendments are to add material to existing standards.
1061 - Closing on Friday of this week.
Brainstorming
for the reinvention and reengineering of the Mgmt Board.
N. Schneidewind thinks we should revise the charter, proactive vs. reactive, standards of the future, not the past. Reach out for new standards development. Standards users need context, examples and applications.
Does a generalized development standard suffice for all applications? Need context. Need guides. We have eliminated guides, general user population not happy with this elimination of guides. Need to consider development of informative sections or possibly return to guides, will help with standards adoption and use.
Recommendations
Set up a sub-committee of the MB, to research whether a generalized standard suffices for all application areas.
Undertake to reach out to wireless community who might be willing to undertake guide or develop context information in support of the wireless community. Other possible communities networks, network-centric systems, and web based systems.
ExCom makes policy for SESC. The types of things that Norm suggests are under the purview of the ExCom. Need to bring this issue before the ExCom, schedule Norm for a telecon session. Norm to participate via telecon on Tuesday (1100 PST) afternoon and Wed (0900) ExCom agenda.
Revision of recommended practice ANSI/AIAA R013, AIAA wants to make a standard when revised (R013). Reliability society has put in a PAR to cooperate with AIAA to do a standard that is within the scope of reliability and SESC. NesCom should reject the PAR because of scope not within correct society. Recommended Practice for Software Reliability. Par excludes SESC.
Jim French developed an agreement between AIAA and Reliability society. Not adopted, but did nominate Norm as chair of WG. Need an agreement between AIAA and SESC. Reluctant to let AIAA hold copyright.
Action items for the MB and ExCom are attached.
IEEE Software Engineering Standards
Committee (SESC)
Executive Committee
12-14 August 2002
Location
Northrop Grumman Information Technology
1992 Lewis Turner Blvd
Fort Walton Beach, Fl 32547
Call
to Order and Approval of Agenda (P. Croll)
Agenda attached.
Process
Mapping Tool Vendor Presentations (J. Jarzombek)
(J. Jarzombek) A lot of great IEEE standards, but practitioners not aware of content of standards, need to show mapping of IEEE standards to CMMI would help sell IEEE standards. Needs to be web enabled to support practitioners and standards developers. Tool to be provided free for hosting, in return for free advertising.
(P.Croll) Created Study Group on external Standards Coordination. Negotiated language with IEEE legal that can be used when we ask individuals to participate in standards activities, to allow for free distribution of standards for use by Study Group or Working Group members.
(J. Jarzombek) Need to address the specifics of the mapping. Need to define how the guidance work should be conducted so that it is consistent and standard. Need to list individuals doing initial mapping on website so that they can take ownership of the mapping process and answer any questions that may arrive.
See attachment.
Process
mapping tool discussion (J. Jarzombek)
Following much discussion, the Executive Committee unanimously decided to use the STC QuagMap tool in support of the mapping effort.
The following were identified as mapping effort prerequisites:
Need to identify reference models that we are going to come up with.
Need to identify core standards, and two people for each standard.
Need authors guide.
Need to negotiate with STC.
Need a project plan
Day 2 Tuesday, 13 August
SESC
Organization (Croll)
(P.Croll) Appointment of Kathy Land as Secretary of SESC.
(D.Schultz) Welcome of Scott Duncan as newest member of the SESC MB.
(P. Croll) Discussion of invitation of MB Chairs for participation as members of the Executive Committee.
(P.Croll) Role for Dennis Lawrence who recently stepped down as chair of Management Board. We have not had an archivist role in the past and there is a need for this supporting role. This has been offered to Dennis and he has accepted, he has come forward with a plan for artifact management.
(J. Jarzombek) Suggested publishing a list for ExCom and MB members of what is available in the archive.
Board has reallocated items assigned to Dennis Lawrence. Have identified projects which need to be acted upon in the coming year. We discussed upcoming challenges.
610.12, 1028, 1044, 1062, 1233 In September agenda for RevCom standards approval.
1045, 1008, 1228 Recirculation closing this week
1061 closed last night with 91% return following extension due to lack of return, 50 affirmative, 6 neg, needs to be recirculated; Norm has been notified of recirculation. If do a 10 day recirc could be ready for November ballot.
T. Byrne should there be a cover letter circulated with each electronic ballot. This is not happening currently. Is the cover letter a requirement, can this useful information be included?
A.Ortiz The current balloting letter is a template and we are allowed to submit a paragraph that can be inserted into this template for circulation. Members should send the information for this informative paragraph should be to A. Ortiz after review by D. Schultz.
D. Schultz submitted a comment regarding the recirculation of standards. Recently opened up the 1045, 1228, 1008 for recirc the notice that item is a recirculation is not prominent, this will be moved up in the template so that voting members will be made more aware that the item is being recirculated.
J. Moore We dont advertise that members can vote No without supporting commentary. There are currently two choices of comments, technical and editorial. Need to return to some type of requirement that members identify comments causing the no vote.
A.Ortiz Stated that she is confident that at some point the non-supported No vote will no longer be allowed by voting members.
610.12 There is currently no chair. Need to submit a working group change form when new chair is recruited. The form is on-line.
730 Hopefully will be approved by RevCom in November.
982 Extension until the end of 2002, Norm believes draft will be complete by 12/31 but has not issued a request for balloting. Before 12/2002 date Norm should let A.Ortiz know status as expiration date approaches. Another extension could be requested.
1016 Basil is working on draft and this is moving along.
1044 being reaffirmed and Norm is exploring possibility of establishing working group for revision; question of whether to remove 1044 in favor of 982.
1074 Par on continuous processing agenda.
1075.1 ballot is going on; negative causing a 10 day recirculation.
Scott Duncan is going to push this working group to be more progressive with their schedule. This working group needs to perform the development of the remaining 4 in parallel.
1044, 982 Action Norm, D. Schultz, Land discuss offline what to do with 1044.
1220 T. Doran PAR written and sent to Claire and Paul on 8/8/2002
Standards to be revised/reaffirmed - D.
Schultz
Expiring 610.12, 1008, 1044, 1045, 1065, 1074, 1228, 1233, 1420.1, 1420.1a, 12207.1
Paul Croll will contact D. Ringle regarding these standards.
T. Byrne How do we poll membership regarding the expiration of standards.
J. Moore no one uses the existing withdrawal procedure, which would allow members to vote on standards expiration. This information is published in the standards bearer prior to expiration.
Polled MB for any issues. D. Schultz 1233 status has not been resolved.
Need to put Administrative Procedures for Creating an IEEE Standard A guide to SESC Working Groups on SESC web site.
Discussion ensued regarding whether or not this document should be included in P&P or whether we should add guides as a fourth level or as a separate
Review of MB discussion:
He started the working group early this year, sending out an announcement, got a list of names, sent information to responders regarding expectations. Sent out working group rules. Several individuals who were super eager put forth their own agendas. Ted dissolved the group and requested a project plan and transferred the MB ownership to Dave Schultz. Dave has a draft PAR from John Williams, and draft project plan from Rob Schaaf.
D. Schultz asked members of board if anyone wanted to support the PAR, all agreed that it should not be approved.
D. Schultz - We are putting forward the recommendation that D. Lawrence act as Chair with Schaaf as Vice Chair. Alerted Dennis on possibly combining 1362 and 1233 within the scope of the 830 revisions.
P.Croll asked Jim Moore his thoughts on the possibility of combining these standards into one. Based upon ensuing discussion, the plan will be to focus 830 on 12207 with 1233 focusing on 15288.
Jim diagramed the relationships between these standards stating that there is currently a problematic relationship between 15288 and 12207. Also, there is currently a relationship between 1233, 830 and 12207. There should be a relationship between 1233 and 15288 and 1233 and 830.
1220, 1362, and 632 should also be related to 1233 and 15288.
J. Jarzombek - We should remember this and re-address these relationships during the mapping effort.
J. Moore - There are ISO groups which are working 15288, 1220 and 620 system engineering study group; 9001 9003 WG 18; 12207 9000-3 systems life cycle processes group. Our group is responsible for 1220, 1233, 830, 1362 and 12207 but we should explore links to all standards in the revision efforts of the items for which we are responsible.
P.Croll if we look at 830, 1233, and 1362 is that tight enough cluster where we want to move these together; or do we keep these separate and be careful to minimize overlap. Are these three separate closely coupled documents or does it make sense to roll one or more of them together.
Board reached consensus that the issue is really 830 and 1233; arguments were made for keeping these items separate or combining these items.
J. Moore Proposed a combined standards outline:
Concepts of Requirements Management (SWEBOK, 1220, 1362)
System Requirements Management
Process (12207conformance)
Contents of SyRS (1233, 12207.1)
Software Requirements Management
Process (12207 conformance)
Contents of SW Req Doc. (830, 12207.1)
Annex: Sample DIDs
J. Jarzombek - commented that the table of contents from each existing document could be pulled into outline with additional work coordinating the two; also stated need to have strong references in all sections of document to V&V.
P. Croll - Proposed withdrawing 830 PAR then proceed with reaffirming 830 and continue with 1233 reaffirmation and kick off new development effort for combined standard. The motion was made to continue entertaining proposals until 830 PAR is withdrawn.
Ted, Mark, Paul, Joe, Jim agreed to form study group to develop an outline for a combined 830/1233 standard.
Angela presented the proposal for three standards services tracks, Red, Blue and Green. The board presented several questions during the presentation, which have been captured as action items assigned to A. Ortiz.
Angela requested that she be ccd on any direct discussions between SESC ExCom/MB members and IEEE SA
Innovative proposal for the creation of a ExCom subcommittee called new markets for standards. Identify new technological areas, wireless, network security, agile development methods, homeland security. The Website is the place for idea solicitation. Subcommittee would be responsible for new market areas and for involving new participants who have not been involved previously. This subcommittee will perform a new business or R&D capacity.
S. Duncan, agile programming community would not like to participate because standardization is an anachronistic to what they do.
Paul challenged Norm to chair new planning group (P2) New Markets for Standards and put together charter for study group. Norm accepted under the terms that he would get SESC volunteer support. S. Duncan and M. Henley to help support Norm in this effort. Upon charter approval, the group will then move forward to implement Norms vision.
Review
of FPs (Moore/Land)
The ExCom discussed FP items presented and contributed to the drafts. These items will be finalized by Moore/Land and presented at the next face-to-face meeting.
SAG
and User Outreach (Claire Lohr/Kathy Land)
Lohr presented status and progress (SAG.doc) to ExCom with a request to add SAG to the standard ExCom agenda.
Jim
Moore, Collection Alignment/Harmonization presentation.
Jim Moore presented his liaison report (Status of IEEE CS Liaison to SC7.htm) to the ExCom.
Adjourn
for the day.
Review
of Agenda (P.Croll)
1220
PAR (T.Doran)
1220 PAR (Attach document) T. Doran voiced questions with how to proceed and concerns regarding timing. Need to add coordination with 15288, 12207, 632, and INCOSE organization.
Following review of PAR, ExCom agreed that the purpose should be revised, incorporating recommended changes, and then submitted. (Revised PAR)
Collection
Alignment and Harmonization - CMMI (J.Jarzombek)
J. Jarzombek presented two new CMMI extensions that will support the areas of Safety Engineering and Security and how this new extensions reference existing safety and security standards. IEEE does not have anything in the security area, there is an existing standard that supports software safety planning (1228) but does not address process definition.
One of the goals for these extensions is to address how the CMMI model may already address security and safety.
Joe Jarzombek presented a comparison of the CMMI vs. Agile Programming.
Joe presented a brief showing a comparison of agile programming and CMMI requirements. He also encouraged attendance and abstract submission to the Conference on the Acquisition of Software-Intensive Systems, January 28-30, 2003. (Call attached.)
Ted Byrne presented Light-Weight Development which is attached (sesc2002b.ppt). This brief presents nine ways in which agile and formal methods are not compatible. Ted suggests that we develop an interface standard. This standard could look more like a recommended practice for a set of questions a prospective agile development customer should ask to ensure product quality and long term viability of their product.
Mark Henley suggested that this question set should also address long-term maintainability. Also wants to see if Ted and Scott can get a market description, their customer and domain characteristics, from the Agile programming community.
ExCom consensus is that it is too soon for an interface standard, but a recommended (should not shall) practice a prospective customer checklist based upon existing best practices would be something worthwhile to pursue.
The next step will be for T. Byrne and S. Duncan to develop a PAR, project plan, and straw-man outline for a recommended practice. After this is circulated within SESC Byrne and Duncan could present at the Conference on Acquisition of Software Intensive Systems, held at the SEI, January 28 30.
Web
Site Review/Planning (Henley)
Discussed current issues with IEEE CS Services for Web support and possibility of moving to IEEE Services for SESC site hosting.
Discussed possibility of allowing members the ability to check to see if members are in the balloting group. This could be done via an email mechanism.
Meetings
and Workshops (Croll)
By the next telecon ExCom members were challenged to present ideas regarding possible meeting and/or workshop venues.
We are scheduled to have a track for STC, 28 April 1 May 2003. To view conference information visit http://www.stc-online.org/.
Action Item Review (Action88.xls).
Next Telecon Meeting #89, Thursday, 19th September 2002 @ 1:00 pm (EDT).
List of Management Board/Executive Committee participants
Status of IEEE CS Liaison to SC7 report
Call for papers, Conference on the Acquisition of Software-Intensive Systems, January 28-30, 2003
Light-weight development presentation