IEEE CS SAB, Nov 2007 IEEE-CS/SC7 Liaison Report 1 IEEE Computer Society Category A Liaison to JTC 1/SC 7: Status Report Jim Moore IEEE CS Liaison Representative Prepared for IEEE CS SAB Nov 2007

IEEE CS SAB, Nov 2007 IEEE-CS/SC7 Liaison Report 2 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.

IEEE CS SAB, Nov 2007 IEEE-CS/SC7 Liaison Report 3 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.

IEEE CS SAB, Nov 2007 IEEE-CS/SC7 Liaison Report 4 The State of Harmonization in 1995 TopicStatusRemarks Terminology & ConceptsRedDifferent vocabulary standards Quality managementOrangeISO: Driven down from ISO IEEE: traditional QA approach. TestingOrangeIEEE standards unrelated to SC7 processes. Architecture descriptionHarmlessSC7 didn’t have architecture standards. Product qualityYellowUnrelated standards Life cycle processesRedIncompatible standards Systems engineering processYellowUnrelated standards SW maintenanceRedIncompatible standards MeasurementYellowUnrelated standards Risk managementHarmlessNo standards at all Project managementRedIncompatible standards Verification and validationRedFundamentally different approaches; minor incompatibilities in details Configuration managementRedIncompatible standards SW process assessmentYellowNothing in IEEE. ISO process assessment incompatible with ISO LC. Requirements engineeringOrangeIEEE standards unrelated to SC7 processes SW life cycle dataRedIncompatible standards User documentationRedIncompatible standards CASE toolsYellowMinor incompatibilities NotationsHarmlessDistinct standards for distinct notations InternetHarmlessNo standards IT Services, Management, GovernanceHarmlessNo standards Specialty Engineering (Safety, Security)OrangeUnrelated approaches OthersYellowMany unrelated standards

IEEE CS SAB, Nov 2007 IEEE-CS/SC7 Liaison Report 5 The State of Harmonization … Today TopicStatusRemarks Terminology & ConceptsYellow  Shared BOK, joint vocabulary project, potential certification framework Quality managementYellowIEEE is adopting ISO/IEC approach. TestingOrange  Both IEEE and BSI may harmonize with SC7 processes Architecture descriptionGreenSC7 adopted IEEE standard and will harmonize with processes. Product qualityYellowISO/IEC was revised as IEEE may adopt. Life cycle processesGreenBut some loose ends remain Systems engineeringGreenShared SE process standard; harmonization with other LC processes underway SW maintenanceGreenProject to merge IEEE and ISO standards is completed MeasurementYellow  IEEE will adopt after its current revision. Some details remain. Risk managementGreenSC7 adopted IEEE standard and is now extending it to the systems level. Project managementYellow  New project to merge the incompatible standards Verification and validationRedFundamentally different approaches. Good intentions, but no action. Configuration managementYellowSC7 withdrew its process standard; systems issues remain SW process assessmentYellow  Harmonization with LC process standards is underway Requirements engineeringOrange  Joint project has been approved SW life cycle dataYellow  IEEE is adopting to replace User documentationYellow  IEEE 1063 has been incorporated into CASE toolsYellowMinor incompatibilities NotationsHarmlessDistinct standards for distinct notations InternetGreenShared standard IT Services, Management, GovernanceYellowIEEE may adopt standards Specialty Engineering (Safety, Security)OrangeUnrelated approaches OthersYellowMany unrelated standards

IEEE CS SAB, Nov 2007 IEEE-CS/SC7 Liaison Report 6 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 revision is planned] – (was ISO/IEC 12207), SW LC Processes [coordinated revision underway] – (was ISO/IEC ), Functional Size Measurement [SC 7 has prepared a Corrigendum] –15288, System Life Cycle Processes [coordinated revision underway]

IEEE CS SAB, Nov 2007 IEEE-CS/SC7 Liaison Report 7 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

IEEE CS SAB, Nov 2007 IEEE-CS/SC7 Liaison Report 8 New Projects underway in IEEE Adopt ISO/IEC to replace IEEE Adopt ISO/IEC and 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

IEEE CS SAB, Nov 2007 IEEE-CS/SC7 Liaison Report 9 A Notable Project: Shared vocabulary for software and systems engineering. IEEE contributed IEEE Std 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. – 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 CD is currently being balloted in SC7 and will soon enter balloting in IEEE.

IEEE CS SAB, Nov 2007 IEEE-CS/SC7 Liaison Report 10 A New Cooperative Project: Testing BSI will contribute their two standards on testing. IEEE has contributed 829 and 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.

IEEE CS SAB, Nov 2007 IEEE-CS/SC7 Liaison Report 11 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.

IEEE CS SAB, Nov 2007 IEEE-CS/SC7 Liaison Report 12 “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.

IEEE CS SAB, Nov 2007 IEEE-CS/SC7 Liaison Report 13 Coordinated Development is used by S2ESC and JTC 1/SC 7 WGSC 7JTC 1ISO CSS2ESC SA StaffSA SB IEEE StdBase Doc Approve NPPAR Draft Form BG CDBallot Recirc FCDRecirc FDIS Recirc 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.

IEEE CS SAB, Nov 2007 IEEE-CS/SC7 Liaison Report 14 The Fundamental Problem The “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

IEEE CS SAB, Nov 2007 IEEE-CS/SC7 Liaison Report 15 Some Fundamental Process Differences IEEE ProcessISO Process Consensus of expert opinionsConsensus 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 mailComments “dispositioned” in person All comments must be entertained.Limited scope revisions are permitted. Administratively enforced rulesEverything subject to NB voting Administrative process review completes the project. Additional NB vote by parent body completes the process.

IEEE CS SAB, Nov 2007 IEEE-CS/SC7 Liaison Report 16 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.

IEEE CS SAB, Nov 2007 IEEE-CS/SC7 Liaison Report 17 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.