درباره ما
IEEE 1062
Recommended Practice for Software Acquisition - Includes 1062-1993 and 1062a-1998; IEEE Computer Society Document
Year: 2002
Abstract: 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-offThe-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.
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-offThe-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.
Subject: acquirer
Show full item record
| contributor author | IEEE - The Institute of Electrical and Electronics Engineers, Inc. | |
| date accessioned | 2017-09-04T16:35:27Z | |
| date available | 2017-09-04T16:35:27Z | |
| date copyright | 12/08/1998 (R 2002) | |
| date issued | 2002 | |
| identifier other | VADGCBAAAAAAAAAA.pdf | |
| identifier uri | https://yse.yabesh.ir/std/handle/yse/98962 | |
| description abstract | 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-offThe-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. | |
| language | English | |
| title | IEEE 1062 | num |
| title | Recommended Practice for Software Acquisition - Includes 1062-1993 and 1062a-1998; IEEE Computer Society Document | en |
| type | standard | |
| page | 49 | |
| status | Active | |
| tree | IEEE - The Institute of Electrical and Electronics Engineers, Inc.:;2002 | |
| contenttype | fulltext | |
| subject keywords | acquirer | |
| subject keywords | modified-off-the-shelf software | |
| subject keywords | software acquisition life cycle | |
| subject keywords | software acquisition process | |
| subject keywords | supplier |