180 likes | 339 Views
IEEE Computer Society Category A Liaison to ISO/IEC JTC 1/SC 7: Status Report. Jim Moore IEEE Computer Society Liaison Representative to ISO/IEC JTC 1/SC 7 Prepared for IEEE CS SAB February 2013. Background. IEEE Computer Society is a Category A Liaison to SC 7.
E N D
IEEE Computer SocietyCategory A Liaison to ISO/IEC JTC 1/SC 7:Status Report Jim MooreIEEE Computer Society Liaison Representative to ISO/IEC JTC 1/SC 7 Prepared for IEEE CS SAB February 2013
Background • 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. • In accordance with the Bylaws of the IEEE, the liaison operates in accordance with the provisions of the “PSDO.” • 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 Chair, the Secretariat, and the meetings of the HODs. • The liaison also represents the Computer Society’s membership in the US Technical Advisory Group to SC 7.
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. • One of its strengths is the standards collection of the IEEE Software and Systems Engineering Standards Committee (S2ESC). • One of its weaknesses is inconsistency between these standards and international standards (from ISO/IEC JTC 1/SC 7) on the same subject. Differences reduce the credibility of both standards on a given subject. • IEEE and SC 7 have undertaken a program to make the two collections completely consistent using the PSDO. • We use 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.
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.
Liaison representatives • Jim Moore, lead, James.W.Moore@ieee.org • Pieter Botman, focusing on certification standards, P.Botman@ieee.org • Terry Doran, focusing on process standards, Terry.Doran@computer.org • Paul Joannou, focusing on safety standards, pauljoannou@rogers.com • Typically, the Computer Society provides the editor for joint standards projects (see remaining charts)
Relevant Results of SC 7 Interim Meeting: Document Progress • 15026-1, Sys and SW Assurance Concepts and Vocabulary: Send to DIS ballot. • 15026-3, Integrity Levels: Editor to prepare working draft. • 15288, Sys Processes: Send to NWIP and CD ballot. • 24748-4, Management of Systems Engineering: Send to CD2 ballot. • 24748-5, SW Development Planning: Send to CD1 ballot.
Relevant Results of SC 7 Interim: Study Group • Study Group on IEEE 1012: • Describe differences in vocabulary and concepts. • List changes needed for adoption by SC 7. • Work with WG1012 to negotiate agreement on changes. • Study Group on Applying ISO/IEC/IEEE 12207 to Service Architectures: • Prepare NWIP for ballot
Relevant Results of SC 7 Interim: Other • Drafting of joint revision to IEEE Std 2001(ISO/IEC 23026) has begun. Annette Reilly is the lead editor. • Decision whether to fast-track IEEE 828 was deferred--“editors of 15288 should, in preparing CD 1, ensure harmonization with IEEE 828 to the greatest degree possible.” • Testing: The interim meeting of the relevant WG has not yet occurred. • Certification: Botman will report to PAB. • BKCASE: The status was presented. • NATO is interested in adoption of 12207.
Relevant Results of SC 7 Interim: Recognition • Dr. Karen Richter, for serving as an editor of 15026-4.
Summary of Effectiveness 1 • (These numbers are current as of Sep 2012.) • There are 51 S2ESC standards (now or imminent) • 33 identical with SC7 (completed or imminent) • 5 more potentially identical • 13 others • 2 outside SC7 scope • 7 SC7 does not work in the area • 3 IEEE provides a legitimate alternative • 1 (1074) likely to remain inconsistent • Projects affecting 11 standards are underway • (Note: Some projects are both completed and underway, i.e. initial completion followed by revision)
Summary of Effectiveness 2 • As a result of harmonization with SC 7, since 2005, old IEEE standards have been updated with modern revisions: • 1 IEEE standard(s) last revised in 2003 • 1 IEEE standard(s) last revised in 2000 • 6 IEEE standard(s) last revised in 1998 • 3 IEEE standard(s) last revised in 1996 • 1 IEEE standard(s) last revised in 1995 • 2 IEEE standard(s) last revised in 1992 • 1 IEEE standard(s) last revised in 1990 • 1 IEEE standard(s) last revised in 1987
Summary of Effectiveness 3 • We have 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 • Certification programs • Training programs • … making IEEE CS the international go-to place for codified knowledge of software engineering.