4071-Australian Standard-SPMP
4071-Australian Standard-SPMP
Australian Standard
Review of Australian Standards. To keep abreast of progress in industry, Australi an Standards are subject
to periodic review and are kept up to date by the issue of amendments or new editi ons as necessary. It is
important therefore that Standards users ensure that they are in possession of the latest editi on, and any
amendments thereto.
Full detail s of all Australi an Standards and related publications will be found in the Standards Australi a
Catalogue of Publications; this information is supplemented each month by the magazine ‘The Australi an
Standard’, which subscribing members receive, and which gives details of new publications, new editi ons
and amendments, and of withdrawn Standards.
Suggesti ons for improvements to Australian Standards, addressed to the head offi ce of Standards Australi a,
are welcomed. Noti fi cati on of any inaccuracy or ambiguity found in an Australian Standard should be made
without delay in order that the matter may be investigated and appropriate action taken.
AS 4071—1992
Australian Standard
PREFACE
This Standard was prepared by the Standards Australia Committee on Software Engineering. It is identical
with and has been reproduced from ANSI/IEEE Std 1058.1 IEEE Standard for Software Project
Management Plans.
Under arrangements made between Standards Australia and the international Standards bodies, ISO and
IEC, as well as certain other Standards organizations, users of this Australian Standard are advised of the
following:
Copyright of the content of this Standard remains the property of IEEE. The copyright of this edition is
vested in Standards Australia.
For the purpose of this Australian Standard, the IEEE text should be modified as follows:
References The references to ANSI/IEEE Standards should be replaced by references to Australian
Standards as follows:
Reference to ANSI/IEEE Standard Australian Standard
729 IEEE Standard Glossary of Software —
Engineering Terminology
730 IEEE Standard for Software Quality —
Assurance Plans
828 I E E E S t an d a r d f o r S o f tw a re 4042 Software configuration management plans
Configuration Management Plans
829 IEEE Standard for Software Test Docu- 4006 Software test documentation
mentation
983 IEEE Guide for Software Quality —
Assurance Planning
1012 IEEE Standard for Software Verifications —
and Validation Plans
This is a free 6 page sample. Access the full version online.
CONTENTS
SECTION Page
2. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
STANDARDS AUSTRALIA
Australian Standard
1. Scope and References 1.2 References. The standards listed here should be
consulted when applying this standard. The latest
1.1 Scope. This standard prescribes the format and revisions shall apply.
content of software project management plans. A
software project management plan is the controlling [1] ANSI/IEEE Std 729-1983, IEEE Standard
document for managing a software project; it defines Glossary of Software Engineering Terminology.
the technical and managerial processes necessary to
satisfy the project requirements. [2] ANSI/IEEE Std 730-1984, IEEE Standard for
Software Quality Assurance Plans.
This standard may be applied to all types of software
projects. Use of this standard is not restricted by the [3] ANSI/IEEE Std 828-1983, IEEE Standard for
size, complexity, or criticality of the software Software Configuration Management Plans.
product. This standard is applicable to all forms of
product delivery media, including firmware,
[4] ANSI/IEEE Std 829-1983, IEEE Standard for
embedded systems code, programmable logic arrays,
Software Test Documentation.
and software-in-silicon. This standard can be applied
to any and all segments of a software product
lifecycle. [5] ANSI/IEEE Std 983-1986, IEEE Guide for
Software Quality Assurance Planning.
This standard identifies the minimal set of elements
that shall appear in all software project management [6] ANSI/IEEE Std 1012-1986, IEEE Standard for
plans. In order to conform to this standard, software Software Verification and Validation Plans.
project management plans must adhere to the format
and content for project plans specified in the 2. Definitions
standard. However, users of this standard may
incorporate other elements by appending additional The definitions listed here establish meanings within
sections or subsections to their project management the context of this standard. Definitions of other
plans. In any case, the numbering scheme of the terms that may be appropriate within the context of
This is a free 6 page sample. Access the full version online.
required sections and subsections must adhere to the this standard can be found in ANSI/IEEE Std
format specified in this standard. Various sections 729-1983 [1].
and subsections of a software project management
plan may be included in the plan by direct activity. A major unit of work to be completed in
incorporation or by reference to other plans and achieving the objectives of a software project. An
documents. activity has precise starting and ending dates,
incorporates a set of tasks to be completed, consumes
This standard for software project management plans resources, and results in work products. An activity
incorporates and subsumes the software development may contain other activities in a hierarchical manner.
plans described in ANSI/IEEE Std 729-1983 [1] 1 and
ANSI/IEEE Std 730-1984 [2].
1
The numbers in brackets corr espond to those of the references
in 1.2.
COPYRIGHT
AS 4071-1992 Software project management plans
This is a free 6 page sample. Access the full version online.
SAI Global also carries a wide range of publications from a wide variety of Standards Publishers: