BS EN 9115:2013

This standard BS EN 9115:2013 Quality Management Systems. Requirements for Aviation, Space and Defense Organizations. Deliverable Software (Supplement to EN 9100) is classified in these ICS categories:

• 35.080 Software
• 03.120.10 Quality management and quality assurance
• 49.020 Aircraft and space vehicles in general
• 03.100.70 Management systems

1.1 General

The requirements of EN 9100 apply with the following clarification for software.

This document supplements the EN 9100 standard requirements for deliverable software and contains quality management system requirements for organizations that design, develop, and/or produce deliverable software for the aviation, space, and defense industry. This includes, as required, support software that is used in the development and maintenance of deliverable software. The deliverable software may be stand-alone, embedded, or loadable into a target computer.

Where the use of Hardware Description Language (HDL) or high order language is utilized as the design source of electronic hardware [e.g., Application Specific Integrated Circuit (ASIC), Programmable Logic Device (PLD)], the organization and customer shall agree on the extent of applicability of this supplement.

NOTE 1 For airborne electronic hardware guidance, see RTCA/DO-254 or EUROCAE ED-80; and for product realization requirements, see EN 9100.

Where Commercial-off-the-Shelf (COTS) or non-developmental software is integrated into a deliverable product, the organization and customer shall agree on the extent of applicability of this supplement.

For the purposes of this document, the terms “product” and “software product” are considered synonymous.

NOTE 2 This document is independent of the life cycle models (e.g., waterfall, spiral, evolutionary, incremental) or methodology (e.g., objected oriented design, unified modeling language, agile).

1.2 Application

The requirements of EN 9100 apply with the following clarification for software.

Exclusions to requirements in Clause 7 should only be considered after analysis of software attributes (e.g., size, safety, security, complexity, criticality, risk).