ieee cs sab, nov 2007 ieee-cs/sc7 liaison report 1 ieee computer society category a liaison to jtc...

IEEE CS SAB, Nov 2007

IEEE-CS/SC7 Liaison Report 1

IEEE Computer Society Category IEEE Computer Society Category A Liaison to JTC 1/SC 7:A Liaison to JTC 1/SC 7:

Status ReportStatus Report

Jim MooreIEEE CS Liaison Representative

Prepared for IEEE CS SABNov 2007



Why Do We Do This?• Throughout the Computer Society, we are undertaking efforts to

make the Society to “go to” place for software engineering.• One of our strengths is the standards collection of the Software and

Systems Engineering Standards Committee (S2ESC).• One of our weaknesses is the extent of inconsistency between

these standards and international standards (from ISO/IEC JTC 1/SC 7) on the same subject. This handicaps the global appeal of our standards.

• We have undertaken a program to make the two collections completely consistent.

• We use several methods:– Sometimes SC 7 adopts an IEEE standard.– Sometimes IEEE adopts an SC 7 standard.– Sometimes we merge our respective standards.– Sometimes we perform “coordinated development” of a new standard or

a revision.• We are both a member of the US TAG to SC 7 and a Category A

liaison to SC 7.



Why International Standardization?• IEEE-SA encourages cooperation with international

standardization:– Enables a healthy blend of technical, national, regional,

and international standards – Example of strong effort by IEC to follow new positions of

the WTO/TBT activity: openness, transparency, due process, coherence, market relevance, etc.

– Sends a strong and clear message to industry that the major technical standards developing organizations aim to cooperate toward one standard in the world wherever possible

– From a market and trade perspective, symbolizes a loosening of real and perceived barriers.

– Informs those countries and regions who are not strong players in the world marketplace that their route to international standardization has more paths than were previously available.

This slide is adapted from a

June 2004 presentation by

Terry deCourcelle and Jodi Haasz.



The State of Harmonization in 1995Topic Status Remarks

Terminology & Concepts Red Different vocabulary standards

Quality management Orange ISO: Driven down from ISO 9001. IEEE: traditional QA approach.

Testing Orange IEEE standards unrelated to SC7 processes.

Architecture description Harmless SC7 didn’t have architecture standards.

Product quality Yellow Unrelated standards

Life cycle processes Red Incompatible standards

Systems engineering process Yellow Unrelated standards

SW maintenance Red Incompatible standards

Measurement Yellow Unrelated standards

Risk management Harmless No standards at all

Project management Red Incompatible standards

Verification and validation Red Fundamentally different approaches; minor incompatibilities in details

Configuration management Red Incompatible standards

SW process assessment Yellow Nothing in IEEE. ISO process assessment incompatible with ISO LC.

Requirements engineering Orange IEEE standards unrelated to SC7 processes

SW life cycle data Red Incompatible standards

User documentation Red Incompatible standards

CASE tools Yellow Minor incompatibilities

Notations Harmless Distinct standards for distinct notations

Internet Harmless No standards

IT Services, Management, Governance Harmless No standards

Specialty Engineering (Safety, Security) Orange Unrelated approaches

Others Yellow Many unrelated standards



The State of Harmonization … TodayTopic Status Remarks

Terminology & Concepts Yellow Shared BOK, joint vocabulary project, potential certification framework

Quality management Yellow IEEE is adopting ISO/IEC 90003 approach.

Testing Orange Both IEEE and BSI may harmonize with SC7 processes

Architecture description Green SC7 adopted IEEE standard and will harmonize with processes.

Product quality Yellow ISO/IEC 12119 was revised as 25051. IEEE may adopt.

Life cycle processes Green But some loose ends remain

Systems engineering Green Shared SE process standard; harmonization with other LC processes underway

SW maintenance Green Project to merge IEEE and ISO standards is completed

Measurement Yellow IEEE will adopt 15939 after its current revision. Some details remain.

Risk management Green SC7 adopted IEEE standard and is now extending it to the systems level.

Project management Yellow New project to merge the incompatible standards

Verification and validation Red Fundamentally different approaches. Good intentions, but no action.

Configuration management Yellow SC7 withdrew its process standard; systems issues remain

SW process assessment Yellow Harmonization with LC process standards is underway

Requirements engineering Orange Joint project has been approved

SW life cycle data Yellow IEEE is adopting 15289 to replace 12207.1

User documentation Yellow IEEE 1063 has been incorporated into 26514

CASE tools Yellow Minor incompatibilities

Notations Harmless Distinct standards for distinct notations

Internet Green Shared standard

IT Services, Management, Governance Yellow IEEE may adopt 20000 standards

Specialty Engineering (Safety, Security) Orange Unrelated approaches

Others Yellow Many unrelated standards



Successes (1 of 2)• Since 1996, IEEE has adopted several SC7

standards– 1462 (was ISO/IEC 14102), CASE Tool Evaluation

and Selection• [SC 7 is revising]

– 1465 (was ISO/IEC 12119), SW Package Quality • [adoption of 25051 revision is planned]

– 12207.0 (was ISO/IEC 12207), SW LC Processes • [coordinated revision underway]

– 14143.1 (was ISO/IEC 14143-1), Functional Size Measurement

• [SC 7 has prepared a Corrigendum]– 15288, System Life Cycle Processes

• [coordinated revision underway]



Successes (2 of 2)• SC7 has adopted IEEE standards

– 16085 (was IEEE 1540), Risk Management Process – 19759, SWEBOK Guide– 23026 (was IEEE 2001), Web Site Practices– 25961 (was IEEE 1471), Architecture Description

• [Awaiting publication; coordinated revision underway]– 26702 (was IEEE 1220), Systems Engineering Process

• [Awaiting publication; coordinated revision anticipated]

• We have jointly revised one shared standard– 16085, Risk Management Process

• [Both ISO and IEEE have published.]

• Some standards have been merged– 14764 (with IEEE 1219), SW Maintenance

• [Both ISO and IEEE have published.]

• Other projects are underway

2006

2006

2006

20062006



New Projects underway in IEEE• Adopt ISO/IEC 15289 to replace IEEE 12207.1.• Adopt ISO/IEC 20000-1 and 20000-2 to provide

a shared basis for work on IT Services and Management.

• Possible adoption of: ISO/IEC 25051, COTS Product Quality.– Balloting group decided that standard should not be

adopted and predecessor standard should be withdrawn

– Comments will be sent to SC 7/WG 6 for their consideration in revising the standard

NEW



A Notable Project: 24765• Shared vocabulary for software and systems

engineering.• IEEE contributed IEEE Std 610.12. SC 7 contributed its

vocabulary aggregations. Other sources, e.g. PMI, made contributions.

• IEEE CS has developed and is hosting a database application providing public web access.– http://www.computer.org/sevocab

• SC 7/WG 22 will maintain the database and will facilitate the consolidation of alternative definitions.

• Occasional snapshots of the database will be published as ISO/IEC and IEEE 24765.

• CD 24765 is currently being balloted in SC7 and will soon enter balloting in IEEE.



A New Cooperative Project: Testing• BSI will contribute their two standards on testing.• IEEE has contributed 829 and 1008.• A new four-part standard will be created at the

international level.– Compatible with international (and IEEE) systems and

software processes– Compatible with international (and IEEE)

documentation standards– Compatible with IEEE CS SWEBOK Guide– Covering a larger scope than the current standards

• IEEE-CS has provided Ursula Parker as the editor

• The NP ballot was approved in May 2007.



New Project: Revision of 15026, Systems Assurance

• IEEE has provided editors: Mark Henley and Sam Redwine.

• New Work Item Proposal was approved.• First draft drew good consensus in SC7

CD ballot and approval in IEEE ballot.• Another CD ballot will be performed.• The editor’s have proposed breaking it into

a four-part standard. This question will be balloted in SC7.



“Coordinated Development” is used by S2ESC and JTC 1/SC 7

• Typically SC 7 supplies WG convener, IEEE CS supplies project editor.

• The idea is to conduct corresponding steps concurrently.

• All comments are resolved by the ISO working group.

• Both organizations reach consensus via their own processes according to their own rules.

• Both organizations publish roughly simultaneously.



Coordinated Development is used by S2ESC and JTC 1/SC 7

WG SC 7 JTC 1 ISO CS S2ESC SA Staff SA SB

IEEE StdBase Doc

Approve NP PAR

Draft Form BG

CD Ballot

Recirc

FCD Recirc

FDISRecirc

Approve

IEEE StdISO/IEC

Contribute standards

Prepare MS

CD

Publish identical standards

Possibly multiple

Note that there is generally no use for an

IEEE working group.

Note that there are too many recirculations.



The Fundamental ProblemThe “normal” ISO development path.

The flexibility they have available according to their rules.

The “normal” IEEE development path.

The flexibility they have available

according to their rules.

The space I have left to

work in.

Oh yeah, automation is making the processes less flexible



Some Fundamental Process DifferencesIEEE Process ISO ProcessConsensus of expert opinions Consensus of staffed “national body”

positions

Consensus formation is ballot-oriented. Consensus formation is meeting-oriented.

Scope and purpose are established at the beginning.

Scope and purpose are subject to change in balloting.

(Typically) One ballot plus recirculations ... Repeated ballots ...

...of a fixed group of balloters ...of an expanding group of balloters

Comment only on “changed portions” Comment on anything

Comments “rebutted” by mail Comments “dispositioned” in person

All comments must be entertained. Limited scope revisions are permitted.

Administratively enforced rules Everything subject to NB voting

Administrative process review completes the project.

Additional NB vote by parent body completes the process.



Some Problems are Surfacing• Some participants in SC7 under-value the IEEE

contribution.• Some participants in S2ESC under-value the ISO

contribution.• Some participants in SC7

– Equate the IEEE with the US, or– Believe that IEEE should appropriately be a “part” of the US

• OTOH, some IEEE parties believe that IEEE is appropriately on equal status with ISO.

• Some SC7 participants believe that the IEEE front matter in the joint publication format unequally portrays the IEEE contribution and participation.

• Those who “operate” the coordinated processes believe that they are too cumbersome and labor intensive.



Possible Improvements• A pending agreement on joint publication format may reduce the

problems with the “endgame” and the representation of participation.

• Nevertheless, the coordinated voting process is still cumbersome and leads to the impression that IEEE is “slowing” the process.

• A possible improvement—Change the coordination process as follows:– IEEE technical materials are contributed at the beginning of the project.– SC7 prepares drafts in the normal fashion.– An IEEE “poll” is conducted during the first CD ballot and the comments

are sent to SC7.– SC7 continues its process in the normal manner.– IEEE conducts an adoption project after the ISO/IEC version is

published.– Any comments resulting from adoption are sent to SC7 for consideration

in the next revision.

ieee cs sab, nov 2007 ieee-cs/sc7 liaison report 1 ieee computer society category a liaison to jtc...

Documents