Treffer: Space and Missile Systems Center Standard: Software Development

The purpose of this standard is to establish uniform requirements for software development activities for mission critical systems. This standard applies to the development of mission critical systems that contain software (such as hardware-software systems), software-only systems, and stand-alone software products. This standard can be applied to contractors or acquirer in-house agencies performing software development. Within this standard, the term acquirer is used for the organization requiring the technical effort (see Section 3.1); the term developer is used for the organization(s) performing the technical effort (see Section 3.1); the term contract is used for the agreement between these parties (see Section 3.1); the term Statement of Work (SOW) is used for the list of tasks to be performed by the developer; and the term Contract Data Requirements List (CDRL) is used for the list of deliverable products. General Requirements 1. This standard shall apply to all software team members. Note: The prime contractor is considered a software team member (see Section 3). 2. This standard shall apply to all categories of software defined in Section 1.2.5.6 that are within the scope of the contract. Note: This standard applies to software included in the categories of software whether or not the software is identified as a software item. 3. This standard shall apply to software installed in firmware devices. Note 1: This standard does not apply to the hardware element of firmware. Note 2: For more detailed requirements for Application-Specific Integrated Circuits (ASICs) and Field-Programmable Gate Arrays (FPGAs), see (Sather 2010) and (Dixon 2006). ; Supersedes SMC-S-012 2008. This revised SMC standard comprises the text of The Aerospace Corporation report number TR-RS-2015-00012, entitled Software Development Standard for Mission Critical Systems. The major changes in this release are documented in the Change Log contained in this document.