1 / 14

IEEE Computer Society Category A Liaison to ISO/IEC JTC 1/SC 7: Status Report

IEEE Computer Society Category A Liaison to ISO/IEC JTC 1/SC 7: Status Report. Jim Moore IEEE CS Liaison Representative Prepared for JTC 1/SC 7 May2011. Background. IEEE Computer Society is a member of the US Technical Advisory group to ISO/IEC JTC 1/SC 7.

kaden
Download Presentation

IEEE Computer Society Category A Liaison to ISO/IEC JTC 1/SC 7: Status Report

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. IEEE Computer SocietyCategory A Liaison to ISO/IEC JTC 1/SC 7:Status Report Jim MooreIEEE CS Liaison Representative Prepared for JTC 1/SC 7 May2011

  2. Background • IEEE Computer Society is a member of the US Technical Advisory group to ISO/IEC JTC 1/SC 7. • IEEE Computer Society also has a Category A Liaison relationship with SC 7. • We don’t get to vote. • But we do get to participate, offer comments, and contribute documents (via a standing agreement with the US National Body). • We provide SC 7 access to Computer Society expertise around the world. • We represent Computer Society interests in standards, BOK, certifications, curricula and professional activities. • In IEEE, we report to Computer Society Standards Activities Board (SAB) and coordinate with Software and Systems Engineering Standards Committee (S2ESC) and IEEE Standards Association (IEEE-SA). • In SC 7, we report to the Chair, the Secretariat, and the so-called “advisory group”.

  3. Why Does the Computer Society 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 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 “joint development” of a new standard or a revision.

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

  5. Inconsistencies circa 1995

  6. Inconsistencies Today

  7. Liaison representatives • Jim Moore, lead, James.W.Moore@ieee.org • Pieter Botman, focusing on product standards, P.Botman@ieee.org • Terry Doran, focusing on process standards, Terry.Doran@computer.org • Many others support specific projects (see remaining charts)

  8. Current projects - 1

  9. Current projects - 2

  10. Current projects - 3

  11. Other recent events • IEEE 829, SW Test Documentation, was contributed again. (It had been revised since previous contribution.) • IEEE 1028, Reviews and Audits, was contributed again. (It had been revised since previous contribution.) • IEEE 1074, Developing the SW Life Cycle, has been contributed to a study group. • IEEE 1320, IDEF, may be offered for fast-track if WG19 processes an SC 7 resolution for invitation.

  12. Related Action inside IEEE • IEEE 1062, Software Acquisition, is being coordinated with SC 27 work on supply chain management. • IEEE 1517, SW Reuse Processes, was updated to align with ISO/IEC/IEEE 12207. • Project 1648, Agile SW Development project, was closed as stale.

  13. Concerns • Misalignment of draft 29119, SW Testing, with life cycle processes • FCD 26515 disparages “traditional software engineering” – presumably meaning SWEBOK Guide, existing standards, etc

  14. Proposed Resolutions • Appoint Jon Hagar to replace Ursula Parker as editor of 29119 project. • Continue Alastair Walker as SC 7 Rapporteur to IEEE project 828.

More Related