IEEE Systems and Software Engineering Standards Committee (S2ESC)
Executive Committee
Minutes of Meeting # 119
Meeting Dates: Monday, February 28, 2005 – Wednesday, March 2, 2005
Meeting Location: Software Engineering Institute (SEI)
NRECA Building, Suite 200
4301 Wilson Boulevard
Arlington, VA 22203
Phone: 703-908-8200
Attendees:
Paul Croll, Chair
David Schultz, MB Chair
Kathy Land, Secretary
Mary Beth Chrissis
Scott Duncan
Roger Fujii
Mark Henley
Joe Jarzombek
Keith Middleton
Jim Moore
Carl Singer
Debra Sparkman
Mike Waterman
Yvette Fischer (Telecon)
Claire Lohr (Telecon)
A Special Note of Thanks: S2ESC would like to thank Mary Beth Chrissis and the SEI
for graciously offering to host this face-to-face meeting.
The purpose of the meeting is to do the following:
Address S2ESC management issues
Review progress of ongoing projects
Review action items
Call to order and approval of the agenda [Croll]
Review of old action items [Land/Croll]
Please refer to attached action item listing.
Status Reports / Issues
Management Board [Schultz]
829 – The PAR change was submitted; unsure if this made the NesCom agenda.
830/1233 – ExCom agreed that this PAR needs to capture the requirement that this
combined standard should be a process standard while retaining the practical guidance in
the form of (normative) annexes.
1008/1028 – D. Lawrence has agreed to chair these WGs; he plans to begin this summer.
1016 – Final WG review, considering PAR extension due to scheduling and work
conflicts. The group is one WG meeting away from final draft.
1045 – Current roster needed for this group from P. Baxter; C. Lohr will remind him.
1058 – New PAR has been drafted and is ready to be circulated to the ExCom.
1062 – 15288 has been approved. Need to draft a PAR. Need to evaluate available
content in addition to the existing IEEE standard.
1074 – The group just met in Sacramento and is on track and the draft coming out of that
meeting will be the draft that will be balloted. The draft is being revised to tighten the
linkage to 12207.
1175 – .1 and .3 are complete – .2 is about 1 paragraph away. .4 have made some leaps
in terms of individuals on the committee and the vision of where it is going – planning to
extend the PAR for a year. .5 is an assemblage of administrative things and will be
accomplished following .1-.4. Although the working group has a roster of about 8
individuals, 4-5 actively support the draft development due to funding and support
constraints.
1220 – This was just submitted to RevCom.
1228 – Possibility of linking with ISO/IEC 15026, need to work with SC7 to broaden the
scope of 15026 and then include 1228 as a normative annex.
1362 – Current PAR extension is only through end of 2005, to give us time to consider
whether to merge 1362 into the 1233/830 combination. J. Moore stated that he did not
think that the linkage between 1362 and 1233/830 was sufficient. We agreed, on the
basis of Jim’s argument, to keep 1362 separate from 1233/830. Need to put in a 2 year
PAR extension. A project plan must be completed prior to the request for the PAR
extension. This standard was created in 1998; reaffirmation may be an alternative. C.
Singer and D. Schultz will determine whether to reaffirm or revise.
1648 – S. Duncan has received draft material back and is trying to work with three
groups to begin to move toward a draft. Will raise the issue of 12207/15288 and how the
group will address these standards from an agile perspective.
12207 – Ballot coordination with EIA point of contact, Dr. John Noblin, will be
contacted this month.
P14764 (revision of 1219) – There is a ballot comment regarding the title of the standard,
this comment has been rejected and the standard will move forward.
P15288 – Approved by RevCom, this standard will be published.
Projects to Initiate in 2005
610.12 – Need to take some action on this, comes up for renewal in 2007.
730 – Need to start something this year. Anticipate beginning this summer. J. Moore
commented that 730 needs to be changed from product to process and that the standard
needs to be aligned more closely with 12207.
1008 – Overdue, D. Lawrence starting this summer.
1028 – Overdue, D. Lawrence starting this summer.
1044 – Draft PAR submitted and on NesCom agenda. Dave Card is the WG chair. This
standard is taxonomy for software anomalies. Dave is turning this into a process
standard.
1045 – Pete Baxter has this moving along. Dave Card is reviewing comments from
previous ballots.
1063 – Scott will talk to Annette regarding committing as WG chair.
1420 series – These standards essentially are a data model for how reuse library items
should be labeled to provide for interoperability. These are very specialized and do not
support the reuse process. May want to consider withdrawing this series of standards;
need to contact the past editor(s) and see if they are interested in doing a revision. The
past chairs of these were Theresa Hobbs and Ed Comer.
1471 – WG Chair has been assigned and is working on a PAR.
Conformance to 12207 – need guidance on a case-by-case, standards basis, a set of
recommendations for each standard so that when revised the WG chair has some MB
guidance and the MB has a set of requirements that can be used to validate this
requirement when the final draft is reviewed. A by product of this effort would be a set
of 12207 conformance requirements for standards developers. Kathy Land has
volunteered to lead this effort and will solicit volunteers from S2ESC ExCom for each
standard. This will be called the 12207 conformance study group.
Balloting Status [Ortiz]
No report.
Working Group Status/Issues [Schultz]
Indemnification/WG Rosters [Schultz/Ortiz]
D. Schultz would like to remind all WG Chairs that it is time for the yearly resubmission
of WG rosters for the purposes of indemnification.
Stabilized Standards [Schultz]
This has been discussed previously. S2ESC has a list of candidate standards. D. Schultz
will circulate the list to the ExCom.
New Standards Opportunities [Moore/Croll]
The group reviewed a proposal for standard on systems integration from Dr. Rashmi Jain.
He makes the point that there are shortcomings regarding systems integration in the
standards arena. P. Croll will invite him to chair a study group to determine the viability
and direction for a standard in support of systems integration.
As a group, the ExCom and MB need to expand and solidify our footprint within systems
engineering.
The study group should look at the scope and characteristics of the standard in question:
Outline specific subject area
Outline use of new, existing, or reference material
Determine recommended content
Additional attention to open source, elicitation of interface specifications, and security.
Attention to the following standards: 15288, 12207, 1471, 1233, 1362, 1220, 1644, and
16085
IEEE Editorial Process [Ho Sang]
Y. Ho Sang presented a review of the IEEE editorial process for the benefit of the
management board representatives. The first step where editor gets involved is the PAR
form (numbering, title, copyright, IP issues). The next interface would be with a review
of the document. There is a mandatory editorial coordination that all projects must go
through. The document is submitted for editorial coordination at the same time invitation
to ballot is issued to balloting pool. At this time editors review the document for three
areas of concern: 1) identify items that need to be corrected where the document would
not be allowed to go to ballot if not addressed (eg., title or scope not mapping to the
PAR). 2) All permissions associated with the document must be submitted. Claudio
Stanziola would be involved to negotiate any agreement. 3) Safety, environmental issues,
or cautionary items in support of legal review.
The second phase of the editorial coordination addresses items that need to be addressed
prior to final recirculation. Issues that have been identified by balloters and others (eg.,
normative references) and ensure that all changes are reflected in the final ballot.
Anything that might change the technical status of the document must be approved by the
balloters in order to be accepted by RevCom. The third phase consists of editorial style
support. This information does not affect approval but needs to be accomplished prior to
publication.
A final RevCom review is done prior to submission to RevCom. Any issues that may
prohibit approval are addressed and comments are submitted to RevCom. Dave Ringle
circulates comments to WG Chairs and gives Chairs opportunity to address these
comments so that they may be presented during RevCom review.
Prior to publication the final electronic copy is compared to what was balloted. Editorial
changes are made and then the document goes through editorial peer review. Then the
standard is uploaded to Standards Online and the IEEE Electronic Library. At this time
the document is also sent out to be printed. The print document is usually available three
weeks after electronic version is available. Only electronic complementary copies are
now provided, and these are sent out and nominations for awards are submitted.
A new Word template is being created in support of working group chairs to enable the
standards publication process. Request that Figures be supplied in a non-editable form.
Suggest that the WG submit the source of the electronic file for archival purposes. It is
important that any figures be grouped, minimum of 300 dpi, and uneditable in order to
avoid problems.
Working Groups often need a .doc to support revisions of existing standards. It is
currently not possible to provide a mirror image copy of published standards. The text
for the most part is in tact – the figures and tables often do not come over cleanly. Please
find her presentation attached.
Liaison Reports
ASQ Software Division Liaison [Duncan]
These activities are ongoing. Trying to increase attention to software within the ASQ
organization and thereby increase attention to standardization of software engineering.
DoD Liaison [Jarzombek]
J. Jarzombek reported on DoD software assurance activities. This report is attached. Joe
presented the DoD emphasis to risk mitigation of software exploitation in critical
software. Next DoD-DHS SW Assurance Forum 11-12 April, 2005 in Alexandria, VA.
Website: https://enstg.com/Signup/default.cfm (conference code: SOF60973).
NASA JPL Liaison [Nikora]
No report.
SC7 Liaison [Moore]
J. Moore presented some background information regarding the integration of software
engineering standards. This report is attached. Discussed ongoing harmonization
activities slide 14 is of particular interest and addresses the harmonization challenges
between 12207 and 15288. Slides 16 and 17 present the status of harmonization efforts
in 1994 and the status of harmonization efforts today. Jim also presented the report
“Vision of Liaison Outcomes IEEE CS and ISO/IEC JTC1/SC7”. This report is attached.
SEI Liaison [Chrissis]
The SEI Configuration Control Board request to become a pilot organization is coming
out soon. SEI is eliminating advanced practices in version 1.2. The notion of
constellations is being expanded, concern about how this affects the end user. Northrop
Grumman is piloting the services/maintenance model. Services represent more than half
of all DoD acquisition budget. Hal Wilson from Northrop Grumman states that you are
going to do continuous process improvement and then assessment based upon stages.
Discussion ensued as to the possibility of standards related to software and systems
engineering services.
J. Moore mentioned that BSI 15000-1/-2 is fast tracking IT services management
standards (practices and specifications) through ISO and these standards may be
incompatible with the CMMI approach. The SEI had concerns with 15504 and CMMI
compatibility and because the standard is taking so long, this is less of a concern. Jim
stated that the BSI standard would probably be finalized in January 06.
The primitive model – the basic set of process areas for required use, the SEI is trying to
be very careful not to provide non-compliance/use loopholes. A briefing is attached. To
summarize, new SCAMPI V1.1A will be available mid 2005. There is a possibility of a
move from maturity levels to capability levels, a more assessment driven model. Also a
move away from staged representation from DoD community. SEI is trying to remain
focused on the needs of the entire user population – both DoD and commercial.
Ukrainian Software Engineering Training Center Liaison [Moldavsky]
No report.
DOE Liaison [Sparkman]
D. Sparkman reported on DOE standardization activities relating to safety system
software, safety software, and safety management and administrative controls software.
This report is attached.
S2ESC Web Page [Henley]
Mark will update the website with Procedure 24, which was approved at this meeting.
Additional updates:
1.
2.
3.
4.
Points of contact are listed on the Contact S2ESC and Contact Us pages.
FAQs are listed on the Help page, and with a link on the General Info page.
The S2ESC Flyer is posted on the General Info page.
The WG Roster template has been updated to open with correct format.
Bill Rini sent an email regarding new tool for hit metrics. Mark has sent an email
inquiring as to when this tool will be available for S2ESC.
User Outreach [Lohr/Land]
Mary Beth Chrissis provided the User Outreach committee with examples of SEI
outreach material and volunteer evaluation criteria.
Meetings and Workshops [Croll]
For the last several years we have provided a track for the SSTC conference in Salt Lake
City. The conference is becoming more DoD focused. S2ESC is looking for other
conferences to link up with.
SE-Online [Land/Lohr/Croll]
P. Croll discussed the recent face-to-face meeting held in Madrid, Spain (refer to attached
presentation). The meeting was very productive and all involved feel the group is on
track. Paul is area editor for Software Engineering, Claire Lohr is area editor for testing
and standards, Carl Singer is the area editor for process, and Kathy Land is area editor for
Project Management and SWEBOK.
All area editors are now looking for content contributors. Contributors get the
recognition of having their Bios posted along with their contributed content. If you
would like to contribute please contact Paul, Kathy, Carl, or Claire.
S2ESC Archivist [Lawrence]
No report.
S2ESC Study Groups
High Integrity Systems Study Group [Moore/Croll/Sparkman]
J. Moore described some of the work of ISO subcommittees in support of language usage
to prevent vulnerabilities. This group is within SC22. Recent ISO level report on how
ISO should react to terrorism in recent years. The work completed regarding IT in this
report was naïve. J. Jarzombek and J. Moore are trying to figure out how to use the DHS
SC& U.S. delegation to broaden exposure of this topic to SC27. This coordination
should be further expanded to include SC7, SC22, SC27 and S2ESC.
The High Integrity Systems Conference is being held in March.
Quality Management Study Group [Duncan]
S. Duncan reported that J.Walz is focusing on 9001 and 90003, Scott is trying to move
the focus back on the examination of gaps within these standards.
S2ESC Standards Collection [Moore/Croll]
The current software engineering standards collection is on CD-ROM. It is about time to
update this collection. Please send suggestions to Paul or Jim for supplemental CD-ROM
content.
S2ESC Policies and Procedures – In Depth Review [Croll/Duncan]
Paul deferred this agenda item until John Walz was available. It will be rescheduled for
the April telecon.
S2ESC Strategic Planning [Croll]
The majority of active participants are from DoD-type organizations. How do we reach
out to other organizations? Each WG chair has the responsibility/opportunity to reach
out to relevant groups of subject matter experts.
Local presentations identify conferences – work to get individuals in the local area to
present.
List of conferences (TCSE website) is available. Also, TCSE is the parent of S2ESC in
the technical management structure (not standards management structure).
S2ESC Business Strategy for 2005
Adjourn
Tuesday, March 1 – S2ESC Executive Committee Meeting (Cont.)
Call To Order And Continuation Of The Agenda [Croll]
Book Series [Fujii]
The book series is moving forward slowly. Karma McClure has completed her book on
software reuse. J. Moore has completed his book and it should be published this year.
CM book is currently in peer review. Roger suggested the possibility of a teaming
arrangement between co-authors. The current authors would remain the primary authors.
Individuals who are interested in authoring or co-authoring a book on standards should
contact Roger Fujii.
Best Practices Clearinghouse [Jarzombek]
Joe introduced Kathleen Dangle, of the Fraunhofer Institute of the University of
Maryland, whom he had invited to come describe the Fraunhofer’s efforts in support of
best practices. Kathleen described their new portal, the DoD Best Practices Clearing
House. This portal provides a way for practitioners to access best practice solutions
tailored to their customized user profiles.
Joe described this as a DoD initiated project but one that is not hardcoded to model DoD
practices exclusively. He feels strongly that the IEEE CS, and particularly Software and
Systems Engineering Standards, should become engaged and have a role to play in
support of this effort.
DISA STIGs
J. Jarzombek presented the suggestion that IEEE look at adopting the DISA Security
Technical Implementation Guides (STIGs). R. Fujii suggested that IEEE could provide
added value by developing a roadmap to the STIGs and publishing the complete set as an
IEEE collection. Joe will bring this idea forward to DISA. Joe will form the assurance
related knowledge products study group to further pursue this matter. Please refer to
attached paper.
IEEE Computer Society Software Engineering Portfolio Oversight Committee (SEPOC)
[Croll/Moore]
P. Croll presented a summary of the newly formed SEPOC committee. The presentation
is attached. A list of the products/serviced bricks is provided as well.
IEEE Systems Council [Croll]
The purpose of the council is to integrate IEEE activities regarding aspects of multiple
disciplines and specialty areas associated with the engineering of systems. This council
covers, but is not limited to, the following areas:
Systems engineering, education, standards, processes and methodologies
Modeling, simulation and integration related to design, testing, production and
support.
Design aspects for robust design, human factors, safety, security and usability
Transition of products from design to production, deployment and use
Quality control and system management
Program/product/project management interactions
Risk management
Systems Architecture
S2ESC Policies and Procedures – In Depth Review [Croll/Duncan]
Procedure 24 was approved unanimously by the ExCom.
Next S2ESC ExCom Meeting Venue [Croll]
Paul suggested that we return to Ft. Lauderdale for our August meeting. Mary Beth
offered to host the August meeting at the SEI facilities in either Pittsburgh, PA, or
Arlington, VA. Paul invited ExCom members to consider these three possible venues
and email their preferences.
Additional items:
The 2004 edition of the SWEBOK is available at www.Swebok.org.
Adjourn
Next teleconference:
Wednesday, 13 April 2005, 12:30 PM EDT (Note date change)