IEEE 1062-1998

IEEE 1062-1998 is the IEEE Recommended Practice for Software Acquisition, 1998 Edition, offering guidance for planning and managing the acquisition of software systems and related services. It addresses the practical steps involved in defining needs, evaluating suppliers, and structuring contracts so software purchases align with project goals and technical requirements. For organizations that need more disciplined procurement and reduced acquisition risk, this standard provides a useful reference point.

IEEE 1062-1998 overview

This recommended practice focuses on the software acquisition process rather than software design or coding. IEEE 1062-1998 is intended to support organizations in making more consistent decisions when procuring software, whether as a standalone product or as part of a larger system. It is especially relevant where requirements must be documented clearly, supplier capabilities compared carefully, and acceptance criteria defined in advance. The document helps bring structure to a process that can otherwise be informal and difficult to control.

Typical use cases

IEEE 1062-1998 is commonly used when an organization is selecting application software, embedded software support tools, or custom-developed software from external suppliers. It may also be useful in acquisition workflows for engineering programs, systems integration projects, and government or enterprise procurement efforts where software performance and deliverables must be specified clearly. Teams can use it to shape solicitation documents, review vendor responses, and plan contract oversight with greater consistency.

Why this standard matters

Software acquisition decisions can affect cost, schedule, interoperability, and long-term maintenance. IEEE 1062-1998 matters because it encourages a more disciplined approach to requirements definition, supplier evaluation, and acceptance planning. That can reduce misunderstandings during procurement and help ensure the acquired software better fits the intended operational environment. For organizations managing complex systems or multiple stakeholders, the standard can support better control over compliance, quality expectations, and acquisition risk.

• Software acquisition planning
• Supplier evaluation and selection
• Requirements and acceptance criteria
• Contract and delivery control