CAP670 / SW01

What is CAP670 / SW01?

CAP670/SW01 assumes that software safety requirements have been derived from a full risk and safety analysis of the system. This will have established the overall safety requirements that have been refined and allocated in the design to software. This is a commonplace system safety process and is described in standards and guidelines such as IEC 61508 Part 1, ARP4754, and Def Stan 00-55/56.

The document does not prescribe how the assurance evidence is to be produced or its adequacy argued. International software assurance standards and guidelines, such as IEC 61508 Part 3, RTCA DO-178B / EUROCAE ED12-B, and Def Stan 00-55/56, when used in conjunction with this document may provide an effective way to produce timely and technically valid evidence to satisfy these assurance objectives.

RTCA DO-178B / EUROCAE ED-12 provides guidelines for the production of software for airborne systems and equipment that performs its intended function with a level of confidence in safety that complies with airworthiness requirements. The guidelines are in the form of:

• Objectives of software life cycle processes
• Description of activities and design considerations for achieving these objectives
• Description of the evidence that indicate that the objectives have been satisfied

The document discusses those aspects of airworthiness certification that pertain to the production of software for airborne systems and equipment used on aircraft or engines.

CAP670 / SW01 Assurance Evidence Levels:

Where DO-178B discusses criticality in terms of safety levels, CAP670/SW01 defines Assurance Evidence Levels. These are based on the ESARR 4 severity classification scheme as:

Note that the classification is the same as ESARR 4, but the level numbers are in the reverse order to that standard.