standard

MIL-STD-1456A - Configuration Management Plan

Body

MIL-STD-1456A
11 SEPTEMBER 1989
---
SUPERSEDING
MIL-STD-1456
25 January 1972

Defined by
Defining documents
Document title Document identifier Document date File size File
MIL-STD-1456A - Configuration Management Plan MIL-STD-1456A 1.01 MB   DOWNLOAD!
Document title Sort descending Document identifier Document date File size File
MIL-STD-1456A - Configuration Management Plan MIL-STD-1456A 1989-09-11 1.01 MB   DOWNLOAD!

MIL-STD-490B - PROGRAM-UNIQUE SPECIFICATIONS, PREPARATION OF

Body

MIL-STD-490B
7 DECEMBER 1992
------------------------------
SUPERSEDING
MIL-STD-490A
4 JUNE 1985
MIL-S-83490
30 SEPTEMBER 1968

Defined by
Defining documents
Document title Document identifier Document date File size File
MIL-STD-490B - PROGRAM-UNIQUE SPECIFICATIONS, PREPARATION OF MIL-STD-490B 742 KB   DOWNLOAD!
Document title Sort descending Document identifier Document date File size File
MIL-STD-490B - PROGRAM-UNIQUE SPECIFICATIONS, PREPARATION OF MIL-STD-490B 1992-12-07 742 KB   DOWNLOAD!
MIL-STD-490B - PROGRAM-UNIQUE SPECIFICATIONS, PREPARATION OF [as PDF scan] MIL-STD-490B 1992-12-07 5.57 MB   DOWNLOAD!

MIL-STD-490A - SPECIFICATION PRACTICES

Body

4 JUNE 1985

SUPERSEDING
MIL-STD-490
30 OCT 1968

Defined by
Defining documents
Document title Document identifier Document date File size File
MIL-STD-490A - Specification Practices MIL-STD-490A 3.62 MB   DOWNLOAD!
Document title Sort descending Document identifier Document date File size File
MIL-STD-490A - Specification Practices MIL-STD-490A 1985-06-04 3.62 MB   DOWNLOAD!
MIL-STD-490A (NOTICE 1), MILITARY STANDARD, SPECIFICATION PRACTICES MIL-STD-490A (NOTICE 1) 1995-08-31 none

MIL-STD-483 (USAF) - Configuration Management Practices For Systems

Body

31 DEC 1970

Defined by
Defining documents
Document title Document identifier Document date File size File
MIL-STD-483 (USAF) - Configuration Management Practices For Systems MIL-STD-483 (USAF) none
Document title Sort descending Document identifier Document date File size File
MIL-STD-483 (USAF) - Configuration Management Practices For Systems MIL-STD-483 (USAF) 1970-12-31 none

[DUPLICATE] Standard: MIL-STD-2168 - Defense System Software Quality Program

The terms "DOD-STD-2167" and "DOD-STD-2168" (often mistakenly referred to as "MIL-STD-2167" and "MIL-STD-2168" respectively) are the official specification numbers for superseded U.S. DoD military standards describing documents and procedures required for developing military computer systems. (These specifications were superseded by MIL-STD-498 in 1994). Specifically:

* DOD-STD-2167 described the necessary project documentation to be delivered when developing a computer software system using the waterfall model

* DOD-STD-2168 was the DoD's software quality assurance standard, titled "Defense System Software Quality Program".

On December 5th, 1994, the standards DOD-STD-2167A and DOD-STD-2168 were superseded by MIL-STD-498, and that document merged DOD-STD-2167A, DOD-STD-7935A, and DOD-STD-2168 into a single document, and incorporated changes to address vendor criticisms.

DoD-STD-2167A - Defense Systems Software Development

Defined by
Defining documents
Document title Document identifier Document date File size File
DoD-STD-2167A - Defense Systems Software Development DOD-STD-2167A 131 KB   DOWNLOAD!
Document title Sort descending Document identifier Document date File size File
DoD-STD-2167A - Defense Systems Software Development DOD-STD-2167A 1988-02-29 131 KB   DOWNLOAD!
DoD-STD-2167A - Defense Systems Software Development [as PDF scan] DOD-STD-2167A 1988-02-29 1.88 MB   DOWNLOAD!

DOD-STD-2167A (Department of Defense Standard 2167A), titled "Defense Systems Software Development", was a United States defense standard, published on February 29, 1988, which updated the less well known DOD-STD-2167 published 4 June 1985. This document established "uniform requirements for the software development that are applicable throughout the system life cycle." It was designed to be used with MIL-STD-2168, "Defense System Software Quality Program".

On December 5th, 1994 it was superseded by MIL-STD-498, which merged DOD-STD-2167A, DOD-STD-7935A, and DOD-STD-2168 into a single document, and addressed some vendor criticisms.

US 12207 (1996+)

Body

From MIL-STD-498, J-STD-016, and the U.S. Commercial Standard:

U.S. Commercial Standard (US 12207-1996)

In August 1995, ISO/IEC 12207 was released as an approved international standard. The JISWG is adapting 12207 for United States use to include the technical content found in J-STD-016. The working group consists of representatives from commercial and government organizations.
[...]
US 12207-1996 will consist of ISO/IEC 12207 with additional materials.
[...]
The scope of ISO/IEC 12207 is broader than the scope of J-STD-016. J-STD-016-1995 focuses on the development process while ISO/IEC 12207 includes the acquisition, supply, operation, and maintenance processes. Consequently, the additional materials in US 12207-1996 focus on those areas where the two standards overlap, i.e., development and the supporting processes such as documentation, quality assurance, configuration management, and joint reviews.

From Contracting for Quality EEE493 2001:

IEEE/EIA 12207 (June 1998)

- Also called “US 12207” for historical reasons

- Represents a “tactical” implementation of ISO 12207

- Focus is on the organizational level rather than the project level

MIL-STD-498 - Software development and documentation

Body

List of Data Item Descriptions (DIDs):

Defined by
Defining documents
Document title Document identifier Document date File size File
MIL-STD-498 - Software development and documentation (PDF) MIL-STD-498 667.77 KB   DOWNLOAD!

MIL-STD-498 (Military-Standard-498) was a United States military standard whose purpose was to "establish uniform requirements for software development and documentation." It was released Nov. 8, 1994, and replaced DOD-STD-2167A, DOD-STD-7935A, and DOD-STD-1703. It was meant as an interim standard, to be in effect for about two years until a commercial standard was developed.

,

[...]
it was cancelled on May 27, 1998 and replaced by J-STD-016 and IEEE 12207.
[...]

,

A key component of the standard is 22 Data Item Descriptions (DIDs). Each DID generically describes the required content of a data item, a "document" that describes the software or some aspect of the software life-cycle. These documents could take many forms, from source code, to installation scripts, to various electronic and paper reports, and the contracting party (e.g., the government) is encouraged to specify acceptable formats. The set of data item descriptions, once tailored for a specific contract, then become Contract Data Requirement List items ("CDRLs") that represent the deliverable items of a contract. Depending on the nature of the project, not all data items may be required.

The terms "DOD-STD-2167" and "DOD-STD-2168" (often mistakenly referred to as "MIL-STD-2167" and "MIL-STD-2168" respectively) are the official specification numbers for superseded U.S. DoD military standards describing documents and procedures required for developing military computer systems. (These specifications were superseded by MIL-STD-498 in 1994). Specifically:

* DOD-STD-2167 described the necessary project documentation to be delivered when developing a computer software system using the waterfall model

* DOD-STD-2168 was the DoD's software quality assurance standard, titled "Defense System Software Quality Program".

On December 5th, 1994, the standards DOD-STD-2167A and DOD-STD-2168 were superseded by MIL-STD-498, and that document merged DOD-STD-2167A, DOD-STD-7935A, and DOD-STD-2168 into a single document, and incorporated changes to address vendor criticisms.

MIL-STD-1478 - Task Performance Analysis

Defined by
Defining documents
Document title Document identifier Document date File size File
MIL-STD-1478 - Task Performance Analysis MIL-STD-1478 none
MIL-STD-1478 (NOTICE 1) - Task Performance Analysis MIL-STD-1478 (NOTICE1) none
Document title Sort descending Document identifier Document date File size File
MIL-STD-1478 - Task Performance Analysis MIL-STD-1478 1991-05-13 none
MIL-STD-1478 (NOTICE 1) - Task Performance Analysis MIL-STD-1478 (NOTICE1) 1995-12-05 none

IDEF9 Business Constraint Discovery

IDEF9 or Integrated Definition for Business Constraint Discovery is designed to assist in the discovery and analysis of constraints in a business system. A primary motivation driving the development of IDEF9 was an acknowledgment that the collection of constraints that forge an enterprise system is generally poorly defined. The knowledge of what constraints exist and how those constraints interact is incomplete, disjoint, distributed, and often completely unknown. This situation is not necessarily alarming. Just as living organisms do not need to be aware of the genetic or autonomous constraints that govern certain behaviors, organizations can (and most do) perform well without explicit knowledge of the glue that structures the system. However, if the desire exists to modify the business in a predictable manner, the knowledge of these constraints is as critical as knowledge of genetics is to the genetic engineer. concepts in terms of familiar, concrete objects and experiences.

ISO/IEC 12207 - Software Lifecycle Processes

Defined by
Document title Sort descending Document identifier Document date File size File
ISO/IEC 12207 SW LC Processes - 12207 Description UNKNOWN 77.63 KB   DOWNLOAD!
ISO/IEC 12207 SW LC Processes - 12207 Tutorial 1999-04-26 793.5 KB   DOWNLOAD!

ISO 12207 is an ISO standard for software lifecycle processes. It aims to be 'the' standard that defines all the tasks required for developing and maintaining software.

The ISO 12207 standard establishes a process of lifecycle for software, including processes and activities applied during the acquisition and configuration of the services of the system. Each Process has a set of outcomes associated with it. There are 23 Processes, 95 Activities, 325 Tasks and 224 Outcomes (the new "ISO/IEC 12207:2008 Systems and software engineering -- Software life cycle processes" defines 43 system and software processes).

The standard has the main objective of supplying a common structure so that the buyers, suppliers, developers, maintainers, operators, managers and technicians involved with the software development use a common language. This common language is established in the form of well defined processes. The structure of the standard was intended to be conceived in a flexible, modular way so as to be adaptable to the necessities of whoever uses it. The standard is based on two basic principles: modularity and responsibility. Modularity means processes with minimum coupling and maximum cohesion. Responsibility means to establish a responsibility for each process, facilitating the application of the standard in projects where many people can be legally involved.

The set of processes, activities and tasks can be adapted according to the software project. These processes are classified in three types: basic, for support and organizational. The support and organizational processes must exist independently of the organization and the project being executed. The basic processes are instantiated according to the situation.

A Guide to the Project Management Body of Knowledge (PMBOK Guide)

Body

From Wikipedia: A Guide to the Project Management Body of Knowledge:

A Guide to the Project Management Body of Knowledge (PMBOK Guide) is a project management guide, and an internationally recognized standard, that provides the fundamentals of project management as they apply to a wide range of projects, including construction, software, engineering, automotive, etc.

A Guide to the Project Management Body of Knowledge (PMBOK Guide) was first published by the Project Management Institute (PMI) as a white paper in 1987 in an attempt to document and standardize generally accepted project management information and practices. The first edition was published in 1996 followed by the second edition in 2000.

In 2004 the PMBOK Guide - Third Edition was published with major changes from the first edition. The English-language PMBOK Guide - Fourth Edition was released on December 31, 2008.

BS EN ISO 9000:2000

Body

Replaces BS EN ISO 8402:1995.

Replaced by BS EN ISO 9000:2005

From ISO - ISO 9000 / ISO 14000 - Quality management principles:

This document introduces the eight quality management principles on which the quality management system standards of the ISO 9000:2000 and ISO 9000:2008 series are based. These principles can be used by senior management as a framework to guide their organizations towards improved performance. The principles are derived from the collective experience and knowledge of the international experts who participate in ISO Technical Committee ISO/TC 176, Quality management and quality assurance, which is responsible for developing and maintaining the ISO 9000 standards.

DOD-STD-2168 - Defense System Software Quality Program

Defined by
Defining documents
Document title Document identifier Document date File size File
DOD-STD-2168 - Defense System Software Quality Program DOD-STD-2168 42 KB   DOWNLOAD!
Document title Sort descending Document identifier Document date File size File
DOD-STD-2168 - Defense System Software Quality Program DOD-STD-2168 1988-04-29 42 KB   DOWNLOAD!
DOD-STD-2168 - Defense System Software Quality Program [as PDF] DOD-STD-2168 1988-04-29 27.97 KB   DOWNLOAD!

The terms "DOD-STD-2167" and "DOD-STD-2168" (often mistakenly referred to as "MIL-STD-2167" and "MIL-STD-2168" respectively) are the official specification numbers for superseded U.S. DoD military standards describing documents and procedures required for developing military computer systems. (These specifications were superseded by MIL-STD-498 in 1994). Specifically:

* DOD-STD-2167 described the necessary project documentation to be delivered when developing a computer software system using the waterfall model

* DOD-STD-2168 was the DoD's software quality assurance standard, titled "Defense System Software Quality Program".

On December 5th, 1994, the standards DOD-STD-2167A and DOD-STD-2168 were superseded by MIL-STD-498, and that document merged DOD-STD-2167A, DOD-STD-7935A, and DOD-STD-2168 into a single document, and incorporated changes to address vendor criticisms.

MIL-STD-499B - Systems Engineering

Body
The cover of the defining standards document states:

Superseding MIL-STD-499A 1 May 1974

However, as this standard was never officially approved and released it did not ever officially supersede: MIL-STD-499A - Engineering Management.

Defined by
Defining documents
Document title Document identifier Document date File size File
MIL-STD-499B Draft 940506 PDF MIL-STD-499B Draft 940506 410.53 KB   DOWNLOAD!
Document title Sort descending Document identifier Document date File size File
MIL-STD-499B Draft 910515 - Systems Engineering MIL-STD-499B Draft 910515 1991-05-15 1.71 MB   DOWNLOAD!
MIL-STD-499B Draft 920506 - For coordination review MIL-STD-499B Draft 920506 1992-05-06 3.67 MB   DOWNLOAD!
MIL-STD-499B Draft 930824 - Joint OSD / Services / Industry Working Group - 7 Sept 93 MIL-STD-499B Draft 930824 1993-08-24 3.5 MB   DOWNLOAD!
MIL-STD-499B Draft 940506 PDF MIL-STD-499B Draft 940506 1994-05-06 410.53 KB   DOWNLOAD!

EIA/IS-731: Systems Engineering Capability Model

Body

From SEI: CMMI Models FAQ:

EIA 731, the Systems Engineering Capability Model, is a source document for CMMI. A mapping that compares EIA 731 and CMMI v1.1 is available on the SEI Web site, including a mapping from CMMI v1.1 to EIA 731 at http://www.sei.cmu.edu/cmmi/casestudies/mappings/cmmimappings.cfm, from EIA 731 to CMMI v1.1 available at http://www.sei.cmu.edu/cmmi/casestudies/mappings/cmmimappings.cfm, and a document to help you interpret these mappings at http://www.sei.cmu.edu/cmmi/casestudies/mappings/cmmimappings.cfm. An article that discusses Transitioning from EIA/IS 731 to CMMI is also available at
https://theqalead.com/topics/what-happened-to-crosstalk-journal-of-defe…

ITAA EIA-731-1 was formerly EIA/IS 731.1.

ISO 9000

Body

From ISO 9000 essentials:

The ISO 9000 family of standards represents an international consensus on good quality management practices. It consists of standards and guidelines relating to quality management systems and related supporting standards.

ISO 9001:2008 is the standard that provides a set of standardized requirements for a quality management system, regardless of what the user organization does, its size, or whether it is in the private, or public sector. It is the only standard in the family against which organizations can be certified – although certification is not a compulsory requirement of the standard.

The other standards in the family cover specific aspects such as fundamentals and vocabulary, performance improvements, documentation, training, and financial and economic aspects.

From Wikipedia: ISO 9000:

ISO 9000 is a family of standards for quality management systems. ISO 9000 is maintained by ISO, the International Organization for Standardization and is administered by accreditation and certification bodies. The rules are updated, as the requirements motivate changes over time.

Some of the requirements in ISO 9001:2008 (which is one of the standards in the ISO 9000 family) include

* a set of procedures that cover all key processes in the business;
* monitoring processes to ensure they are effective;
* keeping adequate records;
* checking output for defects, with appropriate and corrective action where necessary;
* regularly reviewing individual processes and the quality system itself for effectiveness; and
* facilitating continual improvement

A company or organization that has been independently audited and certified to be in conformance with ISO 9001 may publicly state that it is "ISO 9001 certified" or "ISO 9001 registered". Certification to an ISO 9001 standard does not guarantee any quality of end products and services; rather, it certifies that formalized business processes are being applied.

Although the standards originated in manufacturing, they are now employed across several types of organizations. A "product", in ISO vocabulary, can mean a physical object, services, or software.

DOD-STD-2167 - Defense Systems Software Development

Defined by
Defining documents
Document title Document identifier Document date File size File
DOD-STD-2167 DOD-STD-2167 none
Document title Sort descending Document identifier Document date File size File
DOD-STD-2167 DOD-STD-2167 1985-06-04 none

DOD-STD-2167A (Department of Defense Standard 2167A), titled "Defense Systems Software Development", was a United States defense standard, published on February 29, 1988, which updated the less well known DOD-STD-2167 published 4 June 1985. This document established "uniform requirements for the software development that are applicable throughout the system life cycle." It was designed to be used with MIL-STD-2168, "Defense System Software Quality Program".

On December 5th, 1994 it was superseded by MIL-STD-498, which merged DOD-STD-2167A, DOD-STD-7935A, and DOD-STD-2168 into a single document, and addressed some vendor criticisms.

The terms "DOD-STD-2167" and "DOD-STD-2168" (often mistakenly referred to as "MIL-STD-2167" and "MIL-STD-2168" respectively) are the official specification numbers for superseded U.S. DoD military standards describing documents and procedures required for developing military computer systems. (These specifications were superseded by MIL-STD-498 in 1994). Specifically:

* DOD-STD-2167 described the necessary project documentation to be delivered when developing a computer software system using the waterfall model

* DOD-STD-2168 was the DoD's software quality assurance standard, titled "Defense System Software Quality Program".

On December 5th, 1994, the standards DOD-STD-2167A and DOD-STD-2168 were superseded by MIL-STD-498, and that document merged DOD-STD-2167A, DOD-STD-7935A, and DOD-STD-2168 into a single document, and incorporated changes to address vendor criticisms.

Model Driven Architecture (MDA)

Body

From Wikipedia: Model-driven architecture:

Model-driven architecture (MDA) is a software design approach for the development of software systems. It provides a set of guidelines for the structuring of specifications, which are expressed as models. Model-driven architecture is a kind of domain engineering, and supports model-driven engineering of software systems. It was launched by the Object Management Group (OMG) in 2001.

STEP (ISO 10303)

Body

From Wikipedia: ISO 10303:

ISO 10303 is an ISO standard for the computer-interpretable representation and exchange of product manufacturing information. Its official title is "Industrial automation systems and integration - Product data representation and exchange", known as "STEP" or "Standard for the Exchange of Product model data".

The International standard's objective is to provide a mechanism that is capable of describing product data throughout the life cycle of a product, independent from any particular system. The nature of this description makes it suitable not only for neutral file exchange, but also as a basis for implementing and sharing product databases and archiving.

Typically STEP can be used to exchange data between CAD, Computer-aided manufacturing, Computer-aided engineering, Product Data Management/EDM and other CAx systems. STEP is addressing product data from mechanical and electrical design, Geometric dimensioning and tolerancing, analysis and manufacturing, with additional information specific to various industries such as automotive, aerospace, building construction, ship, oil and gas, process plants and others.

From http://www.ap233.org/:

STEP, more formally known as ISO 10303, is an International Standard for the computer-interpretable representation and exchange of product data. The objective is to provide a mechanism that is capable of describing product data throughout the life cycle of a product, independent from any particular system. The nature of this description makes it suitable not only for neutral file exchange, but also as a basis for implementing and sharing product databases and archiving.

AP233 (Application Protocol 233) is the STEP Systems Engineering Project, one of several dozen projects each focusing on specific exchange and integration problems within a given domain. Examples of other STEP projects are:

* AP203 - 3D Designs of Mechanical Piece Parts and Assemblies (MCAD)

* AP209 - Structural Analysis and Related Design (Analysis)

* AP210 - Electronic Assembly, Interconnect, and Packaging Design (ECAD)

* AP212 - Electrotechnical Design and Installation (Cable Harnesses)

* AP238 - Application interpreted model for computer numeric controllers (Machining)

AP-233 (Application Protocol 233)

Body

From http://www.ap233.org/:

STEP's System Engineering Project

AP233 is a STEP-based data exchange standard targeted to support the needs of the systems engineering community, consistent with emerging standards in CAD, structural, electrical, engineering analysis and support domains. The AP233 Project is collaborating with the OMG SE DSIG team that is developing systems engineering extensions to Systems Modeling Language (OMG SysML™) and INCOSE (International Council on Systems Engineering), a systems engineering professional society.

Document title Sort descending Document identifier Document date File size File
AP-233 Overview 2001-09-13 1.61 MB   DOWNLOAD!
Support for Object-Orientation in AP-233 UNKNOWN 82.98 KB   DOWNLOAD!