• There are no items in your cart
We noticed you’re not on the correct regional site. Switch to our AMERICAS site for the best experience.
Dismiss alert

DOD-STD-2167 Revision A:1988

Superseded
Superseded

A superseded Standard is one, which is fully replaced by another Standard, which is a new edition of the same Standard.

View Superseded by
superseded

A superseded Standard is one, which is fully replaced by another Standard, which is a new edition of the same Standard.

DEFENSE SYSTEM SOFTWARE DEVELOPMENT
Available format(s)

PDF

Superseded date

05-12-1994

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.

Committee
AREA MCCR
DevelopmentNote
A NOTICE 1 - Notice of Cancellation/Superseded by MIL STD 498 (04/2003)
DocumentType
Standard
Pages
63
PublisherName
US Military Specs/Standards/Handbooks
Status
Superseded
SupersededBy
Supersedes

DOD-STD-2168 Base Document:1988 DEFENSE SYSTEM SOFTWARE QUALITY PROGRAM
MIL-HDBK-287 Base Document:1989 A TAILORING GUIDE FOR DOD-STD-2167, DEFENSE SYSTEM SOFTWARE DEVELOPMENT
MIL-STD-1662 Revision C:1992 ORDNANCE ALTERATION (ORDALT) INSTRUCTIONS, PREPARATION OF
EIA CMB 6-1 : 2014 STABILIZED CONFIGURATION AND DATA MANAGEMENT REFERENCES
DEFSTAN 00-69(PT2)/1(1998) : 1998 AIRCRAFT/STORE ELECTRICAL INTERCONNECTION SYSTEM - PART 2: DESIGN PRINCIPLES AND PRACTICES FOR, AND GUIDE TO, THE IMPLEMENTATION OF THE AIRCRAFT/STORE ELECTRICAL INTERCONNECTION SYSTEM
MIL-STD-973 Base Document:1992 CONFIGURATION MANAGEMENT
MIL-HDBK-2097 Revision A:1997 ACQUISITION OF SUPPORT EQUIPMENT AND ASSOCIATED INTEGRATED LOGISTICS SUPPORT
MIL-HDBK-782 Base Document:1988 SOFTWARE SUPPORT ENVIRONMENT ACQUISITION
MIL-S-87241 Base Document:1985 SIMULATOR, FLIGHT (REQUEST FOR ISSUE OTHER THAN DOD MUST BE SENT VIA ASD/ENES WRIGHT PATTERSON AFB OH 45433-6503
MIL C 85629 : A (1) CONTROL MONITOR SET GUIDED WEAPON, AN/AWW-13
MIL-Q-87270 Base Document:1992 QUALITY ASSURANCE PROGRAM - INTERACTIVE ELECTRONIC TECHNICAL MANUALS & ASSOCIATED TECHNICAL INFORMATION, REQUIREMENTS FOR
MIL-STD-1456 Revision A:1989 CONTRACTOR CONFIGURATION MANAGEMENT PLANS
NASA GB 8719.13 : 0 NASA SOFTWARE SAFETY GUIDEBOOK
SAE AS 9006 : 2013 DELIVERABLE AEROSPACE SOFTWARE SUPPLEMENT FOR AS9100A - QUALITY MANAGEMENT SYSTEMS - AEROSPACE - REQUIREMENTS FOR SOFTWARE
SAE J 2214 : 1997 VEHICLE ELECTRONIC PROGRAMMING STATIONS (VEPS) SYSTEM SPECIFICATION FOR PROGRAMMING COMPONENTS AT OEM ASSEMBLY PLANTS
SAE ARP 4904 : 2014 CAPABILITY GUIDELINES FOR COMPUTER CONTROLLED TEST EQUIPMENT FOR HYDRAULIC COMPONENTS
MIL-HDBK-272 Revision A:1993 NUCLEAR WEAPONS SYSTEMS, SAFETY DESIGN AND EVALUATION CRITERIA FOR
MIL-HDBK-761 Revision A:1985 HUMAN ENGINEERING GUIDELINES FOR MANAGEMENT INFORMATION SYSTEMS - METRIC
MIL M 49503 : A MANUALS, TECHNICAL: GENERAL STYLE AND FORMAT, TEST PROGRAM SETS FOR AUTOMATIC TEST EQUIPMENT
MIL-STD-2039 Base Document:1992 FIELD CHANGES & FIELD CHANGE KITS, PREPARATION OF
MIL-HDBK-286 Base Document:1990 A GUIDE FOR DOD-STD-2168 DEFENSE SYSTEM SOFTWARE QUALITY PROGRAM
MIL-D-18300 Revision H:1993 DESIGN EXAMINATIONS, ENGINEERING AVIONIC SYSTEMS/EQUIPMENT GENERAL REQUIREMENTS FOR
MIL-D-8708 Revision C:1991 DEMONSTRATION REQUIREMENTS FOR AIRPLANES
NASA STD 2100 91 : 0 NASA SOFTWARE DOCUMENTATION STANDARD
MIL T 31000 : 0 TECHNICAL DATA PACKAGES - GENERAL SPECIFICATION FOR
MIL-HDBK-284-1 Base Document:1992 INTERACTIVE COURSEWARE (ICW) FOR MILITARY TRAINING, MANAGERS GUIDE FOR DEVELOPMENT, ACQUISITION & MANAGEMENT OF

MIL-STD-481 Revision B:1988 CONFIGURATION CONTROL, ENGINEERING CHANGES, DEVIATIONS AND WAIVERS (SHORT FORM)
MIL-STD-499 Revision A:1974 ENGINEERING MANAGEMENT
MIL-STD-1521 Revision B:1985 TECHNICAL REVIEWS AND AUDITS FOR SYSTEMS, EQUIPMENTS, AND COMPUTER SOFTWARE
MIL-STD-490 Revision A:1985 SPECIFICATION PRACTICES
DOD STD 480 : A CONFIGURATION CONTROL - ENGINEERING CHANGES, DEVIATIONS AND WAIVERS

View more information
£16.70
Excluding VAT

Access your standards online with a subscription

Features

  • Simple online access to standards, technical information and regulations.

  • Critical updates of standards and customisable alerts and notifications.

  • Multi-user online standards collection: secure, flexible and cost effective.