1 HARMONIZATION OF ISO/IEC 14764 AND IEEE STD 1219 Thomas M. Pigoski Paul R. Croll IEEE Computer Society Montreal, May 2003.

Slides:

Advertisements

Similar presentations

SIGAda2001© 2001, The MITRE Corporation. Permission is granted to reproduce without modification.James W. Moore - 1 ISO/IEC Standardization James W. Moore.

Advertisements

ANSI/ASQ E Overview Gary L. Johnson U.S. EPA

Technical update on ISO 9001:2015 Colin MacNee Duncan MacNee Limited

ISO/DIS 9001:2015 What effects on the nuclear sector? NUCSIG EVENT, BIRCHWOOD, 24 JULY 2014 GRAHAM WATSON.

Privacy and Security for the HES Gateway Presentation and discussion for SC25 WG1 By: Ludo Bertsch and Tim Schoechle Arlington, USA April 24, 2013 SC25/WG1-N1620.

Software life cycle processes Purpose n A new international standard (ISO/IEC 12207:1995(E) that –establishes a common framework for software life cycle.

1 REQUIREMENTS ENGINEERING and SYSTEMS ANALYSIS Elements and Definitions.

Maintenance Basic concepts. Definition of maintenance  All changes done to software after delivery (IEEE Std 1219)  Modifications due to a problem or.

Defining the Activities. Documents  Goal Statement defines why helps manage expectations  Statement of Work what gets delivered defines scope  Software.

Software testing standards ISO/IEC and 33063

Harmonization and consistency in ISO/TC 211 standards by Serena Coetzee Chair, ISO/TC 211 Programme Maintenance Group at the Tutorial held on 5 December.

Requirements Management Plan - Documents

ISO/IEC A review of the new standard for laboratory accreditation

S2ESC Planning Group: Quality Management John Walz Scott Duncan 15-Jun-04.

TRAINING SOLUTIONS ISO 14001: DEVELOPMENT & IMPLEMENTATION For more information contact Victoria: (Tel) (Fax) ( )

“Here’s why you need the new wheels, too…” Shawn and Steve Image from

Typical Software Documents with an emphasis on writing proposals.

IEEE S2ESC Report1 Software And Systems Engineering Standards Committee (S2ESC) Paul R. Croll S2ESC Sponsor Chair June 2004 Report.

Software Quality Assurance Lecture 4. Lecture Outline ISO ISO 9000 Series of Standards ISO 9001: 2000 Overview ISO 9001: 2008 ISO 9003: 2004 Overview.

Report of Liaison to ISO/IEC JTC1/SC7 James W. Moore, CSDP Liaison Representative Prepared for Presentation to IEEE CS BOG, June.

May 2007: SAB, D2 IEEE-CS/SC7 Liaison Report 1 IEEE Computer Society Category A Liaison to JTC 1/SC 7: Status Report Jim Moore IEEE CS Liaison Representative.

1 Configuration Management “The Cookbook Approach”

Y. KOMACHI Proposal for standardization of Typeface classifications and their mappings.

SQA System Overview Chapter 4. Where we have been so far, Where we are going Where do software errors come from? What is quality? How can quality be measured?

IEEE Standard : The Revised PQ MonitoringStandard Randy Collins Chair, 1159 Working Group IEEE Power Engineering Society Winter Meeting New York.

“Software Life Cycle Processes”

Introduction to the ISO series ISO – principles and vocabulary (in development) ISO – ISMS requirements (BS7799 – Part 2) ISO –

Page 1 ISO/IEC JTC 1/SC 7/WG 7 N Summary of the Alignment of System and Software Life Cycle Process Standards The material in this briefing.

The Final Study Period Report on MFI 6: Model registration procedure SC32WG2 Meeting, Sydney May 26, 2008 H. Horiuchi, Keqing He, Doo-Kwon Baik SC32WG2.

Proposed Revision of IEEE Standard SCC41 Meeting – Delft – 6 July 2010 Jim Hoffmeyer Western Telecom Consultants, Inc. Chair, IEEE Vice Chair,

SQI © T.P. Rout and Griffith University, 1996 A Unified Reference Model for the Processes of Software and System Life Cycles Terry Rout Software Quality.

DICOM and ISO/TC215 Hidenori Shinoda Charles Parisot.

ISA–The Instrumentation, Systems, and Automation Society ISA SP-99 Introduction: Manufacturing and Control Systems Security -- Kickoff Meeting Call to.

A Best Practice Approach for Software Maintenance - Sustaining Critical Capability Paul R. Croll Chair, IEEE Software and Systems Engineering Standards.

1 15 quality goals for requirements  Justified  Correct  Complete  Consistent  Unambiguous  Feasible  Abstract  Traceable  Delimited  Interfaced.

IEEE CS SAB, Nov 2007 For Computer Society Internal Use Only 1 S2ESC Report Standards Activities Board Meeting November 6-7, 2007 Submitted by Paul Croll.

[ISO Water footprint – potential standard]

SC7 - IEEE CS Activity Status Report – T. Doran 6 November 2007 To: J. Walz IEEE CS SAB

1 Overview of Maintenance CPRE 416-Software Evolution and Maintenance-Lecture 3.

Y. KOMACHI Proposal for standardization of Typeface classifications and their mappings.

Omniran CF00 1 Content and outline considerations for Annex: Applicability to non-IEEE 802 PHY layer technologies Date: Authors:

SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.

Doc.: IEEE /0858r0 Submission July 2008 Jesse Walker, Intel CorporationSlide 1 IEEE 802 Presentation for Xi’an Meeting Date: Authors:

Liaison Update IEEE Computer Society Category A Liaison to JTC 1/SC 7 James W. Moore, CSDP The MITRE Corporation The opinions contained.

Dr. Trevor Smith Chair ISO/TC 176 Quality Management & Quality Assurance Worldwide Quality Director Global Manufacturing & Logistics Eastman Kodak Company.

Quality Management Systems Advice from ISO/TC 176 for Sector-specific applications.

DOCUMENTATION ISO/IEC 17025:2005 Documentation.

1 CURRENT PRACTICES AND FUTURE CHALLENGES IN METHODS VALIDATION – NEW AREAS OF APPLICATION THE POINT OF VIEW OF AN ACCREDITATION BODY EURACHEM Workshop.

Report to IEEE CS SESC of IEEE CS/SC7 Liaison1 Report to IEEE CS SESC: Report of IEEE CS / SC7 Liaison James W. Moore Liaison Representative IEEE.

Software Engineering — Software Life Cycle Processes — Maintenance

Introduction for the Implementation of Software Configuration Management I thought I knew it all !

James W. Moore Liaison Representative IEEE Computer Society June 2004

ISO/IEC JTC 1/SC 7 Working Group 42 - Architecture Johan Bendz

Learn Your Information Security Management System

IEEE CS SAB, Mar 2009 IEEE Computer Society Category A Liaison to ISO/IEC JTC 1/SC 7: Status Report Jim Moore IEEE Computer Society Liaison Representative.

Software and Systems Engineering Standards Sponsor Committee Report

For Computer Society Internal Use Only

IEEE Std 1074: Standard for Software Lifecycle

Introduction of ISO/IEC 17065: 2012

Software Life Cycle Risk Management

Defining the Activities

IEEE SC 2 May 12, 2014 Robert Konnik

Date: < yyyy-mm-dd >

Main changes in 2018 revision of ISO/IEC Directives, Part 2

I&C requirements and configuration management

DRAFT ISO 10006:2017 Revision Overview Quality management systems - Guidelines for quality management in projects ISO/TC176 TG 01.

DRAFT ISO 10007:2017 Revision Overview Quality management – Guidelines for configuration management ISO/TC176 TG 01.

DRAFT ISO 10006:2017 Revision Overview Quality management systems - Guidelines for quality management in projects ISO/TC176 TG 01.

DRAFT ISO 10013:20XX Overview Quality management – Guidelines for quality management system documented information ISO/TC176 TG 01.

Presentation transcript:

1 HARMONIZATION OF ISO/IEC AND IEEE STD 1219 Thomas M. Pigoski Paul R. Croll IEEE Computer Society Montreal, May 2003

2 OVERVIEW 1.INTRODUCTION 2.APPROACH 3.PROPOSED CONVERGENCE 4.FUTURE

3 1. INTRODUCTION  IEEE Computer Society Liaison to SC7 (Jim Moore)  This briefing is offered in behalf of IEEE Computer Society.  Discusses harmonization of IEEE Std 1219 and ISO/IEC

4 1. INTRODUCTION (Cont’d)  New Proposal  Tom Pigoski (Project Editor)  Paul Croll (Co-editor)

5 1. INTRODUCTION (Cont’d)  HARMONIZATION GOAL – Achieve consistency and/or compatibility in these areas: 1.Concepts. 2.Terminology. 3.Readability. 4.Level of detail and/or compatibility. 5.Processes. 6.Document structure. 7.Normative references.

6 1. INTRODUCTION (Cont’d) 8.Common interfacing mechanism with the ISO 9000 family of standards. 9.Conformance with requirements from ISO/IEC as applicable. [Harmonization Study Group Report – N0652, ]

7 2. APPROACH  INPUTS  ISO/IEC (1999).  6 defects.  IEEE Std 1219 (1998).  ISO/IEC Amendment 1.  ISO/IEC and ISO/IEC “harmonization” efforts.

8 2. APPROACH (Cont’d)  ASSUMPTIONS  Use ISO/IEC basic structure.  Fold IEEE Std 1219 into structure.

9 2. APPROACH (Cont’d)  ISSUES  Activities  ISO/IEC – 6 Activities.  IEEE Std 1219 – 7 Activities.

10 2. APPROACH (Cont’d)  ACTIVITIES ISO/IEC Process Implementation Problem and modification analysis Modification implementation Maintenance review/acceptance Migration Software retirement IEEE STD 1219 Problem identification Analysis Design Implementation System test Acceptance test Delivery

11 2. APPROACH (Cont’d)  ISSUES (Continued)  ISO/IEC provides a process model.  IEEE Std 1219 provides best practices.  IEEE Std 1219 Annexes  Mostly Informative.  One Normative.  Soft copies showing structure of both standards.

12 3.PROPOSED CONVERGENCE ISO/IEC – CLAUSE NUMBER PROPOSED MAPPING OF IEEE 1219 TO ISO/IEC Foreword Introduction 1Scope1.1 Scope 1.1Purpose1.1 Scope 1.2Field of Application1.1 Scope 1.3Limitations1.1 Scope 2Conformance1.1 Scope 3Normative references2. References 4Terms and definitions3. Definitions and acronyms 5Application of this international standard 5.1Maintenance Process 5.2Organization of this international standard1.1 Scope 6Implementation considerations (Note – Clause name only) 6.1Introduction1.1 Scope

13 3.PROPOSED CONVERGENCE (Cont’d) ISO/IEC – CLAUSE NUMBER PROPOSED MAPPING OF IEEE 1219 TO ISO/IEC Types of maintenance3.1 Definitions 4.1 Problem/modification identification, classification, and prioritization 6.3Arrangements for maintenance 6.4Tools for maintenanceAnnex B, B.5 software tools (Informative) Annex B, Table B.3 Methods and tools for maintenance (Informative 6.5Software measurement1.1 Scope 4.1 (Table 3) Annex A, A.12 Metrics, measures (Informative) 6.6Documentation of process

14 3. PROPOSED CONVERGENCE (Cont’d) ISO/IEC – CLAUSE NUMBER PROPOSED MAPPING OF IEEE 1219 TO ISO/IEC Early involvement in developmentAnnex A, A.3 Maintenance planning (Informative) 6.8Maintainability 6.9Software transitionAnnex A, A.3 Maintenance planning (Informative) 6.10Documentation 7Software maintenance strategy (Note – Clause name only) 7.1IntroductionAnnex A, A.3 Maintenance Planning Annex C Maintenance plan guidelines (Normative) 7.2The maintenance conceptAnnex A, A.3 Maintenance Planning Annex C Maintenance plan guidelines (Normative)

15 ISO/IEC – CLAUSE NUMBER PROPOSED MAPPING OF IEEE 1219 TO ISO/IEC Maintenance planningAnnex A, A.3 Maintenance planning (Informative) Annex C Maintenance plan guidelines (Informative) 7.4Resource analysisAnnex A, A.3 Maintenance planning (Informative) Annex A, A.3.1 Determine maintenance effort (Informative) 8Maintenance processes4. Software maintenance Annex A (Informative) 8.1Process Implementation 3. PROPOSED CONVERGENCE (Cont’d)

16 ISO/IEC – CLAUSE NUMBER PROPOSED MAPPING OF IEEE 1219 TO ISO/IEC Problem and modification analysis4.1 Problem/modification identification, classification, and prioritization 4.2 Analysis 8.3Modification implementation4.3 Design 4.4 Implementation 4.5 System test 4.6 Acceptance test 8.4Maintenance review/acceptance4.7 Delivery 8.5Migration 8.6Software retirement Annex A(Informative) Cross-reference between ISO/IEC and ISO/IEC Bibliography 3.PROPOSED CONVERGENCE (Cont’d)

17 4. FUTURE  If NP approved:  Need National Bodies to work on harmonization.  Need Project Plan.