UNLIMITED FREE ACCESS TO THE WORLD'S BEST IDEAS

close
Already an Engineering360 user? Log in.

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

Customize Your Engineering360 Experience

close
Privacy Policy

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

IEEE 1062

Recommended Practice for Software Acquisition

inactive
Buy Now
Organization: IEEE
Publication Date: 8 December 1998
Status: inactive
Page Count: 49
scope:

This is a recommended practice for performing software acquisitions. It describes a set of useful quality practices that can be selected and applied during one or more steps in a software acquisition process.

In this recommended practice, software products have been classified according to the degree to which the acquirer may specify the features of the software. They are: commercial-of-the-shelf (COTS), modified-off- the-shelf (MOTS), and fully developed item.

COTS software is stable and is normally well-defined in terms of documentation and known capabilities and limitations. It usually comes with "how to operate" documentation. COTS software is defined by a market-driven need. It is commercially available and its fitness for use has been demonstrated by a broad spectrum of commercial users. Also, the COTS software supplier does not advertise any willingness to modify the software for a specific customer.

MOTS software is similar to COTS software; however, MOTS software does advertise services to tailor the software to acquirer-specific requirements.

Fully developed software will often be unique for a specific application and will be produced on a one-of-a-kind or low-volume basis. The software typically will have the potential for future modification by the acquirer to meet changing needs. As a result, most of the documentation will be special to the project (with the exception of the supplier's standard documentation for the operating system, any standard application packages, and programming languages).

This recommended practice can be applied to software that runs on any computer system regardless of the size, complexity, or criticality of the software. However, this recommended practice is more suited for use on MOTS software and fully developed software. Each organization using this recommended practice will need to identify the classes of software to which this recommended practice applies and the specific quality characteristics and activities that need to be included within the acquisition process.

Document History

December 5, 2015
Recommended Practice for Software Acquisition
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...
IEEE 1062
December 8, 1998
Recommended Practice for Software Acquisition
This is a recommended practice for performing software acquisitions. It describes a set of useful quality practices that can be selected and applied during one or more steps in a software acquisition...
January 1, 1998
Recommended Practice for Software Acquisition
A description is not available for this item.
December 2, 1993
RECOMMENDED PRACTICE FOR SOFTWARE ACQUISITION; (IEEE COMPUTER SOCIETY DOCUMENT)
A description is not available for this item.
December 2, 1993
Recommended Practice for Software Acquisition
A description is not available for this item.
January 1, 1993
Recommended Practice for Software Acquisition
A description is not available for this item.

References

Advertisement