AS NZS 15271-1999 PDF
Name in English:
St AS NZS 15271-1999
Name in Russian:
Ст AS NZS 15271-1999
Original standard AS NZS 15271-1999 in PDF full version. Additional info + preview on request
Full title and description
AS/NZS 15271:1999 — Guide for AS/NZS ISO/IEC 12207 (Information technology — Software life cycle processes). This national adoption reproduces ISO/IEC TR 15271:1998 and provides explanatory guidance to help users select, tailor and apply the processes described in ISO/IEC 12207 for different types of software, projects and contractual situations.
Abstract
Provides guidance and explanatory material to support the application of ISO/IEC 12207 software life‑cycle processes. Topics include the architecture of software life‑cycle processes (primary, supporting and organizational), process tailoring and refinement, interfaces with systems engineering, quality management and metrics, and how to choose relevant processes for projects of varying size, complexity and contractual arrangement. The text is identical to ISO/IEC TR 15271:1998.
General information
- Status: Published (1999); the underlying technical report has since been superseded by later guidance documents — see FAQ for details.
- Publication date: 5 May 1999 (AS/NZS edition; original TR dated 1998).
- Publisher: Standards Australia / Standards New Zealand (joint adoption of ISO/IEC TR 15271).
- ICS / categories: 35.080 (Software).
- Edition / version: 1st edition (1999, identical to ISO/IEC TR 15271:1998).
- Number of pages: 49 (published TR / AS product listing).
Scope
This guide explains concepts and intent behind ISO/IEC 12207 and gives practical advice on which life‑cycle processes are likely to be applicable for different software types, development and acquisition contexts, organizational levels and contractual arrangements. It is intended to support project teams, procurement bodies and organizations in selecting, tailoring and improving software life‑cycle processes.
Key topics and requirements
- Overview of software life‑cycle architecture: primary, supporting and organizational processes.
- Guidance on process selection and tailoring according to project size, complexity and contractual needs.
- Interfaces between software life‑cycle processes and systems engineering activities.
- Recommendations for integration of quality assurance, verification, validation and maintenance processes.
- Discussion of metrics, documentation and process improvement/self‑assessment use cases.
These topics follow the structure and intent of ISO/IEC TR 15271 and are intended as explanatory guidance rather than normative requirements.
Typical use and users
Used by software engineers, systems engineers, project managers, quality assurance and process‑improvement teams, procurement and contract managers, and auditors who need to interpret and apply the processes of ISO/IEC 12207 in projects and organizations. It is commonly consulted during process tailoring, contract definition, and internal improvement initiatives.
Related standards
Closely related to ISO/IEC 12207 (software life‑cycle processes). The technical report ISO/IEC TR 15271:1998 (on which AS/NZS 15271:1999 is identical) was later incorporated into the broader guidance of ISO/IEC TR 24748‑3 and national adoptions such as AS/NZS ISO/IEC 12207:2013 and associated SA/SNZ TR materials that provide updated application guidance. Users applying contemporary processes should consult the later TRs and the current AS/ISO/IEEE 12207 editions for up‑to‑date normative process definitions.
Keywords
software life cycle, software processes, ISO/IEC 12207, process guidance, software engineering, process tailoring, verification and validation, maintenance, quality assurance.
FAQ
Q: What is this standard?
A: AS/NZS 15271:1999 is a national adoption (Australia/New Zealand) of ISO/IEC TR 15271:1998 — a technical report that provides guidance for applying the ISO/IEC 12207 software life‑cycle processes. It is a guidance document (technical report), not a normative process standard.
Q: What does it cover?
A: It covers explanatory guidance on the intent, scope and application of software life‑cycle processes: how to identify relevant processes for a project, how to tailor processes, interface issues with systems engineering, quality management considerations, metrics and documentation recommendations.
Q: Who typically uses it?
A: Project teams, systems and software engineers, QA and process‑improvement staff, procurement and contract managers, and auditors—anyone needing interpretative guidance to apply ISO/IEC 12207 in practice.
Q: Is it current or superseded?
A: The original ISO/IEC TR 15271:1998 (on which AS/NZS 15271:1999 is identical) has been superseded by later guidance (ISO/IEC TR 24748‑3:2011 and subsequent national TRs). National practice has evolved toward updated editions of ISO/IEC 12207 and companion TRs (for example AS/NZS ISO/IEC 12207:2013 and later AS/ISO/IEEE editions). Users should consult the newer TRs and current AS/ISO/IEEE 12207 editions for the most up‑to‑date normative and application guidance.
Q: Is it part of a series?
A: Yes — it is a technical report that supports ISO/IEC 12207 and forms part of the family of software/system life‑cycle process standards and guidance (ISO/IEC 12207, ISO/IEC 15288, ISO/IEC TR 24748 series and associated national adoptions). The TR was intended as companion guidance rather than a standalone normative specification.
Q: What are the key keywords?
A: software life cycle, software processes, process tailoring, ISO/IEC 12207, guidance, verification, validation, maintenance, quality assurance.