1、 MIL-HDBK-Lb7 = 70 025bL84 T30 NOT MEASUREMENT 1 SENSITIVE MIL-HDBK-1467 10 DECEMBER 1997 SUPERSEDING SEE 6.2 DEPARTMENT OF DEFENSE HANDBOOK ACQUISITION OF SOFTWARE ENVIRONMENTS AND SUPPORT SOFTWARE This handbook is for guidance only. Do not cite this document as a requirement. AMSC NIA AREA MCCR DI
2、STRIBUTION STATEMENT A. Approved for public release; distribution is unlimited. Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-HDBK-1467 9999970 0256185 977 = MIL-HDBK- 1467 FOREWORD 1. This handbook is approved for use by all Departments and Ag
3、encies of the Department of Defense OD). 2. This handbook is for guidance only. This handbook cannot be cited as a requirement. If it is, the contractor does not have to comply. 3. In order to provide life cycle software engineering for their assigned systems, life cycle support organizations need r
4、ich engineering environments that give them the capabilities needed to satis this mission. 3.1 First, life cycle support organizations establish and maintain a common operating environment (COE) which contains most of the items needed to support the systems in their domains or product-lines. A COE i
5、s the overarching environment, which is the source of the ingredients from which life cycle support organizations develop and maintain software. The COE can be thought of as a virtual repository. One component is the assets from legacy systems that have been certified for reuse. Another component is
6、 the commercial-off-the-shelf (COTS) software that is applicable to the software being developed and maintained. Also, cross-domain reusable assets from other COES, such as Ada run-time kernels and kahan filters, are included. Other items in the COE include architectures, requirements, design, algor
7、ithms, and test cases. Section 4 of this handbook focuses on providing guidance for the acquisition of new items to be integrated into a COE. 3.2 Second, life cycle support organbations support the software of a specific system in their domain or product-line through the use of a Software Engineerin
8、g Environment (SEE). The SEE is composed of software development and maintenance tools integrated with equipment and unique software for each target computer system. The SEE can be one of the COE repositories. Section 5 of this handbook defines the efforts necessary to ensure the existence of a comp
9、lete life cycle support capability for contractually deliverable application software when it enters the operational inventory. Since this may include the acquisition of specific items needed to enrich the SEE, some or all of section 4 may also be applicable. 4. This handbook is designed to recogniz
10、e the needs and consraints of existing life cycle support organizations and, at the same time, allow the contractor the flexibility to develop items and manage the contract in accordance with the contractors best judgement and practices. Accordingly, this handbook does not indicate the approach to b
11、e used by the contractor. The guidance contained in this handbook is predicated on the contracting activity identifj4ng in the request for proposal the life cycle support organization and any of its items that are designated for use by the contractor. Subject to the constraints imposed by the contra
12、cting activity, the contractor may propose to use the existing resources of the contracting activity, to use the contractors own resources (either existing or to be developed), or to select from a wide range of Provided by IHSNot for ResaleNo reproduction or networking permitted without license from
13、 IHS-,-,- MIL-HDBK-L4b7 9999970 025bL8b 803 D MIL-HDBK- 1467 other options. The contractor should be required to identify the selected approach in the proposal for the contracted effort. The contractors approach should be considered during source selection and be subject to approval by the contracti
14、ng activity prior to implementation. 5. This handbook addresses a small portion of the overall software acquisition process. For those organizations that do not have extensive experience in software acquisition, it is recommended that the Software Acquisition Capability Maturity Model (SA-CMM) be co
15、nsulted. The SA-CMM is a collaborative work of authors fi-om government, industry, and the Software Engineering Institute (SEI) of Carnegie Mellon University in Pittsburgh, PA. The SA-CMM identifies a minimum set of actions that, when implemented, will improve the capability of the organizations sof
16、tware acquisition process. It has been developed to provide organizations a roadmap for implementing software acquisition process improvement. Idormation regarding the SA-CMM may be obtained fiom the SEI. 6. Beneficial comments (recomendations, additions, deletions) and any pertinent data which may
17、be of use in improving this document should be addressed to: Commander, US Army Tank-automotive and Armament Command, A“: AMSTA-AR-FSF-S, Picatinny Arsenal, NJ 07806-5000, by using the self-addressed Standardization Document Improvement Proposal (DD Form 1426) appearing at the end of this document o
18、r by letter. . lll Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,- MIL-HDBK-L467 m 9999970 0256187 74T = MIL-HDBK- 1467 CONTENTS Paragraph FOREWORD 1. SCOPE 1.1 Purpose 1.2 Application 1.2.1 COE items 1.2.2 SEE items 1.3 Type of contract 1.4 Non-con
19、tractual use 2. APPLICABLE DOCUMENTS 3. DEFINITIONS 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.8.1 3.8.2 3.8.3 3.8.4 3.9 3.10 3.1 1 3.11.1 3.11.2 3.12 3.12.1 3.12.2 3.13 3.14 Page u. 1 1 1 1 1 1 1 2 3 Common operating environment (COE) 3 Contracting activity 3 Contracting activity -designated resources 3 Con
20、tractor 3 COTS 3 Data rights 3 Host computer system 3 ptem sources 3 Commercially available item 3 Privately developed item 3 Contracting activity-designated item 4 Developmental item 4 Previously developed item 4 Product-line 4 Software 4 Application software 4 Support software 4 Sohare engineering
21、 environment (SEE) 4 Developmental software engineering environment SEE) 5 Life cycle software engineering environment (LCSEE) 5 Target computer system 5 Technical architecture 5 iv Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,- MIL-HDBK-1q67 m 999
22、9970 0256188 686 m Paragrauh 4. COEITEMS 4.1 4.1.1 4.1.2 4.1.3 4.1.3.1 4.1.3.2 4.1.3.3 4.1.4 4.1.5 4.1.6 4.1.7 4.1.8 4.1.9 4.1.10 4.2. 4.2.1 42.1.1 4.2.1.2 4.2.1.3 , 4.2.1.4 4.2.1.5 4.2.2 4.2.2.1 4.2.2.2 4.2.2.3 4.2.2.4 4.2.2.5 4.2.3 4.2.3.1 4.2.3.2 4.2.3.3 4.2.3.4 4.2.3.5 4.2.4 4.2.4.1 4.2.4.2 4.2.
23、4.3 MIL-HDBK-1467 CONTENTS (contd) Contracting activity guidelines Non-technical contractuai requirements Product technical contractuai requirements Product compatibility contractual requirements Physical repository interface requirements Product-line requirements Domain requirements Organizational
24、requirements Documentation requirements Quality assessment requirements Configuration management requirements Change requirements Acceptance requirements Software development requirements Contractor requirements Commercially available items Documentation guidelines Quality assessment guidelies Confi
25、guration management guidelines Item changes Item acceptance guidelines Privately developed items Documentation guidelines Quality assessment guidelines Configuration management guidelines Item changes Item acceptance guidelines Contracting activity -designated items Documentation guidelines Quality
26、assessment guidelines Configuration management guidelines Item changes Item acceptance guidelines Developmental items Documentation guidelines Quality assessment guidelines Codiguration management guidelines Page 6 6 6 6 6 6 6 6 6 6 7 7 7 7 7 7 8 8 8 8 8 9 9 9 9 9 9 10 10 10 10 10 10 10 10 10 10 11
27、V Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,- MIL-HDBK-1467 m 9999970 025b189 512 m Paragraph 4.2.4.4 4.2.4.5 4.3 4.3.1 4.3.2 5. SEEITEMS 5.1 5.1.1 5.1.2 5.1.3 5.2 5.2.1 5.2.2 5.2.3 5.2.4 5.2.5 5.2.6 5.2.7 5.3 5.3.1 5.3.1.1 5.3.1.2 5.3.1.3 5.3.1
28、4 5.3.1.5 5.3.1.6 5.3.2 5.3.2.1 5.3.2.2 5.3.2.3 5.3.2.4 5.3.2.5 5.3.2.6 5.3.3 5.3.3.1 5.3.3.2 5.3.3.3 MIL-HDBK- 1467 CONTENTS (contd) Item changes Item acceptance guidelines Establishment of COE item supportability with the designated life cycle support organization Identification of other addition
29、s to the designated COE Supportability and compatibility requirements Contracting approach Initial step Next step Final step DSEE Plan Contracting activity-hished resources DSEE identification DSEE contents DSEE operation Differences between the DSEE and the designated LCSEE Item source identificati
30、on Limited and restricted rights DSEE implementation Commercially available items Integration guidelines Documentation guidelines Quality assessment guidelines Configuration management guidelines Item changes Item acceptance guidelines Privately developed items Integration guidelines Documentation g
31、uidelines Quality assessment guidelines Configuration management guidelines Item changes Item acceptance guidelines Contracting activity-designated items Integration guidelines Documentation guidelines Quality assessment guidelines Pane 11 11 11 11 11 12 12 12 12 12 12 13 13 13 13 14 14 14 14 15 15
32、15 15 15 16 16 16 16 17 17 17 17 17 18 18 18 18 vi Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-HDBK-LYb7 m 9999970 025bL90 23Y = Paramaph 5.3.3.4 5.3.3.5 5.3.3 -6 5.3.4 5.3.4.1 5.3.4.2 5.3.4.3 5.3.4.4 5.3.4.5 5.3.4.6 5.4 5.4.1 5.4.2 5.4.3 5.5
33、 6. NOTES 6.1 6.2 6.3 6.4 , 6.5 MIL-HDBK-1467 CONTENTS (Contd) Pane Configuration management guidelines 18 Item changes 18 Item acceptance guidelines 18 Developmental items 18 Integration guidelines 19 Documentation guidelines 19 Quality assessment guidelines 19 Item changes 19 Item acceptance guide
34、lines 19 Establishment of item supportability with the designated life cycle support organization 19 Identification of other additions to the designated LCSEE 20 20 20 Configuration management guidelines 19 Description of the designated LCSEE operation Supportability and compatibility requirements 2
35、0 Item transition to the designated LCSEE 22 Intended use 22 Suppression data 22 Cross-reference of classifications and substitutability data 22 Subject term (key word) listing 22 Identification of changes 22 CONCLUDING MATERIAL 23 APPENDIX A APPENDIX B APPENDIX C Al B1 c1 Provided by IHSNot for Res
36、aleNo reproduction or networking permitted without license from IHS-,-,- MIL-HDBK-1467 9999970 0256191 170 MIL-HDBK-1467 PAGE LEFT BLANK INTENTIONALLY . vu Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,- MIL-HDBK-14b7 m 9999970 0256192 007 m MIL-HDB
37、K-1467 1. SCOPE 1.1 Pumose. This handbook establishes guidelines for the acquisition of new COE items and ensuring the compatibility of these items with the designated COE. Further, it establishes guidelines for the contracting activitys use in Contracting for SEE items, to ensure the compatibility
38、of each SEE item with the contracting activitys designated Life Cycle Software Engineering Environment (LCSEE), and to ensure the existence of a complete life cycle support capability for application software that is to be delivered under the contract. This is for guidance only. This handbook cannot
39、 be cited as a requirement. If it is, the contractor does not have to comply. 1.2 Amlication. 1.2.1 COE items. These guidelines should be applied to all contracts that include the acquisition of items destined for integration into a specific COE. For this type of acquisition, Section 4 of this handb
40、ook applies. This handbook is intended to support the contracting activity development of procurement packages that will contain delivery requirements for items that are to be integrated into a particular COE. The prime contractor should be made responsible for invoking all contractual requirements
41、Stemming from this handbooks use on any and all subcontractors, vendors, or other sources involved in the production of COE items to be delivered under the requirements of the contract 1.2.2 SEE items. These guidelines should be applied to all contracts that include the acquisition of new items need
42、ed for the life cycle support of application software to be delivered under the contract, Section 5 of this handbook should be used for this type of acquisition, however some or all of Section 4 may also be applicable. This handbook is intended to support contracting activity preparation of statemen
43、ts of work that must satis particular engineering and support requirements for a contracted application software effort. The prime contractor should be made responsible for invoking all Contractual requirements stemming from this handbooks use on any and all subcontractors, vendors, or other sources
44、 involved in the development of items to be delivered under the requirements of the contract. 1.3 TyDe of contract. In situations where the items being acquired are not the subject of a specific contract but the subject of a task or delivery order under a larger contract, the word “contract“ as used
45、 in this handbook should be interpreted to mean “task or delivery order.“ 1.4 Non-contractuai use. This handbook can be used by any organization obtaining an item from another Organization (in-house). For this usage, the term “contractor“ refers to the organization producing the item. The term “cont
46、racting activity“ refers to the obtaining organization and the term “contract“ refers to the agreement between the organizations. 1 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,- MIL-HDBK-3467 m 9999970 0256393 T43 m MIL-HDBK- 1467 2. APPLICABLE DO
47、CUMENTS 2.1 This section is not applicable to this handbook. 2 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,- MIL-HDBK-3467 9999970 0256394 98T MIL-HDBK- 1467 3. DEFINITIONS The definitions provided in this section describe the terms as they are us
48、ed in this handbook. 3.1 Common oDerating environment (COE). A repository or repositories (some perhaps virtual) that contains the ingredients fiom which an organization develops new software. Some examples of COE items include a SEE, reusable software and process assets, selected COTS packages, and
49、 cross-domain assets. 3.2 Contracting activiw. That office, with contract and project directive administrative authority, which has prime responsibility for and authority over the contracted effort. 3.3 Contracting activitv-designated resources. Resources that the contracting activity identifies to the contractor to be inc
