AS/NZS 15939:2003

1 - AS/NZS 15939:2003 SOFTWARE ENGINEERING-SOFTWARE MEASUREMENT PROCESS
4 - PREFACE
5 - CONTENTS
6 - INTRODUCTION
7 - 1 Scope
7 - 1.1 Purpose
7 - 1.2 Field of application
7 - 1.3 Tailoring this International Standard
7 - 1.4 Conformance
8 - 1.5 Limitations
8 - 2 Normative reference
8 - 3 Terms and definitions
8 - 3.1 acquirer
8 - 3.2 attribute
9 - 3.3 base measure
9 - 3.4 data
9 - 3.5 data provider
9 - 3.6 data store
9 - 3.7 decision criteria
9 - 3.8 derived measure
9 - 3.9 entity
9 - 3.10 indicator
9 - 3.11 indicator value
9 - 3.12 information need
9 - 3.13 information product
10 - 3.14 measure (noun)
10 - 3.15 measure (verb)
10 - 3.16 measurable concept
10 - 3.17 measurement
10 - 3.18 measurement analyst
10 - 3.19 measurement experience base
10 - 3.20 measurement function
10 - 3.21 measurement librarian
10 - 3.22 measurement method
10 - 3.23 measurement procedure
11 - 3.24 measurement process
11 - 3.25 measurement process owner
11 - 3.26 measurement sponsor
11 - 3.27 measurement user
11 - 3.28 model
11 - 3.29 observation
11 - 3.30 operator
11 - 3.31 organisational unit
11 - 3.32 process
11 - 3.33 scale
12 - 3.34 software product
12 - 3.35 software service
12 - 3.36 stakeholder
12 - 3.37 supplier
12 - 3.38 system
12 - 3.39 unit of measurement
12 - 3.40 user
12 - 3.41 value
13 - 4 Application of this International Standard
13 - 4.1 Purpose and outcomes of the software measurement process
13 - 4.2 Overview of this International Standard
16 - 4.3 Organisation of this International Standard
17 - 5 Description of the activities
17 - 5.1 Establish and sustain measurement commitment
18 - 5.2 Plan the measurement process
19 - 5.2.1 Characterise organisational unit
19 - 5.2.2 Identify information needs
19 - 5.2.3 Select measures
20 - 5.2.4 Define data collection, analysis, and reporting procedures
20 - 5.2.5 Define criteria for evaluating the information products and the measurement process
21 - 5.2.6 Review, approve, and provide resources for measurement tasks
21 - 5.2.7 Acquire and deploy supporting technologies
21 - 5.3 Perform the measurement process
22 - 5.3.1 Integrate procedures
22 - 5.3.2 Collect data
23 - 5.3.3 Analyse data and develop information products
23 - 5.3.4 Communicate results
23 - 5.4 Evaluate measurement
23 - 5.4.1 Evaluate information products and the measurement process
24 - 5.4.2 Identify potential improvements
25 - Annex A - The measurement information model
25 - A.1 General
27 - A.2 Model description
30 - A.3 Examples
33 - Annex B - Measurement process work products
35 - Annex C - Example criteria for selecting measures
37 - Annex D - Example criteria for evaluating an information product
37 - D.1 General
37 - D.2 Use of information products
37 - D.3 Confidence in an information product
37 - D.4 Evidence of fitness for purpose of an information product
38 - D.5 Understandability of information products
38 - D.6 Satisfaction of the assumptions of an indicator model
38 - D.7 Accuracy of a measurement procedure
39 - D.8 Repeatability of a measurement method
39 - D.9 Reproducibility of a measurement method
40 - Annex E - Example criteria for evaluating the performance of the measurement process
40 - E.1 General
40 - E.2 Timeliness
40 - E.3 Efficiency
40 - E.4 Defect containment
40 - E.5 Customer satisfaction
40 - E.6 Process compliance
41 - Annex F - Example elements of measurement planning
42 - Annex G - Guidelines for reporting information products
43 - Bibliography

Defines a software measurement process applicable to all software-related engineering and management disciplines.

1.1 PurposeThis International Standard identifies the activities and tasks that are necessary to successfully identify, define, select, apply, and improve software measurement within an overall project or organisational measurement structure. It also provides definitions for measurement terms commonly used within the software industry.This International Standard does not catalogue software measures, nor does it provide a recommended set of measures to apply on software projects. It does identify a process that supports defining a suitable set of measures that address specific information needs.1.2 Field of applicationThis International Standard is intended to be used by software suppliers and acquirers. Software suppliers include personnel performing management, technical, and quality management functions in software development, maintenance, integration, and product support organisations. Software acquirers include personnel performing management, technical, and quality management functions in software procurement and user organisations.The following are examples of how this International Standard can be used:•By a supplier to implement a software measurement process to address specific project or organisational information requirements.•By an acquirer (or third-party agents) for evaluating conformance of the supplier’s software measurement process to this International Standard.•By an acquirer (or third-party agents) to implement a software measurement process to address specific technical and project management information requirements related to the acquisition.•In a contract between an acquirer and a supplier as a method for defining the software process and product measurement information to be exchanged.1.3 Tailoring this International StandardThis International Standard contains a set of activities and tasks that comprise a software measurement process that meets the specific needs of software organisations and projects. The tailoring process consists of modifying the non-normative descriptions of the tasks to achieve the purpose and outcomes of the software measurement process. All normative clauses shall be satisfied. New activities and tasks not defined in this International Standard may be added as part of tailoring.1.4 ConformanceConformance to this International Standard is defined as satisfying the purpose and outcomes of the measurement process and all of the normative clauses within the tasks in Clause 5. Any organisation imposing this International Standard as a condition of trade is responsible for specifying and making public all task-specific criteria to be imposed in conjunction with this International Standard.Throughout this International Standard, “shall” is used to express a provision that is binding on the party that is applying this International Standard, “should” to express a recommendation among other possibilities, and “may” to indicate a course of action permissible within the limits of the International Standard.It is the responsibility of the organisation to maintain appropriate evidence of satisfaction of the normative clauses for purposes of demonstrating conformance.1.5 LimitationsThis International Standard does not assume or prescribe an organisational model for measurement. The user of this International Standard should decide, for example, whether a separate measurement function is necessary within the organisation, whether the measurement function should be integrated within individual software projects, or across projects, based on the current organisational structure, culture, and prevailing constraints.This International Standard is not intended to prescribe the name, format, or explicit content of the documentation to be produced. The International Standard does not imply that documents be packaged, or combined in some fashion. These decisions are left to the user of the International Standard.The measurement process should be appropriately integrated with the organisational quality system. Not all aspects of internal audits and non-compliance reporting are covered explicitly in this International Standard, as they are assumed to be in the domain of the quality system.This International Standard is not intended to conflict with any organisational policies, standards, or procedures that are already in place. However, any conflict should be resolved and any overriding conditions and situations need to be cited in writing as exceptions to the application of the International Standard.

First published as AS/NZS 15939:2003.