1. 2004-02 SAB Report1 SAB Report Board of Governors February 2004 James W. Moore Vice-President of Standards Activities IEEE Computer Society

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

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

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

5. 2004-02 SAB Report 5 Liaisons ToFrom IEEE TABJim Isaak IEEE-SADon Wright IEEE-SA Standards BoardLowell Johnson SCC20John Sheppard Other SCCs JTC1François Coallier INCITS JTC1 TAGBob Pritchard JTC1/SC7 and SC7 TAGJim Moore IFIP AwardsJohn Walz Computer MagazineJack Cole PPCKathy Land TABJack ColeDenis Baggi Other Boards & Comm

6. 2004-02 SAB Report 6 Staff u Computer Society: John Daniel u IEEE-SA Staff Representative: Susan Tatiner, Noelle Humenick

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

8. 2004-02 SAB Report 8 Three Challenges for SAB u Challenge: Declining relevance of de jure standardization in IT profession, contrasted with an increasing need for professional norms. u Challenge: Simplify standardization for small producers. u Challenge: Broadening international impact of CS IT standardization efforts.

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

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

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

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

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

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

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

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