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.

Ingénierie du logiciel — Processus du cycle de vie — Acquisition des logiciels

General Information

Status
Published
Publication Date
09-Oct-2024
Current Stage
6060 - International Standard published
Start Date
10-Oct-2024
Due Date
14-Oct-2024
Completion Date
10-Oct-2024
Ref Project

Relations

Buy Standard

Standard
ISO/IEC/IEEE 41062:2024 - Software engineering — Life cycle processes — Software acquisition Released:10. 10. 2024
English language
81 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)


International
Standard
ISO/IEC/IEEE 41062
Second edition
Software engineering — Life cycle
2024-10
processes — Software acquisition
Ingénierie du logiciel — Processus du cycle de vie — Acquisition
des logiciels
Reference number
© IEEE 2024
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from IEEE at the address below.
Institute of Electrical and Electronics Engineers, Inc
3 Park Avenue, New York
NY 10016-5997, USA
Email: stds.ipr@ieee.org
Website: www.ieee.org
Published in Switzerland
© IEEE 2024 – All rights reserved
ii
Contents Page
Foreword .vi
Introduction .viii
1 Scope . 1
2 Normative references . 1
3 Terms, definitions and abbreviated terms . 1
3.1 Terms and definitions .1
3.2 Abbreviated terms .4
4 Software acquisition process . 4
4.1 General .4
4.2 Purpose .5
4.3 Outcomes .5
4.4 Structure of the software acquisition process .5
4.4.1 Software acquisition sub-processes .5
4.4.2 Defining the acquisition process .6
4.4.3 Tailoring the acquisition process.7
5 Software acquisition alternatives . 8
5.1 General .8
5.2 Custom-developed software .8
5.2.1 General .8
5.2.2 Advantages of custom-developed software .9
5.2.3 Disadvantages of custom-developed software .9
5.3 Off-the-shelf (OTS) software .9
5.3.1 General .9
5.3.2 Advantages of OTS software . . .10
5.3.3 Disadvantages of OTS software .10
5.4 Software as a service (SaaS) .11
5.4.1 General .11
5.4.2 Advantages of software as a service (SaaS).11
5.4.3 Disadvantages of SaaS .11
5.5 Free and open-source software (FOSS) . 12
5.5.1 General . 12

5.5.2 Advantages of FOSS. 12
5.5.3 Disadvantages of FOSS . 13
5.6 Services . 13
6 Planning and RFP sub-process. 14
6.1 Purpose .14
6.2 Outcomes . 15
6.3 Planning the software acquisition strategy . 15
6.3.1 Develop an acquisition strategy . 15
6.3.2 Perform feasibility study .16
6.3.3 Assess and manage risk .16
6.3.4 Agile development considerations .16
6.3.5 Initiate a planning process .18
6.3.6 Develop an acquisition plan . . .19
6.3.7 Form an acquisition team .19
6.3.8 Obtain assistance with acquisition .19
6.4 Defining the acquisition and content requirements .21
6.4.1 General .21
6.4.2 Types of requirements in an RFP . 22
6.4.3 Business requirements . 22
6.4.4 Software/System requirements . 23
6.4.5 Statement of work (SOW) .24
6.4.6 Performing verification and validation of requirements .24

© IEEE 2024 – All rights reserved
iii
6.5 Identifying potential suppliers .24
6.5.1 General .24
6.5.2 Advertising the acquisition .24
6.5.3 Pre-qualification . . 25
6.5.4 Streamlined pre-qualification . 26
6.5.5 No pre-qualification . 26
6.6 Preparing contract requirements .27
6.6.1 General .27
6.6.2 Request for information (RFI) .27
6.6.3 Request for quote (RFQ) .27
6.6.4 Request for proposals (RFP) . . 28
6.6.5 Contractual requirements . 30
7 Evaluation, selection, and contracting sub-process.33
7.1 Purpose . 33
7.2 Outcomes . 35
7.3 Evaluating proposals . 35
7.3.1 Planning for proposal evaluation . 35
7.3.2 Evaluation criteria . 35
7.3.3 Establishing proposal e
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.