Report to IEEE CS SESC: Report of IEEE CS SC7 Liaison - PowerPoint PPT Presentation

1 / 38
About This Presentation
Title:

Report to IEEE CS SESC: Report of IEEE CS SC7 Liaison

Description:

IEEE CS originates all of the Information Technology standards approved by the IEEE. ... New SC7 study group for System Quality Management. ... – PowerPoint PPT presentation

Number of Views:192
Avg rating:3.0/5.0
Slides: 39
Provided by: jamesw78
Category:
Tags: ieee | sesc | liaison | report | sc7 | study | work

less

Transcript and Presenter's Notes

Title: Report to IEEE CS SESC: Report of IEEE CS SC7 Liaison


1
Report to IEEE CS SESCReport of IEEE CS / SC7
Liaison
  • James W. MooreLiaison RepresentativeIEEE
    Computer SocietyFt Lauderdale, August 2003

2
To Do List for SESC Meeting
  • Review status of liaison effort (this briefing)
  • Approve coordination procedure
  • Approve changes in Instructions to ILR

3
Purpose of this Presentation
  • Summarize the status of the Category A liaison
    between IEEE CS and ISO/IEC JTC1/SC7.
  • Summarize the steps being taken by IEEE CS and
    ISO/IEC JTC1/SC7 to contribute to the agreed
    objectives.

4
Institute of Electrical and Electronics Engineers
  • IEEE is the worlds largest organization of
    technical professionals--about 375,000
    individuals.
  • It publishes 30 of the worlds technical
    literature in its areas of interest.
  • It has a collection of about 50 standards for
    software and systems engineering.
  • With about 100,000 members, the IEEE Computer
    Society is the largest of the 36 Technical
    Societies of the IEEE.
  • IEEE CS originates all of the Information
    Technology standards approved by the IEEE.
  • All IEEE standards are initiated, approved and
    published by the IEEE Standards Association.

5
Responsible Parties in IEEE
IEEE
Societies
Computer Society Board of Governors
Standards Association Board of Governors
SWEBOK Editorial Team
Tech Committees
Technical Council on Software Engineering
IEEE CSStandards Activity Board
IEEE SAStandards Board
Software Engineering Standards Committee
6
IEEE and the Computer Society are International
in Scope
  • IEEE has members in 150 countries.
  • About half of IEEE CS members have non-US
    addresses. Non-US membership is growing more
    rapidly.
  • IEEE standards are used in many countries, e.g.
    Australia, India, European Space Agency.
  • Many SC7 experts contribute to SESC standards.

7
IEEE Standards
  • IEEE standards are created by forming a consensus
    of individual technical professionals. (In a few
    cases, organizational balloting is used.)
  • 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-3 standards (LAN/MAN) are identical
    with IEEE 802.3 standards.

Top right corner of cover page of ISO/IEC 8802-3
8
IEEE CS Software Engineering Standards Committee
(SESC)
  • Purpose from SESC Charter
  • Codify the norms of professional software
    engineering practices into standards.
  • Promote use of software engineering standards
    among clients, practitioners, and educators.
  • Harmonize national and international software
    engineering standards development.
  • Scope from SESC Fundamental Policy 2
  • Standardization of processes, products,
    resources, notations, methods, nomenclatures, and
    techniques for the engineering of software and
    systems dependent on software.

9
IEEE has already adopted several SC7 standards
  • IS 12207, Software Life Cycle Processes (IEEE/EIA
    12207.0)
  • 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 14143-1, Functional Size Measurement Concepts
    (IEEE 14143.1)

These standards were all adopted with minor
changes to normative content. Separate adoption
virtually guarantees capricious differences. The
approved coordination procedure addresses this
problem.
10
IEEE CS standards cover some areas with no SC7
standard
  • Terminology
  • 610.12 Glossary
  • Reuse
  • 1420.1, 1420.1a, 1420.1b 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

11
History of Liaison Relationship
12
Status Plans
  • Vision of Liaison Outcomes was circulated to
    SC7 as 07N2742 and approved 11-0-1 as summarized
    in 07N2803.
  • It provides a road map for harmonization of the
    collections.
  • IEEE CS will offer proposals that implement the
    plan.
  • It would be appropriate for SC7 and IEEE CS to
    jointly set priorities for implementing the plan.

13
Status Procedures
  • 07N2860 is the approved set of coordination
    procedures approved at the May 2003 meeting of
    SC7.

14
Status Terminology and Concepts
  • An NP is being balloted as 07N2882.
  • Coordinated adoption is proposed.
  • US has offered Perry DeWeese as convener.
  • IEEE CS has contributed IEEE Std 610.12.
  • Update proposed actions to indicate coordinated
    adoption.

15
NP for Vocabulary
16
Status Quality Management
  • IEEE-SA has decided to adopt 9000-3 alone rather
    than with ASQ.
  • New SC7 study group for System Quality
    Management.
  • New ISO 10005 includes an annex with a SW Quality
    Mgmt Plan.
  • Update proposed actions to remove ASQ
    coordination.

17
Status Systems Engineering
  • WG7 requested first revision of 1220 by IEEE CS
    alone.
  • T. Doran is chair of IEEE WG.
  • WG7 has appointed liaison reps and proposed
    revision topics.
  • Result will be fast-tracked.
  • INCOSE wants OR status.
  • Update to indicate actual plan for 1220 and for
    harmonization.

18
12207/15288 Harmonization
  • An NP is currently under ballot for a project to
    harmonize 15288, 12207 and other documents.
  • Alain Faisandier (France) is the editor. INCOSE
    and IEEE CS will each be asked to offer a
    co-editor.
  • (Eventually there will be more editors for the
    various documents.)
  • We need a list of acceptable candidates to
    solicit.
  • Should IEEE adopt the current ISO/IEC 15288?

19
Status Product Quality
  • IEEE SESC has adopted the quality model of 9126-1
    as a policy. Future SESC standards will use the
    terminology of 9126-1.

20
Status Life Cycle Process Framework
  • SC7 is initiating a corrigendum to the amendment.

21
Status Maintenance process
  • An NP is under ballot to merge IEEE 1219 and
    ISO/IEC 14764 via coordinated adoption.
  • US has offered Tom Pigoski and Paul Croll as
    editors.
  • IEEE CS has contributed 1219.

22
NP for Maintenance Process
23
Status Measurement process
  • IEEE CS SESC has adopted the ISO/IEC 15939
    measurement framework as a policy for measurement
    standards.

24
Status Risk management process
  • IEEE 1540 passed fast-track ballot as ISO/IEC
    16085.
  • Comment disposition was written. Revised standard
    was drafted. NP is under ballot.
  • Concurrent CDR was requested not under ballot.
  • IEEE PAR was approved and balloting group is
    being formed.

25
NP for 16085 Revision
26
Status Supporting Processes
  • Should we pursue coordinated revision of ISO/IEC
    16326 and IEEE Std 1058, both to be harmonized
    with new PMBOK?

27
Status Process Assessment
28
Status Process Construction
29
Status Safety
30
Status Documentation (1 of 2 Data from Life
Cycle Processes)
  • IEEE CS desires a single, shared standard for
    process data products. IEEE CS is willing to
    contribute 12207.1, or adopt 15289, or work
    jointly to develop a document.
  • SC7 study group formedchaired by Annette Reilly.
  • Revise to emphasize migration from 12207.1

31
Status Documentation(2 of 2 User Documentation)
  • IEEE CS is willing to offer 1063 for fast-track.
  • IEEE CS is willing to revise IEEE 1063 via the
    coordinated adoption process for better fit with
    ISO/IEC 18019.
  • 18019 would describe process. 1063 would describe
    product.
  • SC7 study group was formed.

32
Status Functional Size Measurement
33
Status CASE Tools
  • SC7 is deciding whether to revise 14471 and
    14102.
  • Do we want to pursue coordinated adoption?

34
Status Notations
35
Status SWEBOK
  • Comments from PDTR ballot have been recorded for
    final revision.
  • Unchanged draft submitted for DTR ballot.
  • Final SWEBOK revision will be submitted again.

36
Status Internet Best Practices
  • Revision of IEEE Std 2001 has been completed.
  • IEEE CS is willing to submit for fast-track if so
    requested.
  • SC7 has invited submission for informal
    consideration prior to fast-track.
  • Waiting for release letter from IEEE-SA.

37
Status Other Standards
38
IEEE CS Representatives at Montréal Plenary of
SC7, May 2003
  • Overall, AG, WG9, WG18
  • Jim Moore
  • WG2
  • Annette Reilly User documentation Data produced
    by life cycle processes
  • WG7
  • Terry Doran Harmonization of IEEE 1220 with
    ISO/IEC 15288 (System Life Cycle Processes)
  • Tom Pigoski and Paul Croll Convergence of IEEE
    1219 and ISO/IEC 14764 (Maintenance)
  • Annette Reilly Data produced by life cycle
    processes
  • sWG9
  • Robert Charette and Cheryl Jones Revision of
    ISO/IEC 16085 (same as IEEE Std 1540)
  • WG20
  • Claude Laporte, Alain Abran, Pierre Bourque, and
    Robert Dupuis DTR 19759 (SWEBOK Guide)
  • Planned WG22
  • Perry DeWeese Vocabulary project
Write a Comment
User Comments (0)
About PowerShow.com