Software

For newly developed software, the Contractor / Supplier should be required to submit a Software Quality Assurance Plan complying with IEEE 730 or equivalent. This plan, and containing, as a minimum, the following documentation requirements:
a. Software Requirements Specification
b. Software Design Description
c. Software Verification and Validation Plan
d. Software Verification and Validation Report
e. User Documentation

The source code is normally written in a high-level language such as C. Generally, all source code, properly documented, is placed in an approved third-party escrow when the last vehicle exits its warranty period. The Software Design Description, in (b) above, should be specified to comply with IEEE 1016 or equivalent.

Standard:	IEEE 730 - Standard for Software Quality Assurance Plans
Purpose:	This standard provides uniform, minimum acceptable requirements for preparation and content of software quality assurance plans. This standard applies to the development and maintenance of critical software. For noncritical software, or for software already developed, a subset of the requirements of this standard may be applied.
Criteria:	Specify compliance with standard
Usage:	Shall submit a Software Quality Assurance Plan complying with IEEE 730

Standard:	IEEE 1016 - Recommended Practice for Software Design Descriptions
Purpose:	This recommended practice for describing software designs, specifies the necessary information content, and recommended organization for a software design description (SDD). The SDD is a representation or model of a software system to be created. The model will provide the precise design information needed for planning, analysis, and implementation of the software system.
Criteria:	Specify compliance with standard
Usage:	Shall submit a Software Design Description complying with IEEE 1016