DOD-STD-2167 Revision A:1988

1 Scope
1.1 Purpose
1.2 Application
1.2.1 System development
1.2.2 Firmware
1.2.3 Software developed by Government agencies
1.2.4 Other applications
1.3 Tailoring of this standard
2 Referenced documents
2.1 Government documents
2.1.1 Specifications, standards, and handbooks
2.1.2 Other Government documents, drawings, and
        publications
2.2 Other publications
2.3 Order of precedence
3 Definitions
4 General requirements
4.1 Software development management
4.1.1 Software development process
4.1.2 Formal reviews/audits
4.1.3 Software development planning
4.1.4 Risk management
4.1.5 Security
4.1.6 Subcontractor management
4.1.7 Interface with the software IV&V agent
4.1.8 Software development library
4.1.9 Corrective action process
4.1.10 Problem/change report
4.2 Software engineering
4.2.1 Software development methods
4.2.2 Software engineering environment
4.2.3 Safety analysis
4.2.4 Non-developmental software
4.2.5 Computer software organization
4.2.6 Traceability of requirements to design
4.2.7 High order language
4.2.8 Design and coding standards
4.2.9 Software development files
4.2.10 Processing resource and reserve capacity
4.3 Formal qualification testing
4.3.1 Formal qualification test planning
4.3.2 Software test environment
4.3.3 Independence in FQT activities
4.3.4 Traceability of requirements to test cases
4.4 Software product evaluation
4.4.1 Independence in product evaluation activities
4.4.2 Final evaluations
4.4.3 Software evaluation records
4.4.4 Evaluation criteria
4.5 Software configuration management
4.5.1 Configuration identification
4.5.2 Configuration control
4.5.3 Configuration status accounting
4.5.4 Storage, handling, and delivery of project media
4.5.5 Engineering change proposals
4.6 Transitioning to software support
4.6.1 Regenerable and maintainable code
4.6.2 Transition planning
4.6.3 Software transition and continuing support
4.6.4 Software support and operational documentation
5 Detailed requirements
5.1 System requirements analysis/design
5.1.1 Software development management
5.1.2 Software engineering
5.1.3 Formal qualification testing
5.1.4 Software product evaluations
5.1.5 Configuration management
5.2 Software requirements analysis
5.2.1 Software development management
5.2.2 Software engineering
5.2.3 Formal qualification testing
5.2.4 Software product evaluations
5.2.5 Configuration management
5.3 Preliminary design
5.3.1 Software development management
5.3.2 Software engineering
5.3.3 Formal qualification testing
5.3.4 Software product evaluations
5.3.5 Configuration management
5.4 Detailed design
5.4.1 Software development management
5.4.2 Software engineering
5.4.3 Formal qualification testing
5.4.4 Software product evaluations
5.4.5 Configuration management
5.5 Coding and CSU testing
5.5.1 Software development management
5.5.2 Software engineering
5.5.3 Formal qualification testing
5.5.4 Software product evaluations
5.5.5 Configuration management
Figures
1 An example of system development reviews and audits
2 Deliverable products, reviews, audits, and baselines
3 Example of a system breakdown and CSCI
    organizational structure
4 Evaluation criteria for products of system
    requirements analysis/design
5 Evaluation criteria for products of Software
    Requirements Analysis
6 Evaluation criteria for products of Preliminary
    Design
7 Evaluation criteria for products of Detailed Design
8 Evaluation criteria for products of Coding and CSU
    Testing
9 Evaluation criteria for products of CSC Integration
    and Testing
10 Evaluation criteria for products of CSCI Testing
Appendixes
A List of acronyms and abbreviations
B Requirements for software coding standards
C Category and priority classifications for problem
    reporting
D Evaluation criteria

Describes requirements for acquisition, development, or support of software systems. Coverage includes: software development process; software development methods; software engineering environment; software configuration management; software transition and continuing support; software product evaluations; regenerable and maintainable code. Also contains detailed diagrams and appendixes.

This standard establishes requirements to be applied during the development and acquisition of Mission-Critical Computer System (MCCS) software, as defined in DOD Directive 5000.29.