1. James W. Moore Liaison Representative IEEE Computer Society June 2004
IEEE CS/SC7 Liaison Report
Coordination of IEEE CS Software and System Engineering Standards with ISO/IEC JTC 1/SC 7
Report of May 2004 Plenary Meeting of SC7, Brisbane, Australia
James W. Moore Liaison Representative IEEE Computer Society June 2004
IEEE CS/SC7 Liaison Report

2. Background
2000: IEEE Computer Society became a Category A liaison to ISO/IEC JTC 1/SC 7 (Software and Systems Engineering)
Category A provides essentially all rights of a “national body” except voting.
IEEE CS SAB delegated responsibility for executing the liaison to its Software and Systems Engineering Standards Committee (S2ESC)
2001: Liaison policy and procedures were developed. Moore appointed as liaison representative. SAB concurred.
2001: IEEE-SA staff briefed on liaison plans.
2002: Based on earlier plans, S2ESC develops liaison strategy.
2003: SC7 approves “Vision of Liaison Outcomes” based on the strategy.
2003: SC7 approves coordination procedure.
2003: First projects begin.
IEEE CS/SC7 Liaison Report

3. Reporting Moore serves as liaison representative.
S2ESC has operational responsibility.
IEEE-SA approves contributions of all standards.
IEEE-SA negotiates intellectual property rights.
Results are reported to:
S2ESC
SAB
IEEE-SA staff
IEEE CS/SC7 Liaison Report

4. IEEE Standards
IEEE S2ESC standards are created by forming a consensus of individual technical professionals.
ISO/IEC JTC1 standards are formed by creating a consensus of “national bodies”. Each country has one vote.
IEEE-SA has a long history of international coordination on the content of important standards, e.g.:
ISO/IEC 9945 standards (POSIX) are identical with IEEE 1003 standards.
ISO/IEC 8802 standards (LAN/MAN) are identical with IEEE 802 standards.
Top right corner of cover page of ISO/IEC
IEEE CS/SC7 Liaison Report

5. IEEE has already adopted several SC7 standards
IS 12207, Software Life Cycle Processes (IEEE/EIA )
Supplemented with guides to data and process implementation
IS 12119, Software Packages--Quality and Testing (IEEE 1465)
IS 14102, Guidelines for Evaluation and Selection of CASE Tools (IEEE 1462)
IS , Functional Size Measurement Concepts (IEEE )
Project underway to adopt IS 15288, System Life Cycle Processes
Project underway to adopt IS 90003, Applying 9001 to Software
These standards were all adopted with minor changes to normative content.
Separate adoption virtually guarantees capricious differences.
The approved coordination procedure addresses this problem.
IEEE CS/SC7 Liaison Report

6. S2ESC standards cover some areas with no SC7 standard
Terminology
610.12: Glossary
Reuse:
1420.1, a, b: Libraries
1571: Reuse Processes
Risk management
1540: Software Risk Management Process
Systems engineering
1362: Concept of Operations
1233: Requirements Specification
1220: Systems Engineering Process
1228: Safety Plans
Software acquisition
1062
Software architecture description
1471
Software testing
829: Test Documentation
1008: Unit Testing
Internet best practices
2001: Web Page Engineering
Body of Knowledge
Guide to the SWEBOK
Coordination underway
IEEE CS/SC7 Liaison Report

7. IEEE CS Representatives at Brisbane Plenary of SC7
Lead Liaison Representative: Jim Moore
WG2, and life cycle data: Annette Reilly
WG7: Jim Moore
WG7, Harmonization Team: Terry Rout
WG7, 14764: Tom Pigoski
WG9, 15026: Mike Gayle
sWG9, 16085: Cheryl Jones
Also Terry Doran, chair of IEEE Std 1220
IEEE CS/SC7 Liaison Report

8. Summary of Coordination Results
5 SC7 standards being adopted by S2ESC: 12119, 14102, 14471, 15288,
4 IEEE-CS documents being adopted by SC7: 1220, 2001, (nee 1540), (SWEBOK)
4 projects to merge standards: /15289, 1219/14764, 1058/16326, /various
3 S2ESC standards to be submitted for study: 1063, 1471, 1517
3 major IEEE-CS positions accepted: process harmonization approach, functional size measurement, configuration management
IEEE-CS to lead study on system assurance requirements
IEEE-CS to lead study on international certification of software engineers
IEEE CS/SC7 Liaison Report

9. Plans and Procedures
“Vision of Liaison Outcomes” was updated with changes suggested by IEEE CS liaison representative.
Coordination procedure continues to work well.
Permits fast-track of S2ESC standards followed by a “coordinated revision”.
“Coordinated revision” synchronizes IEEE and SC7 ballots on drafts. SC7 performs ballot resolution. Consensus must be achieved in both organizations before publication.
IEEE CS/SC7 Liaison Report

10. WG2: Life Cycle Data
IEEE/EIA is a supplement to IEEE/EIA describing software life cycle data—but contains errors.
Draft IS also describes life cycle data.
IEEE participated in study groups to recommend an appropriate plan.
IEEE’s primary concern is transition for current users of
Scope of will be broadened to include system life cycle processes.
Annette Reilly (IEEE-CS) is editor of
IEEE CS/SC7 Liaison Report

11. WG2: User Documentation
WG2 has standards related to user documentation, notably IS
IEEE Std 1063 provides requirements on the content of user documentation.
IEEE CS is participating in a study group to determine a plan.
IEEE was requested to provide 1063 for study.
IEEE CS/SC7 Liaison Report

12. WG4: CASE Tools IEEE has adopted ISO/IEC 14102 as IEEE Std 1462.
WG4 is currently revising and IEEE CS will attempt to provide comments.
IEEE CS plans to adopt the results of the revision projects.
IEEE CS/SC7 Liaison Report

13. WG6: Software Packages
IEEE is an adoption of ISO/IEC 12119:1994.
WG6 is revising into a COTS software standard.
IEEE CS is providing comments.
IEEE CS plans to adopt the result.
IEEE CS/SC7 Liaison Report

14. WG7: System Life Cycle Processes
IEEE CS has started the process to adopt ISO/IEC
Balloting group is now being formed. Balloting will probably begin in June. Adoption would occur in early 2005.
The process will probably result in the addition of an informative annex referencing appropriate IEEE standards. An errata sheet might also be added.
IEEE CS/SC7 Liaison Report

15. WG7: Systems Engineering Process
IEEE Std 1220 concerns the Systems Engineering Process.
In consultation with WG7, IEEE is revising 1220 to remove incompatibilities with ISO/IEC Balloting group has been formed. Balloting will probably begin in June. Revision may complete in early 2005.
The result will be offered for fast-track and coordinated revision.
IEEE CS/SC7 Liaison Report

16. WG7: Software Life Cycle Processes
IEEE CS has adopted ISO/IEC 12207:1995 as IEEE/EIA SC7 has created two amendments which IEEE has not adopted. IEEE CS is awaiting further progress in harmonization.
IEEE CS participates in harmonization team (Terry Rout).
IEEE CS proposes that:
Process harmonization should precede the formulation of either process architecture or document architecture.
Following process harmonization, and should be “reconstructed” as a verification step.
We can then make thoughtful decisions regarding proposed changes to the two standards.
IEEE CS proposal for harmonization was adopted by US and then by SC 7/WG 7.
IEEE CS/SC7 Liaison Report

17. WG7: Software Maintenance
IEEE Std 1219 and ISO/IEC both concern the software maintenance process.
A coordinated revision is underway to merge the two standards (Tom Pigoski, editor).
IEEE ballot and SC7 CD ballot has completed. Both sets of comments were resolved. Next draft will be sent for FCD ballot and IEEE recirculation.
Both organizations will adopt the same result.
IEEE CS/SC7 Liaison Report

18. WG7: Quality Management of Software
IEEE CS is conducting a project to adopt ISO/IEC
IEEE CS plans to add an annex explaining the relationship to other IEEE standards.
SC7 is planning to develop a guide on quality management of systems.
IEEE CS/SC7 Liaison Report

19. WG7: Software Project Management
Both organizations have SW project management stds.
IEEE Std 1490 is an adoption of the Project Management Body of Knowledge.
IEEE Std 1058 is a standard concerning software project management plans.
ISO/IEC TR supplements the management process of with guidance compatible with PMBOK and ISO
IEEE CS has proposed to WG7 a coordinated revision of IEEE Std 1058 and ISO/IEC TR into a standard.
Both organizations would adopt the result.
IEEE CS was invited to draft a New Work Item Proposal.
IEEE CS/SC7 Liaison Report

20. WG7: Configuration Management
IEEE Std 828 concerns CM plans.
ISO/IEC TR concerns CM process.
IEEE CS participated in a WG7 study group considering future plans. The recommendations were adopted:
Withdraw SC7 technical report
Reference IEEE Std 828
IEEE CS/SC7 Liaison Report

21. WG9: System and Software Assurance
IEEE CS has provided comments on WD3 of the revision of
IEEE CS proposes that:
15026 should place product requirements on the form of an “assurance case”.
15026 should relate the assurance case to the system life cycle by providing additional outcomes to the processes and stages of
Moore was appointed to chair a study group to determine how to perform the mapping.
IEEE CS/SC7 Liaison Report

22. sWG9: Risk Management Process
IEEE Std 1540 was accepted via fast-track as ISO/IEC
Fast-track comments are now being resolved via coordinated revision.
IEEE ballot and CD ballot has completed. Both sets of comments were resolved. Next draft goes to FCD ballot and IEEE recirculation. (Terry Rout, chair; Cheryl Jones and Tom Pigoski, editors)
Both organizations will adopt the same standard.
IEEE CS/SC7 Liaison Report

23. WG12: Functional Size Measurement
IEEE Std is an adoption of ISO/IEC
IEEE CS believes that revision of is not needed.
IEEE CS negotiated a plan permitting WG12 to develop a corrigendum to the standard.
IEEE CS/SC7 Liaison Report

24. WG19: Internet Best Practices
IEEE Std 2001, concerning internet best practices, was circulated to SC7 for comment.
SC7 invited IEEE to submit 2001 for fast-track balloting. Any comments will be resolved in a coordinated revision.
IEEE CS plans to participate in forthcoming JTC1 Workshop on Web Services.
IEEE CS/SC7 Liaison Report

25. WG20: SWEBOK Guide
IEEE CS completed final technical editing of SWEBOK Guide 2004.
This version incorporates comments from PDTR and DTR ballot of
IEEE CS draft was accepted as the final text.
The result will be published as ISO/IEC TR
IEEE CS/SC7 Liaison Report

26. WG22: Vocabulary
IEEE CS has contributed IEEE Std as a base document.
IEEE CS provided a convener for a working group. Unfortunately the convener lost his funding.
New convener was appointed.
IEEE CS was invited to name an editor.
IEEE CS/SC7 Liaison Report

27. Study Group: Architectures
Study standards for architecture
IEEE CS was invited to submit IEEE Std 1471, Architectural Description, for study.
IEEE CS/SC7 Liaison Report

28. Study Group: COTS, Reuse, NDI, Open Source
IEEE CS has been requested to contribute IEEE Std 1517, Reuse Processes, for study.
IEEE CS/SC7 Liaison Report

29. Study Group: Certification
Steve Seidman to chair study group on professional certification of “software engineers”
IEEE CS invited to contribute material
Possible contents:
“Task analysis” and “test specification” for exam
Culturally appropriate exams
International portability of certification
Respect for licensing schemes
Interim report, ; final report,
IEEE CS/SC7 Liaison Report

30. Backup
IEEE CS/SC7 Liaison Report

31. History of Liaison Relationship
IEEE CS/SC7 Liaison Report