IEEE/ISO/IEC 41062 2019
$42.25
ISO/IEC/IEEE International Standard – Software engineering – Recommended practice for software acquisition
| Published By | Publication Date | Number of Pages |
| IEEE | 2019 | 72 |
– Active. 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.
PDF Catalog
| PDF Pages | PDF Title |
|---|---|
| 5 | Title page |
| 7 | Important Notices and Disclaimers Concerning IEEE Standards Documents |
| 10 | Participants |
| 12 | Introduction |
| 13 | Contents |
| 15 | Important Notice 1. Overview 1.1 Scope |
| 16 | 1.2 Purpose 2. Normative references |
| 17 | 3. Definitions and terms 3.1 Definitions 3.2 Use of should, may, and can 4. Software acquisition alternatives 4.1 Introduction |
| 18 | 4.2 Custom-developed software 4.2.1 Advantages of custom-developed software 4.2.2 Disadvantages of custom-developed software 4.3 Off-the-shelf (OTS) software |
| 19 | 4.3.1 Advantages of OTS 4.3.2 Disadvantages of OTS 4.4 Software as a service (SaaS) |
| 20 | 4.4.1 Advantages of SaaS 4.4.2 Disadvantages of SaaS |
| 22 | 5. Software acquisition process 5.1 Purpose 5.1.1 Outcomes |
| 23 | 5.1.2 Activities and tasks 5.1.3 Principal acquisition roles 5.2 Eight steps in acquiring quality software |
| 26 | 5.3 Step 1: Planning the software acquisition strategy 5.3.1 Purpose 5.3.2 Outcomes 5.3.3 Activities and tasks 5.3.3.1 Initiate a planning process 5.3.3.2 Develop an acquisition strategy |
| 27 | 5.3.3.3 Develop an acquisition plan 5.3.3.4 Include contracting practices |
| 28 | 5.3.3.5 Obtain acquisition services from other organizations 5.3.3.6 Tailor the process 5.4 Step 2: Defining the acquisition and software requirements 5.4.1 Purpose 5.4.2 Outcomes |
| 29 | 5.4.3 Activities and tasks 5.4.3.1 Define the software being acquired 5.4.3.2 Establish supplier evaluation criteria 5.4.3.3 Establish acquirer and supplier obligations 5.4.3.4 Develop plans to evaluate and accept software and services 5.4.3.5 Develop contingency plans |
| 30 | 5.5 Step 3: Identifying potential suppliers 5.5.1 Purpose 5.5.2 Outcomes 5.5.3 Activities and tasks 5.5.3.1 Gather software supplier’s information |
| 31 | 5.5.3.2 Review software supplier’s information 5.5.3.3 Survey users of the supplier’s software |
| 32 | 5.6 Step 4: Preparing contract requirements 5.6.1 Purpose 5.6.2 Outcomes 5.6.3 Activities and tasks 5.6.3.1 Determine the required quality of the work 5.6.3.2 Determine how payment is to be made |
| 33 | 5.6.3.3 Determine nonperformance remedies 5.6.3.4 Prepare contract provisions 5.6.3.5 Review contract provisions with legal counsel |
| 34 | 5.7 Step 5: Evaluating proposals and selecting the supplier 5.7.1 Purpose 5.7.2 Outcomes 5.7.3 Activities and tasks 5.7.3.1 Evaluate supplier proposals |
| 35 | 5.7.3.2 Visit supplier facilities 5.7.3.3 Select a qualified supplier 5.7.3.4 Negotiate the contract |
| 36 | 5.8 Step 6: Managing for supplier performance 5.8.1 Purpose 5.8.2 Outcomes 5.8.3 Activities and tasks |
| 37 | 5.9 Step 7: Accepting the software 5.9.1 Purpose 5.9.2 Outcomes 5.9.3 Activities and tasks 5.9.3.1 Review and update the acceptance criteria |
| 38 | 5.9.3.2 Conduct a review and test of the software 5.9.3.3 Manage the testing process 5.9.4 Document the test results 5.10 Step 8: Evaluating the process and identifying improvement opportunities 5.10.1 Purpose |
| 39 | 5.10.2 Outcomes 5.10.3 Activities and tasks 5.10.3.1 Evaluate contracting practices 5.10.3.2 Evaluate software product quality 5.10.3.3 Evaluate supplier performance |
| 40 | 6. Quality assurance for software acquisition 6.1 Objectives of quality assurance in software acquisition 6.2 Implementing quality assurance in software acquisition |
| 42 | Annex A (informative) Checklists for quality software acquisition processes |
| 61 | Annex B (informative) Software safety assurance and software information security assurance |
| 65 | Annex C (informative) Rights in technical data and software usage |
| 66 | Annex D (informative) Acquisition plan guidelines |
| 70 | Annex E (informative) Bibliography |
| 71 | Blank Page |
