Standard Details
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.
| Standards Committee | |
| Status |
Active
|
| Board Approval |
2015-12-05
|
| History |
Published Date:2016-02-26
|
Additional Resources Details
| PAR |
Working Group Details
| Working Group |
1062_WG - RP for Software Acquisition Working Group
|
| Working Group Chair |
Marcus Hervey
|
| Standards Committee | |
| Society | |
| IEEE Program Manager | |
| Active Projects |
This standard describes a set of useful activities, tasks and methods that can be selected and applied during the acquisition of software or software services. The standard 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 commercial-off-the-shelf (COTS), custom, or open source software. Software services can include software development and sustainment, software integration, and software verification and validation. Security is included as a quality attribute considered during the acquisition. However, specific requirements for acquisition of information assurance (security) services and cloud services are not included.
|
| Existing Standards |
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.
|
|
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.
|