IEEE CS SAB, Mar 2009 IEEE Computer Society Category A Liaison to ISO/IEC JTC 1/SC 7: Status Report Annette Reilly IEEE Computer Society Liaison Representative to ISO/IEC JTC 1/SC 7 June 2017 IEEE-CS/SC7 Liaison Report

Goal of the Liaison to SC 7 The goal is to support the IEEE Computer Society as a joint “owner” with ISO/IEC JTC 1/SC7 of a single, globally relevant characterization of the scope and content of systems and software engineering. IEEE and ISO/IEC JTC1 have over 35 joint standards today, including SC7, SC22, with 17 joint standards in development or revision June 2017

Objectives of the SC7 Society Representative Under the terms of the Partner Standards Development Organization (PSDO) agreement, and in cooperation with IEEE-Standards Association, improve the degree of alignment between IEEE S2ESC standards and SC7 standards. Seek improvement of standards to provide additional rigor for situations of high consequence, and broad applicability for current processes and methods Ensure that the SC7 adoption of the Software Engineering Body of Knowledge (SWEBOK Guide), ISO/IEC TR 19759, remains consistent with the IEEE CS SWEBOK Guide as it evolves. June 2017

Working relationships IEEE Computer Society is a Category A Liaison to SC 7. The Computer Society does not vote. But it does get to participate, offer comments, and contribute documents The liaison relationship provides SC 7 access to Computer Society expertise around the world. The liaison represents Computer Society interests in BOK, certifications, curricula and professional activities. As provided by the Bylaws of the IEEE, the liaison operates in accordance with the provisions of the Partner Standards Development Organization (PSDO) agreement. In IEEE, the liaison reports to Computer Society Standards Activities Board (SAB) and coordinates with Software and Systems Engineering Standards Committee (S2ESC) and IEEE Standards Association (IEEE-SA). In SC 7, the liaison provides reports to the Secretariat. The liaison also represents the Computer Society’s membership in the US Technical Advisory Group to SC 7. IEEE-Standards Association intends to transfer administration of the US TAG to SC7 to INCITS in November 2017. June 2017

Portfolio status As of June 2017, there are 56 IEEE S2ESC standards 17 IEEE-unique 11 IEEE-adopted from ISO/IEC 28 Joint ISO/IEC/IEEE Projects for 31 standards are underway 17 of these are joint projects with SC7 Note: Some projects are both completed and underway, i.e. initial completion followed by revision June 2017

(almost) Published Standards 2017 ISO/IEC/IEEE 15289, 3rd ed. Systems and software engineering -- Content of life-cycle information items (documentation) ISO/IEC/IEEE 15939, Systems and software engineering - Measurement process ISO/IEC/IEEE 26512 Requirements for Acquirers and Suppliers of Information for Users ISO/IEC/IEEEE 24765 Systems and software engineering—Vocabulary ISO/IEC/IEEE 24748-5 Systems and Software Engineering--Life Cycle Management--Part 5: Software Development Planning June 2017

New and Anticipated 2017 projects Joint new projects with SC7 (pending project approval) 24748-3 Guide to 12207:2017 (revision) 42030 Architecture Evaluation (new) New IEEE projects IEEE 2675 DevOps processes P2430, Standard for Software Nonfunctional Sizing Measurement IEEE 7000 Model-based ethics process IEEE 7003 Algorithm Bias Considerations IEEE 7006 Standard for Personal Data Artificial Intelligence (AI) Agent June 2017

Candidate IEEE standards for SC7 adoption/revision IEEE 15288.1 Standard for Application of Systems Engineering on Defense Programs IEEE 15288.2 Standard for Technical Reviews and Audits on Defense Programs IEEE 1012 Standard for System and Software Verification and Validation (possible future) IEEE 1062 Recommended Practice for Software Acquisition June 2017

Joint development/revisions in progress (1) FDIS 12207 Systems and software engineering—Software life cycle processes WD 16085 Standard for Software Engineering - Software Life Cycle Processes - Risk Management WD 16326 Systems and Software Engineering--Life Cycle Processes--Project Management CD 21839, Systems Engineering - Systems of Systems Considerations in Engineering of Systems 24748-1 Life Cycle Management - Part 1: Guidelines for Life Cycle Management 24748-2 Life Cycle Management-- Part 2: Guidelines for the Application of ISO/IEC/IEEE 15288 (System Life Cycle Processes) 29148 Life Cycle Processes --Requirements Engineering June 2017

Joint development/revisions in progress (2) DIS 26511 Requirements for Managers of Information for Users of Systems, Software, and Services FDIS 26513 Systems and Software Engineering -- Requirements for Testers and Reviewers of User Documentation DIS 26515 Developing Information for Users in an Agile Environment 42010 Systems and Software Engineering -- Architecture Description 42020 Systems and Software Engineering -- Architecture Processes June 2017

Liaison representatives/editors Annette Reilly, lead, annette.reilly@computer.org Edward Addy, verification standards edward.addy@ngc.com Pieter Botman, BOK and certification standards, P.Botman@ieee.org Mary Beth Chrissis, risk management, mb@sei.cmu.edu Terry Doran, life cycle process standards, Terry.Doran@computer.org Joann Hackos, content management and information management standards, joann.hackos@comtech-serv.com Jon Hagar, software testing standards jon.d.hagar@gmail.com Mark Henley, engineering project management mark.henley@L-3COM.COM Rich Hilliard, architecture and SWEBOK rich.hilliard@gmail.com Paul Joannou, integrity levels, paul.joannou@rogers.com Claude Laporte, VSE series, Claude.Y.Laporte@etsmtl.ca Garry Roedler, defense-related SE garry.j.roedler@lmco.com Laney Strange, software management process guides laneyd@gmail.com Suzanne Van Hove, service management processes, VSE, sdv@practical-itsm.com Jim Moore, founding lead, James.W.Moore@ieee.org June 2017

SWEBOK Revisions Planning underway to transition the next version of SWEBOK to an incrementally updated, internet-accessible wiki format. The SWEBOK Guide: characterizes the contents of the software engineering discipline promotes a consistent view of software engineering worldwide clarifies software engineering's place with respect to other disciplines provides a foundation for training materials and curriculum development, and provides a basis for certification and licensing of software engineers Published 2014 by IEEE Computer Society http://www.computer.org/portal/web/swebok/swebokv3 Published as ISO/IEC TR 19759:2015, Corrected version 2016-06-01 June 2017

Summary of Effectiveness IEEE CS has created a coherent, consistent collection of standards, recognized world-wide, that supports and is supported by: An agreed body of knowledge An agreed vocabulary database Training programs … making IEEE CS an international source for codified knowledge of systems and software engineering. June 2017

Back-up June 2017

Why Does the Computer Society Do This? IEEE CS SAB, Mar 2009 Why Does the Computer Society Do This? Throughout the Computer Society, we are undertaking efforts to make the Society the “go to” place for systems and software engineering. The role of its Standards Activity Board (SAB) and Systems and Software Engineering Standards Committee (S2ESC) is to deal with the standards collection. One of the strengths of the CS systems and software engineering program is the standards collection of the S2ESC. One of its weaknesses is inconsistency between these standards and other international standards (from ISO/IEC JTC 1/SC 7) on the same subject. Differences reduce the credibility of both standards on a given subject. CS and SC 7 have undertaken a program to make the two collections completely consistent using the PSDO. We use two approaches: Adoption: One organization adopts the standard of the other. Joint projects: Either to merge two standards, develop a new one serving both organizations, or revise an existing one. Where there is no overlap, we encourage revision of our standards in a manner that avoids contradiction with those of the SC 7 collection. June 2017 IEEE-CS/SC7 Liaison Report

IEEE CS SAB, Mar 2009 PSDO Agreement The IEEE Standards Association and ISO Central Secretariat have concluded a PSDO (Partner Standards Development Organization) agreement. The agreement provides uniform procedures for joint development and maintenance of standards by IEEE and designated TCs of ISO and SCs of JTC 1. IEEE also has a dual logo agreement with IEC. June 2017 IEEE-CS/SC7 Liaison Report

How does joint development between IEEE and ISO/IEC JTC 1 SC work? Typically, one working group (SC7 or IEEE) takes the lead in working draft development and comments management The lead working group prepares text in ISO format with very minor modifications for the triple copyright notices, Foreword text Each partner follows its own procedures for Working group formation, Project initiation (ISO NWIP, IEEE PAR) Agreement to go to ballot (ISO CD, IEEE initial ballot) The lead working group resolves comments from both IEEE and ISO ballots Further ballots and revisions until consensus approval is gained for the identical text (ISO DIS/FDIS, IEEE recirculations are scheduled concurrently) ISO ITTF and IEEE Standards Association editors work together to prepare the final published version. June 2017

Current and completed projects - 1 WG Project IEEE POC Notes 2 15289, LC data Annette Reilly Jointly published. 2651x, User documentation Jointly published 26511, 26512 and 26515. IEEE adopted 26513 and 26514. 23026, Internet practices ISO/IEC revision/ of IEEE 2001/ISO-IEC 23026. 26531, Content management   Published 4 14102, 14471, CASE tools IEEE adopted ISO/IEC 14102 and 14471. 6 SQUARE series IEEE project to adopt 25010 has been initiated. There have been delays. 14143-1, FSM concepts IEEE has withdrawn its obsolete edition, leaving the ISO/IEC standard as the single standard. 25051, SW product quality IEEE has withdrawn its obsolete edition (which was an adoption of ISO/IEC 12119). June 2017

Current projects - 2 WG Project Notes IEEE POC 7 15288 and 12207, LC Processes Garry Roedler, Terry Doran, Annette Reilly, Bill Bearden 15288 Published jointly. 12207: pending FDIS. 15939, Measurement; 16085, Risk management; 16326, Project management; 29148 Requirements management Cheryl Jones, Garry Roedler, Mark Henley Published jointly. Revisions in process 14764, Maintenance Tom Pigoski Published jointly. IEEE may initiate joint revision. 15026-x, Systems and software assurance Jim Moore, IEEE adopted 15026-2, -3, -4. Joint revisions underway IEEE 828, Configuration management Bob Aiello IEEE revision was provided to WG 7 for study. 24748-1,2,3, LC management guides 24748-1, -2, -3 adopted as IEEE Guides. Revisions are underway. 24748-4, Systems engineering process Terry Doran, editor Superseded IEEE 1220. 24748-5, SW Planning process E. Strange, editor Pending publication 24774, Process description IEEE adopted 24774. IEEE 1012, V&V Anatol Kark, SG chair IEEE revision continuing June 2017

Current and completed projects - 3 WG Project IEEE POC Notes 19 31320-1,-2, IDEF ISO/IEC fast-track of IEEE 1320.1 and 1320.2 was successful. 20 19759, SWEBOK Guide V3 Pieter Botman Previous version adopted by ISO/IEC. SWEBOK V3 published; pending publication(as US NB contribution) by ISO/IEC. 24773, Certification of SW professional; 29154; Guide to 24773 Pieter Botman, editor IEEE CS established a revised certification scheme. 22 24765, Vocabulary Annette Reilly, convener Published jointly. IEEE CS hosts web site for free public access: www.computer.org/sevocab 23 90003, SW quality management Jim Moore, editor IEEE. adopted it 24 29110-x, LC profiles for VSE S.D. Van Hove IEEE will consider publishing derivative documents to suit end-user needs. 26 29119, Testing Jon Hagar, editor IEEE contributed base documents. Parts 1-5 have been jointly published. 42 42010, Architecture description Rich Hilliard, editor Original was fast-track of IEEE 1471. Revision was published jointly. June 2017

Consistencies in the two collections today IEEE CS SAB, Mar 2009 Consistencies in the two collections today Topic Status Remarks Terminology & Concepts Green IEEE CS SWEBOK = ISO/IEC 19759. Identical vocabulary, 24765, hosted by IEEE CS. Quality management Identical standard, 90003. Revision is underway. Testing First four standards of joint s29119 series are published. One remains. Architecture description Identical standard: 42010 Product quality IEEE withdrew its conflicting standard and may adopt 25010 Life cycle processes 12207, 15288 under revision. IEEE is adopting associated guides: 24748. Systems engineering process ISO/IEC 26702 = IEEE 1220. Joint revision is underway. SW maintenance Identical standard: 14764. Measurement Identical standard: 15939. Risk management Identical standard, 16085, but revision is needed. Project management Identical standard: 16326. Verification and validation Yellow  IEEE 1012 is broadened to systems. Configuration management 12207 and 15288 revisions somewhat align with revised 828. SW process assessment Harmless No related IEEE standards Requirements engineering Identical standard, 29148 replaced IEEE 830, 1233, 1362. SW life cycle data Identical standard, 15289 User documentation Identical standards, 26511 through 26515 CASE tools Identical standards, 14102, 14471 Notations Distinct standards for distinct notations. SC 7 recently adopted IDEF standards. Internet Joint project underway to revise ISO/IEC 23026 aka IEEE 2001 Specialty Engineering (Safety, Security) IEEE has adopted ISO/IEC 15026 (4 parts). Revision of parts 1 and 3 is underway. Professional certification IEEE CSDA and CSDP were the first to conform to ISO/IEC 24773 June 2017 IEEE-CS/SC7 Liaison Report

Inconsistencies in the two collections, circa 1995 IEEE CS SAB, Mar 2009 Inconsistencies in the two collections, circa 1995 Topic Status Remarks Terminology & Concepts Red Different vocabulary standards Quality management Orange ISO: Driven down from ISO 9001. IEEE: traditional QA approach. Testing IEEE standards unrelated to SC7 processes. Architecture description Harmless SC7 didn’t have architecture standards. Product quality Yellow Unrelated standards Life cycle processes Incompatible standards Systems engineering process SW maintenance Measurement Risk management No standards at all Project management Verification and validation Fundamentally different approaches; minor incompatibilities in details Configuration management SW process assessment Nothing in IEEE. ISO process assessment incompatible with ISO LC. Requirements engineering IEEE standards unrelated to SC7 processes SW life cycle data User documentation CASE tools Minor incompatibilities Notations Distinct standards for distinct notations Internet No standards IT Services, Management, Governance Specialty Engineering (Safety, Security) Unrelated approaches Professional certification None June 2017 IEEE-CS/SC7 Liaison Report