MILITARY STANDARD - Product Lifecycle Management

1 ,.. DoDSTD-2167. 4 JUNE 1%. SUPERSEDING. DOD-STD-1B7BA (NAVY. Z? OCTOBER 19S2. MILSD-1644B (TDl 2 MARCH 19S4. MILITARY STANDARD . defense SYSTEM. SOFIVVARE DEVELOPMENT. (. ~. i AMSC NO. N3 SOB AREA MCCR. DISTRIBUTION STATEMENT A. Approved forpublicreleaaa;. distribution isunlimitd'. DOD-STD-2167. department OF defense . Washington, DC 20301. defense System Software Development 1. This MILITARY STANDARD is approved $or use by all Departments and Agencies of the department of defense . 2. Beneficial comments (recommendations, additions, deletions). and any pertinent data which may be of use in improving this document should be addressed to: COMMANDER , Space and Naval Warfare Systems Command, ATTN: SPAWAR 8111, Washingtonr 20363-5100, by using the self-addressed Standardization Document Improvement Proposal (DD Form 1426) appearing at the end of this document or by letter. ). ii DOD-STD-2167. Foreword 1. This STANDARD contains requirements for the development of Mission-Critical COMpUter System SOftWare.))

2 It establishes a uniform software development process which is' applicable throughout the system life cycle . The software development process defines development activities which result in: (1) the generation different types and levels of software and documentation~f (2) the application of development tools, approaches, and methods, and (3) project planning and control. It incorporates practices which have been demonstrated to be cost-effective from a life cycle perspective, based on information gathered by the department of defense (DOD) and industry. 2. This STANDARD is intended to be dynamic and responsive to the rapidly evolving software technology field. As such, this STANDARD should be selectively applied and tailored to fit the unique characteristics of each software acquisition program. To ensure that the requirements in this STANDARD are appropriate and responsive to software acquisition needs, users of this STANDARD are encouraged to provide feedback to the Preparing Activity.

3 User experience in terms of benefits, pitfalls, and any other useful information encountered in applying this STANDARD will be most helpful. 3. Data Item Descriptions (DIDs~ applicable to this STANDARD are listed in Section 6. When used in conjunction with this STANDARD , these DIDs provide a set of concise and complete documents for recording and communicating information generated as a result of adherence to the requirements specified herein. iii/iv DOD-STD-2167. CONTENTS. Paragraph E!%&. 1. SCOPE ..,.. 1. Purpose .. 1. Applia' 1. Application to various types of 1. Non-applicability of this STANDARD .. 1. 1. Software developed by Government agencies .. 4. Tailoring of this STANDARD .. 4. 2. REFERENCED DOCUMENTS .. 5. Government documents .. 5. Specifications, standards , and handbooks .. 5. Other Government ,documents, drawings, and publications .. 5. Gther publications .. 5. Order of precedence .. 5. 3. DEFINITIONS.)

4 7. Alloca~ed Baseline.. 7. Authentication.. 7. Baseline .. 7. ::: Certification .. Computer data definit .. ;. Computer software (or software) ..:.. 7. Computer Software Component (CSC) .. 7. Computer Software Configuration Item (CSCI).. 7. Computer Software Documentation .. 7. Computer software quality (or software quality) .. 7. Configuration Identification .. 8. Configuration Item .. 8. Developmental Configuration .. 8. Firmware .. 8. Formal test .. Functional Baseline .. : Hardware Configuration Item (HWCI) .. 8. Informal test .. 8. Modular .. 8. Product Baseline .. 8. Software development library (SOL).. 8. Top-down .. 9. Unit .. 9. 4. GENERAL REQUIREMENTS .. 11. Software development cycle .. 11. Computer software organization .. 11. Software quality.. 15. Use of commercially available, reusable, and Government furnished software .. 15. v DOD-STD-2167. CONTENTS - Continued 1. Paragraph ~. Subcontractor control.

5 16. Non-deliverable software, firmware, and hardware..,. 16. Firmware .. 16. Development 16. Security .. 16. 4,10 Deliverable Data .. 16. Deviations and waivers.. 17. 5. DETAILED REQUIREMENTS .. Software Requirements Analysis .. Activities - Software Requirements Analysis .. Products - Software Requirements Analysis .. Formal Reviews - Software Requirements Analysis.. Baselines - Software Requirements Analysis .. Preliminary Design .. Activities - Preliminary Design .. Products - Preliminary Design .. Formal Reviews - Preliminary Design .. Developmental Configuration - Preliminary Design .. 27. Detailed Design .. 27. Activities-Detailed Design .. 27. Products -Detailed Design.. 30. Formal Reviews - Detailed Design .. 31 .). Developmental Configuration - Detailed Design .. 31. Codinci and Unit Testinq.. 31. A~tivities - Codin~ and Unit Testing .. 31. Products - Coding and Unit Testing .. 33. Developmental Configuration - Coding and Unit Testing.

6 33. Csc Integration and Testing.. 34. Activities - CSC Integration and Testing .. 34. Products - CSC Integration and Testing .. 35. Formal Reviews - CSC Integration and Testing .. 36. Developmental Confiquration - CSC Integration and Testing ..~.. CSCI Testing .. Activities -CSCI Testing.. Prod~~cts - CSCI Testing .. Audits -CSCI Testing.. Baselines -CSCI Test in.. Software .. Installation and checkout.. Configuration Management (CM).. 39. Activities - Configuration Management .. 39. Configuration identification .. 39. Configuration control.. 40. Configuration status accounting .. 41. ). vi DOD-STD-2167. CONTENTS - Continued Paragraph Products - Configuration Management .. 41. Audits - Configuration Management .. 42. Software Quality Evaluation.. 42. Activities - Software Quality Evaluation .. 42. Planning .. 42. Internal reviews .. 42. Evaluation Criteria .. 42. Internal reviews - all phases .. 43. Internal review - Software Requirements Analysis.

7 43. Internal review - Preliminary Design .. 43. Internal review - Detailed Design .. 44. Internal review - Coding and Unit Testing 45. Internal review - CSC Integration and Testing.. 46. Internal review - CSCI Testing .. 46. Formal reviews and audits.. 47. Acceptance inspection .. 47. , Installation and checkout .. 48. Evaluation of subcontractor products .. 48. Commercially available, reusable, and Government furnished software .. 48. Pi-eparation of quality records .. 48. Quality reporting .. 48. Corrective action system ..' 48. Quality cost data .. 49. Products - Software Quality Evaluation .. 49. Quality records .. 49. Quality reports .. 49. Certification .. 49. Independence .. 49. Software project planning and control .. 49. Activities - Software project planning and control .. 49. Sizing and timing assessments .. 49. Status and cost reporting .. 50. Test documentation control .. 50. Software development library (SDL).

8 50. Risk Management .. 50. 6. NOTES .. 51. Intended use .. 51. Data requirements list and cross reference .. 51. Subject term (keyword) listing .. 56. vii DOD-STD-2167. CONTENTS - Contintied FIGURES. 1 System development cycle within the system life cycle .. 2. Software development cycle .. 12. CSCI sample static structure .. 14. System support cycle within the system life cycle .. 62. 5 Sequence Construct .. 72. 6 IF-THEN-ELSE construct .. 72. DO-WdILE construct.. 73. ; DO-UNTIL construct .. 73. 9 CASE construct .. 10 Relationship among Management documents .. :: 11 Relationship among requirements documents .. 85. 12 Relationship among design documents .. 87. TABLES. Table I Typical data item requirements .. 82. APPENDIXES. Appendix A List of acronyms and abbreviations .. 59. B System life cycle .. 61. c Design and coding standards .. 71. D Guidelines for tailoring this STANDARD .. 77. viii DOD-STD-2167. 1.

9 SCOPE. lol,Purpose. This STANDARD establishes requirements to be applied during the development and acquisition of Mission-Critical Computer 'Systen (MCCSI software, as defined in DOD Directive This STANDARD ma: also be applied to non-14 CCS software development and acquisition. A lication. proc~i~O;;wT;~~;;;;OZe?;e ~~fW~l~~v~~~m~;~r~~~l~. occurs orieor more times during each of the system life cycle phases (Figure 1). Appendix B describes a typical system life cycle , the activities that take place during each iteration of software development, and the documentation which typically exists at the beginning of an iteration in any given system life cycle phase. The requirements of this STANDARD shall be applied to each iteration, as described below. The requirements of this STANDARD shall also be applied to the development of software for firmware devices as described in Application to various - ~ software. This STANDARD applies.)

10 To deliv=a~ software designated as Computer Software Configuration Items (CSCIS). This STANDARD , or portions thereof, such configuration Management , quality evaluation, and documen~~tion also applies to: a. Software developed and delivered as part of a system or a Hardware Configuration Item (HWCI) but not explicitly identified as a CSCI. b. Non-deliverable software used in the development and testing of deliverable software and hardware (such as design and test tools). c. Deliverable unmod fied commercially available and reusable software. d. Commercially ava lable software, Government furnished software (~FS), and reusable software that is modified and delivered as part of the system. The specific requirements of this STANDARD which apply to the above categories will be identified in the statement of work (sow). Non-applicability of ~ STANDARD . This STANDARD , or portions thereof, may =t apply to small applications which perform a fixed function that is not expected to change for the life of the system.