AS 4071-1992 (R2014)

Abstract

Prescribes the format and content of software project management plans. This Standard is identical with and reproduced from ANSI/IEEE 1058.1-1987.

RECONFIRMATION NOTICE
Technical Committee IT-015 has reviewed the content of this publication and in accordance with Standards Australia procedures for reconfirmation, it has been determined that the publication is still valid and does not require change.
Certain documents referenced in the publication may have been amended since the original date of publication. Users are advised to ensure that they are using the latest versions of such documents as appropriate, unless advised otherwise in this Reconfirmation Notice.
Approved for reconfirmation in accordance with Standards Australia procedures for reconfirmation on 17 January 2014.
The following are represented on Technical Committee IT-015:

Australian Computer Society
Australian Society for Technical Communication (NSW)
Charles Sturt University
Department of Defence (Australia)
Griffith University
La Trobe University
National Association of Testing Authorities Australia
National ICT Australia
NSW Business Chamber
Quantitative Enterprise Software Performance
Systems Engineering Society of Australia
University of Technology, Sydney

Scope

This standard prescribes the format and content of software project management plans. A software project management plan is the controlling document for managing a software project; it defines the technical and managerial processes necessary to satisfy the project requirements.

This standard may be applied to all types of software projects. Use of this standard is not restricted by the size, complexity, or criticality of the software product. This standard is applicable to all forms of product delivery media, including firmware, embedded systems code, programmable logic arrays, and software-in-silicon. This standard can be applied to any and all segments of a software product lifecycle.

This standard identifies the minimal set of elements that shall appear in all software project management plans. In order to conform to this standard, software project management plans must adhere to the format and content for project plans specified in the standard. However, users of this standard may incorporate other elements by appending additional sections or subsections to their project management plans. In any case, the numbering scheme of the required sections and subsections must adhere to the format specified in this standard. Various sections and subsections of a software project management plan may be included in the plan by direct incorporation or by reference to other plans and documents.

This standard for software project management plans incorporates and subsumes the software development
plans described in ANSI/IEEE Std 729-1983 [1]1and ANSI/IEEE Std 730-1984 [2].

General Product Information

Published
Document Type	Standard
Status	Current
Publisher	Standards Australia
ProductNote	Reconfirmed 30/01/2014. This standard has been reconfirmed in Australia in 2014 and remains current in New Zealand. Reconfirmation Notice 30/01/2014
Pages
ISBN
Committee	IT-015