Source documents summary


The following provides a brief summary of the referenced documentation of the PMS.

MIL-STD-499A or B

Engineering Management / Systems Engineering

The purpose of this document is to provide the project manager with:

Canceled by the US Government without replacement. A 499B was produced in draft but never achieved approval.  


MIL-STD-490A

Specification Practices

The purpose of this document is to define the requirements to prepare, revise, change specifications and associated documentation.  


DOD-STD-2167 and DOD-STD-2167A

Software Development

The purpose of these document where to establish the requirements for the development of Mission-critical computer system software. They establish a uniform software development process which is applicable throughout the system life cycle.

Canceled by the US Government without replacement (MIL-STD-498 for an interim period).  


MIL-STD-498

Software development and documentation

The purpose of this document is to establish uniform requirements for software development and documentation.

With its referenced DIDs, Guidebooks “Overview and Tailoring” and “Application and Reference” will form the basis of an implementation of ISO/IEC 12207 and ISO/IEC 15288.

 

 

 


MIL-STD-483A

Configuration Management Practices for Systems, Computer Programs, and Equipment.

The purpose of this document is to define the configuration management practices which are to be selectively applied, as required, throughout the life cycle of any configuration item.

Canceled by the US Government replaced by MIL-STD-973.  


MIL-STD-973

Configuration Management

The purpose of this document is to define the configuration management requirements that are to be selectively applied, as required, throughout the life cycle of any configuration item.

Canceled by the US Government without replacement.  


STANAG 4159

Configuration Management

The purpose of this document is to define the configuration management requirements which are to be selectively applied, as required, throughout the life cycle of any configuration item for NATO projects.

Still applicable.  


DEF STAN 05-67/1

Guide to Quality Assurance in Design

This document provides guidance on methods and procedures covering a number of techniques which form part of, or are closely related to, quality assurance in design  


DEF STAN 00-16/1

Guide to the achievement of Quality in Software

The purpose of this document is to provide guidance on the methods and procedures necessary to establish confidence in the quality of Software for Operational Defence Computer applications.  


DEF STAN 05-91

Quality System requirements for design/development, production, installation and servicing.

This document specifies quality requirements for a contractors design/development, production, installation and servicing system.  


ISO/IEC 12207

Information technology - Software life cycle processes.

This document provides a framework that can be used by software practitioners to "speak the same language" to create and manage software.  


ISO/IEC 15288

 - System life cycle processes.

This document provides a framework that can be used by system engineering management practitioners to "speak the same language" to create and manage technical system.  

DO-178B / ED-12B

Software Considerations in Airborne Systems and Equipment Certification

The purpose of this document is to provide guide-lines for the production of software for airborne systems and equipment that perform its intended function with a level of confidence in safety that complies with airworthiness requirements.
These guide-lines are in the form of:


ISO 9001

Quality systems - model for quality assurance in design, development, production, installation, and servicing.

This document specifies requirements aimed primarily at achieving customer satisfaction by preventing non-conformity at all stages from design through to servicing.  


DEF STAN 05-28/1

Guide to the preparation of specifications

The purpose of this document is to specify requirements for the specifications and associated documentation necessary to design complex technical systems.  


DOD-STD-2168

Software Quality Program

The purpose of this document is to establish a 'Software Quality Program Plan' which basically demands phase independent audits of the processes involved in the development of software.
Historical note: This task was integrated within the 'Software Quality Evaluation Plan' part of DOD-STD-2167 and was a complementary with DOD-STD-2167

It is unclear what will replace it.  


DEF STAN 05-10

Drawing Procedure

The purpose of this document is to define the requirements for engineering drawings.  


MIL-STD-680

Standardization Program requirements for Acquisitions

The purpose of this document is to establish requirements for planning and executing standardization programs.  


MIL-STD-810

Environmental Test Methods and Engineering Guide-lines

The purpose of this document is to provide guide-lines for conducting engineering tasks to tailor environmental tests to end-items, equipment applications and Test methods for determining the effects of natural and induced environments on equipment.  


MIL-HDBK-245

Preparation of Statement of Work

The purpose of this document is to aid in the preparation of an effective SOW 


DEF STAN 00-970

Design and Airworthiness requirements for Service Aircraft

The purpose of this document is:


DEF STAN 05-123

Technical Procedures for the Procurement of Aircraft and associated equipment

The purpose of this document is to provide the technical procedure requirements for the design, development, and testing of aircraft and associated equipment.


Rest

Under construction. 


 

The total number of visitors to this site since the 15th of March 1998


LE FastCounter

 

Back to Home page MANAGING STANDARDS Home page

Please send any beneficial comments or identification of errors using the following form to: kenr@wysywig.airtime.co.uk

Copyright © by Ken Rigby 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003