A Survey of Software Engineering Standards ASMA & SQA Meeting

Mike Berry Email: Michael.Berry@student.unsw.edu.au

21/10/02

A Personal Journey Standards are for people who cant think for themselves 1975
21/10/02 2

From Sceptic to Standard-builder

1987 Responsible for internal standards manual at Qantas 1989 Became aware of AS3563 : Software Quality Assurance 1990 Became aware of ISO/IEC 9126: Software Product Evaluation - Quality Characteristics and guidelines for their use 1995 Used ISO/IEC 12207 as the basis for Software Process Design 1996 Joined WG13 developing ISO/IEC 15939: Software Measurement Process
21/10/02 3

What happened to the Qantas Internal Standards Manual?

Displaced by a set of Manuals for a proprietary methodology from a Consulting Company
21/10/02 4

What ever happened to AS3563?

It was superseded by ISO 9000-3 Quality Management and Quality Assurance Standards--Part 3: Guidelines for the Application of ISO 9001 to the Development, Supply, and Maintenance of Software
21/10/02 5

What happened to ISO/IEC 9126?

Its been substantially upgraded and repackaged as SQuaRE Latest version: ISO/IEC 9126 -:2001 : Software engineering - Product quality - Part 1: Quality model
21/10/02 6

What happened to ISO/IEC 12207?

Became the standard makers standard but didnt make a big impact on the industry May be replaced by ISO/IEC ISO/IEC 15228 System Life Cycle Processes

21/10/02

What will happen to ISO/IEC 15939?

Uptake will be a function of the demand for software measurement Integrates into 12207 Framework Supports other standards that need measurement
21/10/02 8

My Conclusion
Standards have their own lifecycle of creation, maintenance and decommisioning
21/10/02 9

Whos in the Standards game?

21/10/02

10

Setting Standards
ISO/IEC JTC1/SC7 & the Working Groups IEEE
has entered into a Category A Liaison with ISO/IEC JTC1/SC7 to coordinate work on software and systems engineering standards

Software Engineering Institute

CMM was a product of their imagination CMMI seeking to comply with ISO/IEC 15504, SEI participating in SPICE trials Uses architecture of ISO/IEC standards where appropriate eg used 15939 for basis of Measurement & Analysis process area
21/10/02 11

Whats Out There?

21/10/02

12

ISO/IEC

Software Engineering Standards

Source: Stan Magee @ WWW.12207.com Configuration Management ISO/IEC TR 15846 Software Engineering-Software Life Cycle ProcessConfiguration Management for Software Design ISO/IEC 14102 Guideline for the Evaluation and Selection of CASE Tools, ISO/IEC TR 14759 Mockup and Prototype Documentation ISO/IEC 15910Software User Documentation Process, ISO/IEC TR 9294 Information Processing--Guidelines for the Management of Software Documentation Function Points ISO/IEC 14143-1Software Measurement--Functional Size Measurement-Part1: Definition of Concepts Human Factors ISO/IEC 14598-1 Information Technology-Evaluation of Software Products-General Guide Maintenance ISO/IEC 14764 Software Maintenance 21/10/02 13

ISO/IEC

Software Engineering Standards

Project Management ISO/IEC TR 16326 Guide for the Application of ISO/IEC 12207 to Project Management Quality ISO 9000-3 Quality Management and Quality Assurance Standards-Part 3: Guidelines for the Application of ISO 9001 to the Development, Supply, and Maintenance of Software ISO 9001-2000 Quality Management Systems Requirements ISO/IEC 14598-1 Information Technology-Evaluation of Software Products-General Guide ISO/IEC 9126Software Product Evaluation - Quality Characteristics and guidelines for their use ISO/IEC 12119 Information Technology-Software Packages-Quality Requirements and Testing Security ISO 15408-1Information Technology-- Security Techniques -Evaluation Criteria for IT Security -- Part 1: Introduction and General Model
21/10/02 14

ISO 9000:2000
ISO 9000: Quality management systems Fundamentals and vocabulary ISO 9001: Quality management systems Requirements ISO 9004: Quality management systems Guidance for Performance Improvement ISO 19011:Guidelines on Quality and Environmental Auditing Replacement for 9000-3 is coming 21/10/02 15

ISO/IEC 12207 Information Technology-Software Life Cycle Processes

The Standard Makers Standard

21/10/02 16

History of ISO/IEC 12207

Produced by ISO/IEC JTC1/SC7 Participants
Australia, Canada, Denmark, Finland, France, Germany, Ireland, Italy, Japan, Korea, Netherlands, Spain, Sweden, UK, USA

Convener: James Roberts (USA) Project Editor: Raghu Singh (USA) Schedule: June 1988-August 1995 4 working drafts, 2 committee drafts, 1 DIS 17,000 labor-hours of effort [project editors estimate] Source: Leonard L. Tripp & Raghu Singh.
21/10/02 17

Purpose of 12207
To establish a common framework for the life cycle of software
In particular a standard for standards developers

Acquire, supply, develop, operate, and maintain software Undertakes broader scope than previous standards Manage, control, and improve the framework Recognizes that software is part of a system a project is part of an enterprise To establish a basis for world trade in software
21/10/02 18

12207 Maintenance
Companion Technical Report
ISO/IEC TR 15271Guide for ISO/IEC 12207 (Software Life Cycle Processes)

Amendment 1: 2000 ISO/IEC 15228 System Life Cycle Processes

21/10/02

19

ISO/IEC 12207:2002 - Amendment 1

An interim revision -establishes a coordinated set of software process information that can be used for process definition and process assessment and improvement. Accommodates the requirements of current and developing SC 7 standards and technical reports ISO/IEC 12207 and ISO/IEC TR 15504, considers other standards, i.e., ISO/IEC 14598 and ISO/IEC 15939. Using ISO/IEC 12207 as the basis for organizations software life cycle process and in two-party situations resulted in lessons learned Development of ISO/IEC TR 15504-2 highlighted issues in regard to the granularity of the process definition in ISO/IEC 12207 i.e.; it was difficult to derive a process rating component for the purpose of process assessment and improvement. Amendment resolves the granularity issue and provides ISO/IEC 12207 with purposes and outcomes needed for process assessment and improvement. Removes the need for the Process Reference Model in 15504
21/10/02 20

ISO/IEC 15288 Background

Source: ISO/IEC JTC1/SC7 /N2646R

International Market for systems engineering services and related products services Need for a common process framework In 1994 no systems engineering standard addressed hardware and software in a concurrent and integrated fashion Conventional engineering and software engineering were marching along their separate ways, particularly in the areas of terminology, design representation, and measurement Systems engineering itself was not fully integrated.
21/10/02 21

ISO/IEC 15288 Scope

Establishes a common framework for describing the life cycle of systems created by humans. It defines a set of processes and associated terminology. These processes can be applied at any level in the hierarchy of a systems development. ISO/IEC 15288 concerns those systems that are man-made and may be configured with one or more of the following: hardware, software, humans, or processes.
21/10/02 22

SQuaRE
Software Product Quality Requirements and Evaluation Source: SC7/WG6 N477
21/10/02 23

Introduction
Project 07.13 (ISO/IEC 9126 and 14598 Series) will be accomplished soon (as at Jan 2001) Some inconsistency in the series and, therefore, need for the new architecture were identified. The need for one unique name identifying IS and TR of 9126 and 14598 series was identified. Originally created at the WG6 meeting in 1999, and revised at the 2000 meeting.

21/10/02

24

Background
Software quality requirements shall be stated and evaluated using a quality model and standard metrics
Requirements for a product quality shall be defined using quality model and metrics. Quality models and metrics shall be standardized. Products quality shall be evaluated based on quality model using metrics against quality requirements.

SQuaRE is aiming to provide integrated and comprehensive set of international standards and technical reports on software product quality. SQuaRE includes international standards and technical reports on quality model and metrics, as well as quality requirements and evaluation
21/10/02 25

Scope
SQuaRE is a set of international standards and technical reports on software product quality SQuaRE consists of the following:
Quality requirements, Quality evaluation, Quality models and Quality metrics, as well as the umbrella division.

SQuaRE includes:
Definitions of terms, reference models and the general guide, Requirements (shall) and recommendations (should), and Individual guides to the use of the series.

Intended users of SQuaRE include, but not limited to:

software developers, acquirers, independent evaluators, and their managers.

SQuaRE replaces current ISO/IEC 9126 series and 14598 series

21/10/02 26

Architecture
9126-1n: Software Product Quality 9126-2n: Quality Model 9126-3n: Quality Metrics
30: General Requirements and Guide (NP) 31: Base Metrics (NP) 32: Internal Metrics 33: External Metrics 34: Quality in Use Metrics 35: Documentation of Evaluation Module

9126-4n: Quality Requirements 9126-5n: Quality Evaluation

21/10/02 27

Conclusion Key themes in Standards Work

Constant change Harmonisation Granularity Vocabulary Commercialisation Time to Market Vested Interests
21/10/02 28