1.5 Satisfying the objectives of Part 2 of SW 01 will satisfy the objectives of Article 3 of EU Regulation 482/2008. Part 3 of SW 01 gives additional guidance on how the objectives may be met.
1.6 Means of compliance with Article 3 of EU Regulation No 482/2008 that have been agreed between Service Providers and SRG are made public via the CAA website at the following address:
www.caa.co.uk/publications
1.7 Compliance with Article 4 of EU Regulation No 482/2008 and its associated annexes can be achieved by integrating processes that satisfy CAP 670 SW 01 into an organisation's overall risk assessment and mitigation process. However, to achieve full compliance with EU Regulation No 482/2008 through the use of SW 01, it is also necessary to introduce processes that mandate the guidance in Part 3 and Appendix A of SW 01. This is required to address specific activities and criteria mandated by the Regulation.
2 Scope
2.1 This document applies to any ATS system where the Software is needed to fulfil a system safety requirement.
2.2 The objectives in this document only apply to those software requirements that have an impact on safety. These are called software safety requirements in this document.
2.3 This document does not apply to electronic items such as application specific integrated circuits, programmable gate arrays, solid-state logic controllers or software requirements that can be demonstrated not to affect safety.
2.4 The guidance in Part 3 of this document (CAP 670 Part B SW 01) primarily applies to software outside of the scope of Article 5 of EU Regulation 482/2008, i.e. bespoke software. However, it can also be used for additional guidance in circumstances where published guidance does not fully address the needs of software within the scope of Article 5 of EU Regulation 482/2008, e.g. COTS software and changes to legacy software. Means of compliance for software identified in Article 5 of EU Regulation 482/2008 will be made available via the CAA website at the following address:
www.caa.co.uk/publications
2.5 This document 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 and ARP4754.
2.6 This 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 and RTCA DO178-B/EUROCAE ED12-B, when used in conjunction with this document may provide an effective way to produce timely and technically valid evidence that can then be used to argue that the SW 01 assurance objectives are satisfied.
中國航空網 m.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：CAP 670 Air Traffic Services Safety Requirements 1(68)
