To establish a correlation between the content of software acquisition plans as defined in 1062 and the content of such plans as defined in IEEE 12207.1, Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data by adding an annex which will correlate the assumptions relating to content of the two documents and trace content between subject documentation.
- Sponsor Committee
- C/S2ESC - Software & Systems Engineering Standards Committee
- Status
- Superseded Standard
- Board Approval
- 1998-12-08
- History
-
- ANSI Approved:
- 1999-11-16
- Reaffirmed:
- 2002-09-12
Working Group Details
- Society
- IEEE Computer Society
- Sponsor Committee
- C/S2ESC - Software & Systems Engineering Standards Committee
- Working Group
-
1062_WG - RP for Software Acquisition Working Group
- IEEE Program Manager
- Patricia Roder
Contact Patricia Roder - Working Group Chair
- Marcus Hervey
Other Activities From This Working Group
Current projects that have been authorized by the IEEE SA Standards Board to develop a standard.
No Active Projects
Standards approved by the IEEE SA Standards Board that are within the 10-year lifecycle.
41062-2024
ISO/IEC/IEEE International Standard - Software Engineering - Life cycle processes - Software Acquisition
This document describes a set of useful activities, tasks, methods, and practices that acquirers of software and related services from unrelated (external) suppliers can apply to help ensure an efficient and effective acquisition of software or software services. These practices can be applied in competitive and in sole source procurements, regardless of the type, size, complexity, and cost of the acquisition. The document can be applied to software that runs on any computer system regardless of its size, complexity, or criticality. The software supply chain can include integration of off-the-shelf (OTS), custom, software as a service (SaaS), or open-source software. Software services can include software development and sustainment (maintenance), integration, verification (testing) and operation. Security and safety are included as attributes to be considered during the acquisition. However, specific requirements for acquisition of information assurance (security), safety, and cloud services are not included.
These standards have been replaced with a revised version of the standard, or by a compilation of the original active standard and all its existing amendments, corrigenda, and errata.
1062-1993
IEEE Recommended Practice for Software Acquisition
Superseded by 1062-1998. A set of useful quality practices that can be selected and applied during one or more steps in a software acquisition process is described. This recommended practice can be applied to software that runs on any computer system regardless of the size, complexity, or criticality of the software, but is more suited for use on modified-off-the-shelf software and fully developed software.
1062-2015
IEEE Recommended Practice for Software Acquisition
A set of useful quality considerations that can be selected and applied during one or more steps in a software acquisition process is described in this recommended practice. The recommended practices can be applied to software that runs on any computer system regardless of the size, complexity, or criticality of the software. The software supply chain may include integration of off-the-shelf (OTS), custom, or free and open source software (FOSS). Each organization or individual using this recommended practice will need to identify the specific quality and activities that need to be included within its acquisition process.
These standards have been removed from active status through a ballot where the standard is made inactive as a consensus decision of a balloting group.
No Inactive-Withdrawn Standards
These standards are removed from active status through an administrative process for standards that have not undergone a revision process within 10 years.
No Inactive-Reserved Standards