Standard: IEEE 1062

RECOMMENDED PRACTICE FOR SOFTWARE ACQUISITION

This standard is available for individual purchase.

or unlock this standard with a subscription to IHS Standards Expert

IHS Standards Expert subscription, simplifies and expedites the process for finding and managing standards by giving you access to standards from over 370 standards developing organizations (SDOs).

FEATURES & BENEFITS
  • Maximize product development and R&D with direct access to over 1.6 million standards
  • Discover new markets: Identify unmet needs and discover next-generation technologies
  • Improve quality by leveraging consistent standards to meet customer and market requirements
  • Minimize risk: Mitigate liability and better understand compliance regulations
  • Boost efficiency: Speed up research, capture and reuse expertise
For additional product information, visit the IHS Standards Expert page.

HOW TO SUBSCRIBE
For more information or a custom quote, visit the IHS Contact Us page for regional contact information.
Scope:

This recommended practice describes a set of useful quality considerations that can be selected and applied during one or more steps in a software acquisition process. 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 commercial-off-the-shelf (COTS), 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 the organization’s acquisition process. Security will be included as a quality attribute considered during the acquisition.

Purpose

This recommended practice is designed to help organizations and individuals incorporate quality, including security considerations during the definition, evaluation, selection, and acceptance of supplier software for operational use. It will also help determine how supplier software should be evaluated, tested, and accepted for delivery to end users. This recommended practice is intended to satisfy the following objectives:

Promote consistency within organizations in acquiring software from software suppliers.

Provide useful practices on including quality, security, safety and data rights considerations during acquisition planning.

Provide useful practices on evaluating and qualifying supplier capabilities to meet user requirements.

Provide useful practices on evaluating and qualifying supplier software.

Assist individuals or organizations judging the quality of supplier software for referral to end users.

Assist suppliers in understanding how the software will be evaluated, tested, and accepted for delivery to end users.

Success in acquiring high-quality software products and services from software suppliers can be achieved by doing the following things:

a) Identifying quality characteristics necessary to achieve the acquirer’s objectives

b) Selecting suppliers most capable of meeting the acquisition objectives

c) Including quality considerations in the planning, evaluation, and acceptance activities

d) Developing an organizational strategy for acquiring software

e) Establishing a software acquisition process using the eight steps stated in 5.2 as a starting point

f) Putting the defined process into practice

NASA Notes:
  • This recommended practice describes the management and execution of software acquisition activities. The document is designed to help organizations incorporate quality
    considerations during the definition, evaluation, selection,
    and acceptance of supplier software for operational use.
    The document is also useful for determining how supplier software should be evaluated, tested, and accepted for delivery to end users.
Organization: The Institute of Electrical and Electronics Engineers, Inc.
Document Number: ieee 1062
Publish Date: 2015-12-05
Page Count: 69
Change Type: COMPLETE REVISION
Available Languages: EN
DOD Adopted: NO
ANSI Approved: NO
Most Recent Revision: YES
Current Version: YES
Status: Active

Document History

Document # Change Type Update Date Revision Status
IEEE 1062 Change Type: REAF Update Date: 1998-12-08 Revision: 98 Status: INAC
IEEE 1062 Change Type: Update Date: 1993-12-02 Revision: 93 Status: INAC
IEEE 1062 Change Type: Update Date: 1993-01-01 Revision: 4.1 Status: INAC
IEEE 1062 Change Type: Update Date: 1993-12-02 Revision: 4 Status: INAC
IEEE 1062 Change Type: Revision: 84 Status: INAC

This Standard References

Showing 10 of 22.

view more
Advertisement
Advertisement
Advertisement
Advertisement