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 May 2016

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 40 joint standards today, including SC7, SC22, SC27, SC38, with 18 standards in development or revision May 20162

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. May 20163

Why Does the Computer Society Do This? Throughout the Computer Society, we are undertaking efforts to make the Society the “go to” place for 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. May

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 (via a standing agreement with the US National Body). –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. The SC7 US TAG is administered by IEEE-SA May 20165

SC7 US TAG administration by IEEE The IEEE has administered the SC 7 US TAG for over 25 years. SC7 US TAG elected chairs represent the US through ANSI, not IEEE, in international meetings. Some concerns have been raised that IEEE administration of US TAGs gives the perception that IEEE-SA is a US rather than an international SDO. IEEE-SA is considering transferring responsibilities for US TAG administration, either outside IEEE or to another part of IEEE. The only other ANSI accredited organization in the SC7 domain which could administer a US TAG is INCITS. INCITS dues structure and cumbersome procedures would severely reduce SC7 US TAG participation to the detriment of all systems/software engineering standardization and especially US involvement. May 20166

Portfolio status 100% portfolio review March 2016 As of May 2016, there are 57 IEEE S2ESC standards –20 IEEE-unique –16 IEEE-adopted from ISO/IEC –21 Joint ISO/IEC/IEEE –5 superseded standards withdrawn Projects for 16 standards are underway –6 of these are joint projects with SC7 Note: Some projects are both completed and underway, i.e. initial completion followed by revision May 20167

Candidate IEEE standards for SC7 adoption/revision IEEE Standard for Application of Systems Engineering on Defense Programs IEEE Standard for Technical Reviews and Audits on Defense Programs IEEE 1012 Standard for System and Software Verification and Validation IEEE 1062Recommended Practice for Software Acquisition Resolutions approved for IEEE to provide official copy for SC7 study May 20168

Published Standards Recommended Practice for SW Acquisition (revision) System life-cycle processes (revision) Systems engineering on defense programs Tech reviews and audits on defense programs Content of information items (revision) Website management and engineering Content management Application of 9001:2000 to software Software test techniques Management of systems engineering May 20169

Joint development/revisions in progress DIS Systems and software engineering—Software life cycle processes FDIS – Life Cycle Management – Part 5: Software Development Planning DIS Software and systems engineering -- Software testing -- Part 5: Keyword-driven testing FDIS Systems and Software Engineering - Measurement Process DIS Systems and Software Engineering -- Requirements for Testers and Reviewers of User Documentation ISO/IEC/IEEE Systems and Software Engineering--Life Cycle Processes--Project Management May

Anticipated 2016 projects Joint Revisions with SC7 (pending IEEE project approval) 10 –15289 Contents of life-cycle information items – Guide to life-cycle management – Guide to 15288:2015 – Guide to system integration –24765 Systems/software engineering vocabulary –26511 Management of user information –26512 Acquisition and supply of user documentation –26515 User documentation in an agile environment –29148 Requirements Engineering –42020 Architecture processes Revise in future years: 12 more New projects (pending IEEE project approval) –Model-based ethics process –DevOps processes May

Liaison representatives/editors Annette Reilly, lead, Edward Addy, verification standards Pieter Botman, BOK standards, Terry Doran, life cycle process standards, Joann Hackos, content management and information management standards, Jon Hagar, software testing standards Mark Henley, engineering project management Rich Hilliard, architecture Paul Joannou, integrity levels, Claude Laporte, VSE series, Garry Roedler, defense-related SE Laney Strange, software management process guides Suzanne Van Hove, SC40 Liaison, service management processes, VSE, Jim Moore, founding lead, May

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 the international go- to place for codified knowledge of systems and software engineering. May

Back-up May

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. May

Current and completed projects - 1 WGProject IEEE POC Notes , LC dataAnnette ReillyJointly published x, User documentationAnnette ReillyJointly published 26511, and IEEE adopted and , Internet practicesAnnette ReillyISO/IEC revision/ of IEEE 2001/ISO-IEC , Content management Annette ReillyPublished , 14471, CASE toolsIEEE adopted ISO/IEC and SQUARE seriesIEEE project to adopt has been initiated. There have been delays , FSM conceptsIEEE has withdrawn its obsolete edition, leaving the ISO/IEC standard as the single standard , SW product qualityIEEE has withdrawn its obsolete edition (which was an adoption of ISO/IEC 12119). May

Current projects - 2 WGProject IEEE POC Notes and 12207, LC Processes Garry Roedler, Terry Doran, Annette Reilly, Bill Bearden Published jointly : recirculation ballot , Measurement; 16085, Risk management; 16326, Project management; Requirements management Cheryl Jones, Bob Charette, Mark Henley Published jointly , MaintenanceTom PigoskiPublished jointly. IEEE may initiate joint revision x, Systems and software assurance Jim Moore, Paul Joannou IEEE adopted , -3, -4. 7IEEE 828, Configuration management Bob AielloIEEE revision has been provided to WG 7 for study ,2,3, LC management guides , -2, -3 adopted as IEEE Guides. Revision is underway , Systems engineering process Terry Doran, editor Supersedes IEEE Published , SW Planning process E. Strange, editor In ballot , Process descriptionIEEE adopted IEEE 1012, V&VAnatol Kark, SG chair IEEE revision completed May

Current and completed projects - 3 WGProject IEEE POC Notes ,-2, IDEFISO/IEC fast-track of IEEE and was successful , SWEBOK Guide V3Pieter BotmanPrevious version adopted by ISO/IEC. SWEBOK V3 published; pending publication(as US NB contribution) by ISO/IEC , Certification of SW professional; 29154; Guide to Pieter Botman, editor IEEE CS established a revised certification scheme , VocabularyAnnette Reilly, convener Published jointly. IEEE CS hosts web site for free public access: , SW quality management Jim Moore, editor IEEE. adopted it x, LC profiles for VSES.D. Van HoveIEEE will consider publishing derivative documents to suit end-user needs , TestingJon Hagar, editor IEEE contributed base documents. Parts 1-4 have been jointly published. Part 5 is in ballot , Architecture description Rich Hilliard, editor Original was fast-track of IEEE Revision was published jointly. May

SWEBOK v3 published 2014 by IEEE Computer Society 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 Available at Published as ISO/IEC TR 19759:2015, Corrected version May

May TopicStatusRemarks Terminology & ConceptsGreenIEEE CS SWEBOK = ISO/IEC Identical vocabulary, 24765, hosted by IEEE CS. Quality managementGreenIdentical standard, Revision is underway. TestingGreenFirst four standards of joint s29119 series are published. One remains. Architecture descriptionGreenIdentical standard: Product qualityGreenIEEE withdrew its conflicting standard and may adopt Life cycle processesGreen12207, under revision. IEEE is adopting associated guides: Systems engineering processGreenISO/IEC = IEEE Joint revision is underway. SW maintenanceGreenIdentical standard: MeasurementGreenIdentical standard: Risk managementGreenIdentical standard, 16085, but revision is needed. Project managementGreenIdentical standard: Verification and validationYellow  IEEE 1012 is broadened to systems. Configuration managementYellow  and revisions somewhat align with revised 828. SW process assessmentHarmlessNo related IEEE standards Requirements engineeringGreenIdentical standard, replaced IEEE 830, 1233, SW life cycle dataGreenIdentical standard, User documentationGreenIdentical standards, through CASE toolsGreenIdentical standards, 14102, NotationsGreenDistinct standards for distinct notations. SC 7 recently adopted IDEF standards. InternetGreenJoint project underway to revise ISO/IEC aka IEEE 2001 Specialty Engineering (Safety, Security)GreenIEEE has adopted ISO/IEC (4 parts). Revision of parts 1 and 3 is underway. Professional certificationGreenIEEE CSDA and CSDP were the first to conform to ISO/IEC Consistencies in the two collections today

May Inconsistencies in the two collections, circa 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 Professional certificationHarmlessNone