1.1This standard practice intends to ensure the dependability of UAS software. Dependability includes both the safety and security aspects of the software.
1.2This practice will focus on the following areas: (a) Organizational controls (for example, management, training) in place during software development. (b) Use of the software in the system, including its architecture and contribution to overall system safety and security. (c) Metrics and design analysis related to assessing the code. (d) Techniques and tools related to code review. (e) Quality assurance. (f) Testing of the software.
1.3There is interest from industry and some parts of the CAAs to pursue an alternate means of compliance for software assurance for small UAS (sUAS).
1.4This practice is intended to support sUAS operations. It is assumed that the risk of sUAS will vary based on concept of operations, environment, and other variables. The fact that there are no souls onboard the UAS may reduce or eliminate some hazards and risks. However, at the discretion of the CAA, this practice may be applied to other UAS operations.
1.5This standard does not purport to address all of the safety concerns, if any, associated with its use. It is the responsibility of the user of this standard to establish appropriate safety and health practices and determine the applicability of regulatory limitations prior to use.