SAB Report Board of Governors February 2004

1. SAB ReportBoard of GovernorsFebruary 2004 James W. Moore Vice-President of Standards Activities IEEE Computer Society

2. SAB Officers and Chairs • Officers • Chair, Jim Moore • Vice-Chair, Robby Robson • Secretary, John Walz • Committee Chairs • Awards, John Walz • International Activities, Jim Moore • Procedures, Robby Robson • Vitality, Kathy Land

3. Sponsor Representatives New • DASC: Peter Ashenden • IASC: Jack Cole, chair • LMSC (802): Paul Nikolich, chair • LTSC: Robby Robson, chair • MMSC: Bob Davis, chair • PASC: Lowell Johnson, chair • SESC: Paul Croll, chair • SISO SAC: Chris Rouget, chair; alternate - Kathleen Morse (?) • SSSC: Curtis Anderson, chair • TTSC: Rohit Kapur, chair; alternate - Greg Maston (?) • SAB-sponsored projects: Paul Eastman Sponsor representatives are voting members. New New

4. Members-at-Large • Denis Baggi • François Coallier • Paul Eastman • Jim Isaak • Kathy Land • Gary Robinson • John Sheppard • John Walz • Don Wright Members-at-large are voting members.

5. Liaisons

6. Staff • Computer Society: John Daniel • IEEE-SA Staff Representative: Susan Tatiner, Noelle Humenick

7. Officers Committee Chairs Plus Lowell Johnson Don Wright Jack Cole Anyone is invited to attend. Adcom will meet on day preceding SAB. Adcom will handle routine business and make recommendations to full SAB. SAB time will be spent on strategic business. This is an experiment. We are inventing as we go. Administrative Committee

8. Three Challenges for SAB • Challenge: Declining relevance of de jure standardization in IT profession, contrasted with an increasing need for professional norms. • Challenge: Simplify standardization for small producers. • Challenge: Broadening internationalimpact of CS IT standardization efforts.

9. “International Impact” Goal • Goal: Broaden international impact of CS IT standardization efforts. • Strategy: Exploit current international liaison for SWE standardization and extend it to other IT areas. • 2003 Accomplishments: • ISO/IEC JTC1/SC7 approval of IEEE-CS “Vision of Outcomes” and Coordination Procedure • One standard fast-tracked – others on the way – a dozen harmonization efforts underway • SC7 adopts SWEBOK Guide as an ISO/IEC Technical Report • SC7 liaison named to SAB • JTC1 Technology Watch formed – CS invited to participate • JTC1 invited IEEE to apply for Category A liaison to JTC1

10. Implementation:Positioning • Survey current international relationships of CS standards sponsors. • Support effort to create IEEE Category A Liaison to JTC1. • Capitalize on new relationship: • “Regularize” the current mixture of relationships. • Use the opportunity to “fast-track” IEEE standards to JTC1.

11. Implementation:Application of Expert Resources • Participate in the “Technology Watch” JTC1 Special Working Group. • “Reach back” to TAB and other resources to provide expert advice. • Example: TAB is staffing the JTC1 Study Group on Web Services. Representative will report to both SAB and TAB. • When appropriate: • Fast-track IEEE standards • Adopt specifications from others • Supply talent to develop new standards

12. Implementation:Provide a Single “Voice” for CS • Develop a CS policy and procedure for reaching a consensus technical position in CS on items in addition to standards. • Apply procedure to IFIP participation: • Allot IFIP TCs to SAB, TAB, wherever is appropriate. • Use consensus procedure to permit representatives to provide a Society point of view. • Apply to other technical projects where consensus is the appropriate decision-making process.

13. Implementation: International View of Software Engineering • Forward new SWEBOK as an ISO/IEC Technical Report. • Supported by SESC collection, IEEE-SA CD-ROM, SESC Book Series. • Forward CSDP Task Analysis as an ISO/IEC Standard. • Gives worldwide credibility to CSDP. • Continue harmonization of SESC and JTC1/SC7 collections. • Extend into “[software] systems engineering” and “[software] quality management.”

14. Digression: Current Status of Harmonization of SWE Standards • SESC has about 40 standards. ISO/IEC JTC1/SC7 has about 50 standards—more if you count the “parts” individually. • SESC and SC7 have agreed on a coordination procedure and a “Vision of Outcomes.” • CS representatives are participating in a dozen different WGs, SGs, Teams, etc. • SESC is “leading” SC7 in four current projects. • SESC is “following” SC7 in six current projects. • SESC and SC7 are “merging” standards in two projects. • One important project is delayed pending CS staffing.

15. Implementation:International Leadership • Develop a flagship conference for Practical Software Engineering. • In addition to papers and presentations … • It would host workshops for Fundamental Principles, SWEBOK, standards working groups, and other related efforts. • Key part of the CS “Software Engineering Branding” initiative

16. Some Details re TAB and SAB • Working on matrix of SAB-TAB relationships. • Planning a joint TAB-SAB meeting this year. • TAB and SAB are exchanging liaison representatives. • SAB is reaching back to TAB to staff JTC1 technology study groups. • SAB is encouraging standards sponsors to develop relationships to corresponding organs within SAB. Each sponsor will brief SAB during the year on this topic.